EPON MIB WG L. Khermosh
Internet-Draft Passave Technologies
Expires: August 14, 2006 February 10, 2006
Managed Objects of EPON
draft-ietf-hubmib-efm-epon-mib-04.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 14, 2006.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in TCP/IP based
Internets. In particular, it defines objects for managing for
generic point to multi-point (P2MP) networks, and in specifically
Ethernet Passive Optical Networks (EPON) interfaces, defined in IEEE
Std 802.3ah-2004, which amends IEEE Std 802.3-2002.
The Internet-Standard Management Framework
Khermosh Expires August 14, 2006 [Page 1]
Internet-Draft Managed Objects of EPON February 2006
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. Managed objects are accessed via a virtual
information store, termed the Management Information Base or MIB.
MIB objects are generally accessed through the Simple Network
Management Protocol (SNMP). Objects in the MIB are defined using the
mechanisms defined in the Structure of Management Information (SMI).
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
[RFC2579] and STD 58, RFC 2580 [RFC2580].
Terminology
Key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
Khermosh Expires August 14, 2006 [Page 2]
Internet-Draft Managed Objects of EPON February 2006
Table of Contents
1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Terminology and abbreviations . . . . . . . . . . . . . . 4
1.2. EPON architecture highlights . . . . . . . . . . . . . . . 5
1.2.1. Introduction . . . . . . . . . . . . . . . . . . . . . 5
1.2.2. Principles of operation . . . . . . . . . . . . . . . 6
1.2.3. The physical media . . . . . . . . . . . . . . . . . . 7
1.2.4. PMD specifications . . . . . . . . . . . . . . . . . . 8
1.2.5. Point to point emulation . . . . . . . . . . . . . . . 8
1.2.6. MPCP principles . . . . . . . . . . . . . . . . . . . 9
1.2.7. Forward Error correction (FEC) . . . . . . . . . . . . 11
1.3. Management architecture . . . . . . . . . . . . . . . . . 12
2. MIB structure . . . . . . . . . . . . . . . . . . . . . . . . 18
3. Relation to other MIB Modules . . . . . . . . . . . . . . . . 19
3.1. Relation to the Interfaces MIB and Ethernet-like
Interfaces MIB . . . . . . . . . . . . . . . . . . . . . . 19
3.2. Relation to the IEEE 802.3 MAU MIBs . . . . . . . . . . . 23
3.3. Relation to the EFM OAM MIB . . . . . . . . . . . . . . . 24
3.4. Relation to the bridge MIB . . . . . . . . . . . . . . . . 24
4. Relation table of the dot3EPON MIB module objects to the
IEEE802.3ah attributes . . . . . . . . . . . . . . . . . . . . 25
5. Definitions - The DOT3 EPON MIB module . . . . . . . . . . . . 29
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 70
7. Security Considerations . . . . . . . . . . . . . . . . . . . 71
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 73
8.1. Normative References . . . . . . . . . . . . . . . . . . . 73
8.2. Informative References . . . . . . . . . . . . . . . . . . 73
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 75
Intellectual Property and Copyright Statements . . . . . . . . . . 76
Khermosh Expires August 14, 2006 [Page 3]
Internet-Draft Managed Objects of EPON February 2006
1. Overview
This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in TCP/IP based
Internets. In particular, it defines objects for managing interfaces
that conform to the Ethernet Passive Optical Networks (EPON) standard
as defined in [802.3ah], which are extended capabilities to the
Ethernet like interfaces. The document contains a list of management
entities based on the attributes defined in [802.3ah] Annex 30A for
the EPON section.
1.1. Terminology and abbreviations
BER - Bit Error Rate
BW - Bandwidth
CO - Central Office
CPE - Central Premises Equipment
FCS - Frame Check Sequence
EFM - Ethernet First Mile
EPON - Ethernet Passive Optical Network
LLID - Logical Link IDentifier
MAC - Media Access Control
MPCP - Multi-Point Control Protocol
OAM - Operation Administration Maintenance
OLT - Optical Line Terminal (Server unit of the EPON)
ONU - Optical Network Unit (Client unit of the EPON)
PHY - Physical Layer
PMD - Physical Medium Dependant
RTT - Round Trip Time
SLA - Service Level Agreement
TDM - Time Division Multiplexing
Khermosh Expires August 14, 2006 [Page 4]
Internet-Draft Managed Objects of EPON February 2006
1.2. EPON architecture highlights
1.2.1. Introduction
The EPON standard, as defined in [802.3ah], is defining the Layer 1
(Physical media) and layer 2 (media access) interfaces for the
Ethernet passive optical networks. The EPON is a Gigabit Ethernet
protocol for the Optical Access based on passive optical splitting
(PON) topology. A Passive Optical Network (PON) is a single, shared
optical fiber that uses optical passive splitters to divide 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.
Standard is IEEE802.3ah.
The following diagram describes the PON topology:
Device with
one or more P2MP
interfaces such as OLT
for EPON An EPON IP host
------- OLT ONU "modem" --------
Other IEEE | | interface | interface ------ Other IEEE| |
interface | |-------\----------------| | interface | |
===========| | \ | |===========| |
| | \ ------ --------
| | \ ------ --------
. . \------------| | | |
| |------\ | |===========| |
| | \ ------ --------
------- \ etc
The architecture positioning is defined in the [802.3ah] Figure 56.2
diagram. The [802.3ah] defines the following clauses for the network
operation.
Clause 30 - management
Clause 60 - PMD for the EPON media (Burst PMD)
Khermosh Expires August 14, 2006 [Page 5]
Internet-Draft Managed Objects of EPON February 2006
Clause 64 - MPCP (Multipoint control protocol) - defines the media
access for the operation of the multipoint architecture of the EPON.
Clause 65 -
a) Virtual links for the EPON
b) FEC
c) PMA for the EPON.
1.2.2. Principles of operation
The EPON protocol is based on the gigabit Ethernet protocol of the
IEEE as described in [802.3ah] clause 35 and 36. The interface to
the MAC is through the GMII I/F as described in clause 35 and the PCS
layer is based on the gigabit Ethernet clause 36. The MPCP is placed
in the MAC control layer. The Emulation layer, located at the RS
(Reconciliation Sublayer), creates virtual private path to each ONU
and the FEC enhances reach and split performance.
Khermosh Expires August 14, 2006 [Page 6]
Internet-Draft Managed Objects of EPON February 2006
The following diagram describes the layering:
+==========================================+
| Higher layers |
+==========================================+
| 802.1D Bridge |
+==========================================+
| MAC client| ... |MAC client|
+==========================================+
| MAC Control - (MPCP) | *NEW*
+==========================================+
| MAC | ... | MAC |
+==========================================+
| P2P Emulation (P2PE) | *NEW*
+==========================================+
| |
| GMII |
| |
+==========================================+
| PCS |
+==========================================+
| FEC | *NEW*
+==========================================+
| PMA |
+==========================================+
| PMD |
+==========================================+
| |
| MDI |
| |
/===================/
/ Media /
/===================/
1.2.3. The physical media
Uplink and downlink are multiplexed using separated wavelengths on
the same fiber. The Downlink is a broadcast media where the OLT
transmits the data to all ONUs. The uplink is a shared transmission
media for all of the ONUs. The uplink multiplexing access is based
on time division (TDM) and the management of the TDM access is
defined in the Multi-Point control protocol (MPCP). The upstream
collisions are avoided through the transmission coordination done by
the MPCP protocol. The transmission is of one ONU at a time. The
OLT send control messages (GATE messages) allowing ONUs to transmit,
Khermosh Expires August 14, 2006 [Page 7]
Internet-Draft Managed Objects of EPON February 2006
defining when the transmission occurs and what is its duration.
These messages define the 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 to divide the BW and control the
delay of each ONU according to its SLA.
1.2.4. PMD specifications
The same wavelength optical plan as ITU-T G.983 is selected. The
transceivers are derivations from existing Ethernet optics
transceivers. What is added is the burst functionality for the
uplink - burst transmission at the ONU and burst reception at the
OLT. The [802.3ah] selected very relaxed burst parameters.
1.2.5. Point to point emulation
An emulated point-to-point link is created for each ONU. The
downstream transmission is an aggregation of point-to-point tunnels
and single-copy-broadcast channel (tagged as all ones LLID). The
ONUa filter traffic not intended for their reception according to the
virtual link marking. An LLID tag is attached at the preamble to
denote the virtual link - destination at the downstream and source at
the upstream.
The virtual links concept is also used to avoid violations of
bridging rules for peer to peer traffic in the PON. A bridge sees a
single MAC Client for every link pair. The private paths concept
means no networking problems exist and it provides subscriber
isolation. As the tunneling is only virtual there is a single
physical interface and a single physical layer for the device
including attributes like local MAC address. The following diagram
describes the virtual tunneling for the EPON.
Khermosh Expires August 14, 2006 [Page 8]
Internet-Draft Managed Objects of EPON February 2006
Trunk Line
|
|
|
\|/
+===============================================+
| 802.1D Bridge |
+===============================================+
| MAC client1| ... |MAC client3|
+===============================================+
| MP2PE |
+===============================================+
| PHY |
=================================================
| | |
| | |
\|/ \|/ \|/
+============+ +============+ +============+
| PHY | | PHY | | PHY |
+============+ +============+ +============+
| MP2PE | | MP2PE | | MP2PE |
+============+ +============+ +============+
| MAC client | | MAC client | | MAC client |
+============+ +============+ +============+
| PHY | | PHY | | PHY |
+============+ +============+ +============+
/|\ /|\ /|\
| | |
| | |
| | |
Subscriber1 Subscriber2 Subscriber3
1.2.6. MPCP principles
The OLT, which is the server unit, manages the network. The MPCP
controls the TDM transmission of the uplink. The MPCP is implemented
at the MAC control layer and the MPCP messages are MAC control
messages using the 8808 Ethertype. These messages are not forwarded
from the MAC. A concept of time must exist in the protocol in order
to schedule the uplink transmission. The synchronized timestamp in
the network is managed through the MPCP messages. The timestamp is
also used to measure the RTT of each ONU and compensate it for
transmission. The difference of incoming timestamp to local time
allows OLT to calculate the RTT. 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 at the gate message to shift the ONU
Khermosh Expires August 14, 2006 [Page 9]
Internet-Draft Managed Objects of EPON February 2006
transmission time in the opposite direction.
A scheduling algorithm at the OLT, which is not defined in the
[802.3ah], is responsible to divide the BW and control the
transmission delay of each ONU according to its SLA. In order for
this algorithm to be efficient a closed loop operation is enabled
meaning. The closed loop is achieved by that the ONU reports on the
amount of BW it require for transmission. This allows to allocate
different peak BW for each ONU at different times using the
statistical properties of the traffic hence allowing oversubscription
of the BW. The messages are for the BW report are denoted as REPORT
messages which report the amount of data in the ONU queues. In
addition to that the MPCP defines a protocol of auto-discovery and
registration of ONUs.
The registration process is defined in the diagram below:
OLT ONU
| |
| Discovery Gate \|
|--------------------------------------------|
| /|
| |
|/ Register Request |
|--------------------------------------------|
|\ |
| |
| Register |
| (assigning LLID) \|
|--------------------------------------------|
| /|
| |
| Gate \|
|--------------------------------------------|
| /|
| |
|/ Register ACK |
|--------------------------------------------|
|\ |
| |
| |
A new ONU requests to register (sends a REG_REQUEST message) in a
Khermosh Expires August 14, 2006 [Page 10]
Internet-Draft Managed Objects of EPON February 2006
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
new ONUs is not known yet a collision in transmission might occur. A
random backoff mechanism of transmission is used to schedule the next
registration requests to avoid these collisions. When the OLT
receives REG_REQUEST message of an ONU and approves this ONU then it
sends a REGISTER message to this ONU defining its LLID. From this
time the ONU transmission is scheduled by its LLID, knowing the RTT,
and no collision can occur. The ONU replies with a REGISTER_ACK
message and the registration process of the MPCP ends. Higher layer
protocols may yet be needed to authenticate the ONU and allow it to
participate in the network.
1.2.7. Forward Error correction (FEC)
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
the distance are limited by the link budget and hence an FEC which
improves the link budget is very useful. The FEC code used is the
RS(239,255,8), similar to G.975 improving the BER from 1E-4 to 1E-12.
The FEC parity encapsulation is based on the Ethernet frames. The
Ethernet frames are spaced by rate adaptation, and the parity bytes
are inserted in the provided space.
As the start and end of frame signals are outside of the FEC
protection, they are replaced by a series of symbols to enhance their
vulnerability to errors.
The following diagram presents an FEC protected frame:
+-------------------------------------------------------------------+
| | | | | | | |
| S_FEC | Preamble/SFD | Frame | FCS | T_FEC | Parity | T_FEC |
| | | | | | | |
+-------------------------------------------------------------------+
The FEC layer introduces a fixed delay in the receive and transmit
path.
The FEC layer is optional.
Khermosh Expires August 14, 2006 [Page 11]
Internet-Draft Managed Objects of EPON February 2006
1.3. Management architecture
Each one of the EPON layers is accompanied by a management I/F, which
is controlled through clause 30 of the spec. The MIB document
allocates for each one of them a separate package, as the [802.3ah]
spec may be used for different applications and may use some of the
clauses separately.
The following diagram presents the packages relation to IEEE layering
diagram:
+===========================+
| Higher layers |
+===========================+
| 802.1D Bridge |
+===========================+
|MAC client| ... |MAC client|
+===========================+ \ +=============================+
| MAC Control - (MPCP) |----- |MpcpObjects| ... |MpcpObjects|
+===========================+ / +=============================+
| MAC | ... | MAC |
+===========================+ \ +=============================+
| P2P Emulation (P2PE) |----- |OmpEmulat | |OmpEmulat |
+===========================+ / |ionObjects | ... |ionObjects |
| | +=============================+
| GMII |
| |
+===========================+
| PCS |
+===========================+ \ +=============================+
| FEC |----- |FecObjects | ... |FecObjects |
+===========================+ / +=============================+
| PMA |
+===========================+
| PMD |
+===========================+
| |
| MDI |
| |
/===============/
/ Media /
/===============/
Khermosh Expires August 14, 2006 [Page 12]
Internet-Draft Managed Objects of EPON February 2006
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
interfaces for the virtual links of the ONUs ( and another virtual
interface for the broadcast virtual link). As can be seen from the
layering diagram above, the MAC is virtually duplicated and therefore
the selection for the management for this scenario is to allocate an
interface index for each one of the virtual link and an additional
interface index for the OLT. Therefore the Interface, MAU and
etherLike interfaces MIBs have a row (ifIndex) for each virtual link
at the OLT. The justification for this partition is that the
interfaces are quite well separated as they present physical
different ONUs which are viewed from the OLT point of view, and for
instance there is a meaning for a separate bad frames, or bad octets
counters for each virtual link as the ONUs can be distanced
differently, which is quite similar to a separate physical interface.
The same partition concept exists for the MIB module of this
document. Each row in the tables is selected according to the
ifIndex and specifically there is a row for each virtual link. There
are a few control objects which are defined for the entire layer (and
they should have the same value for each ifIndex) but most of the
objects are partitioned into N+1 logical interfaces at the OLT for
each layer. It is a bit different than the IEEE layering diagram
which present the P2MP layer as a single layer while duplicating the
MAC and MAC client layers (Please see the diagram above). However
from management perspective it is more convenient and neat to
partition the management of the entities for the virtual links as the
managed atomic entity is the virtual link, and use the interface
index for that purpose as it is already used for 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
table for an OLT with 3 ONUs registered:
Khermosh Expires August 14, 2006 [Page 13]
Internet-Draft Managed Objects of EPON February 2006
At ONU1 in working mode, one row:
+---------------------------+-----------------+
| MPCP control MIB object | Value |
+---------------------------+-----------------+
| ifIndex | 1 |
| | |
| dot3MpcpOperStatus | true |
| | |
| dot3MpcpAdminState | true |
| | |
| dot3MpcpMode | onu |
| | |
| dot3MpcpSyncTime | 25 |
| | |
| dot3MpcpLinkID | 1 |
| | |
| dot3MpcpRemoteMACAddress | OLT_MAC_Address |
| | |
| dot3MpcpRegistrationState | registered |
| | |
| dot3MpcpTransmitElapsed | 10 |
| | |
| dot3MpcpReceiveElapsed | 10 |
| | |
| dot3MpcpRoundTripTime | 100 |
+---------------------------+-----------------+
Table 1
Khermosh Expires August 14, 2006 [Page 14]
Internet-Draft Managed Objects of EPON February 2006
at the OLT in working mode the MPCP cotrol objects associated with
the virtual links, 4 rows
+----------------+-----------+------------+------------+------------+
| MPCP control | Value | Value | Value | Value |
| MIB object | | | | |
+----------------+-----------+------------+------------+------------+
| ifIndex | 1 | 2 | 3 | 65535 |
| | | | | |
| dot3MpcpOperSt | true | true | true | true |
| atus | | | | |
| | | | | |
| dot3MpcpAdminS | true | true | true | true |
| tate | | | | |
| | | | | |
| dot3MpcpMode | olt | olt | olt | olt |
| | | | | |
| dot3MpcpSyncTi | 25 | 25 | 25 | 25 |
| me | | | | |
| | | | | |
| dot3MpcpLinkID | 1 | 2 | 3 | 65535 |
| | | | | |
| dot3MpcpRemote | ONU1_MAC_ | ONU2_MAC_A | ONU3_MAC_A | BRCT_MAC_A |
| MACAddress | Address | ddress | ddress | ddress |
| | | | | |
| dot3MpcpRegist | registere | registered | registered | registered |
| rationState | d | | | |
| | | | | |
| dot3MpcpTransm | 10 | 10 | 10 | 10 |
| itElapsed | | | | |
| | | | | |
| dot3MpcpReceiv | 10 | 10 | 10 | 10 |
| eElapsed | | | | |
| | | | | |
| dot3MpcpRoundT | 100 | 60 | 20 | 0 |
| ripTime | | | | |
+----------------+-----------+------------+------------+------------+
Table 2
The creation of the rows at the ONU and at the OLT, for the OLT
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
table after initialization:
Khermosh Expires August 14, 2006 [Page 15]
Internet-Draft Managed Objects of EPON February 2006
At ONU1 in working mode, one row:
+---------------------------+--------------+
| MPCP control MIB object | Value |
+---------------------------+--------------+
| ifIndex | 1 |
| | |
| dot3MpcpOperStatus | true |
| | |
| dot3MpcpAdminState | true |
| | |
| dot3MpcpMode | onu |
| | |
| dot3MpcpSyncTime | 0 |
| | |
| dot3MpcpLinkID | 0 |
| | |
| dot3MpcpRemoteMACAddress | 00 |
| | |
| dot3MpcpRegistrationState | unregistered |
| | |
| dot3MpcpTransmitElapsed | 0 |
| | |
| dot3MpcpReceiveElapsed | 0 |
| | |
| dot3MpcpRoundTripTime | 0 |
+---------------------------+--------------+
Table 3
Khermosh Expires August 14, 2006 [Page 16]
Internet-Draft Managed Objects of EPON February 2006
at the OLT in working mode the MPCP cotrol objects associated with
the virtual links, one row:
+---------------------------+------------------+
| MPCP control MIB object | Value |
+---------------------------+------------------+
| ifIndex | 65535 |
| | |
| dot3MpcpOperStatus | true |
| | |
| dot3MpcpAdminState | true |
| | |
| dot3MpcpMode | olt |
| | |
| dot3MpcpSyncTime | 25 |
| | |
| dot3MpcpLinkID | 65535 |
| | |
| dot3MpcpRemoteMACAddress | BRCT_MAC_Address |
| | |
| dot3MpcpRegistrationState | registered |
| | |
| dot3MpcpTransmitElapsed | 10 |
| | |
| dot3MpcpReceiveElapsed | 100000 |
| | |
| dot3MpcpRoundTripTime | 0 |
+---------------------------+------------------+
Table 4
The example above shows the MPCP control objects when 3 ONUs are
registered. Creation of rows for the Interface, MAU and etherLike
interfaces MIBs is quite similar. Please see the example in section
3.
Khermosh Expires August 14, 2006 [Page 17]
Internet-Draft Managed Objects of EPON February 2006
2. MIB structure
This document defines the DOT3 EPON MIB module. The DOT3 EPON MIB
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
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
65 point to point emulation attributes. In this MIB module group:
The dot3OmpEmulationTable defines the objects used for the
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]
clause 60 and clause 65 EPON FEC attributes. The dot3EponFecTable
defines the objects used for the configurations and status
indications, which are per logical link, of FEC EPON compliant
interfaces.
The EPON extended package MIB objects defining the objects used for
configuration and description of management objects for extended
capabilities of the EPON interfaces. The dot3ExtPkgControlTable
defines the extended package objects, which are per logical link,
used for the configuration and status indication of the EPON
interfaces. The dot3ExtPkgQueueTable defines the extended package
objects, which are per logical link, and per REPORT queue used for
the configuration and status indication of the ONU queues reported at
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.
Khermosh Expires August 14, 2006 [Page 18]
Internet-Draft Managed Objects of EPON February 2006
3. Relation to other MIB Modules
3.1. Relation to the Interfaces MIB and Ethernet-like Interfaces MIB
EPON interfaces are a type of Ether-like interface. This module
extends the objects of the Ehter-like interfaces management for the
EPON type interfaces. Thus, each managed EPON interface 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]. 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
instance the document is defining dot3MpcpRemoteMACAddress only while
assuming the local MAC address attribute is already defined in
[RFC3635]
Interface Indexes as specified in [RFC2863] are used in these MIB
Modules. The descriptions of the ifIndexes denote which ifIndex is
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 sub-layers defined in the [802.3ah] for the OLT are also divided
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
64.1.2. At the tables this entry is duplicated for the virtual
interfaces.
Implementing this module therefore MUST require implementation of
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
Khermosh Expires August 14, 2006 [Page 19]
Internet-Draft Managed Objects of EPON February 2006
with 3 ONUs registered:
At the ONU in working mode:
+----------------------+-----------------------------------+
| Interface MIB object | Value |
+----------------------+-----------------------------------+
| ifIndex | 1 |
| | |
| ifDescr | "I/F description" |
| | |
| ifType | gigabitEthernet (117) 1000base-Px |
| | |
| ifMtu | MTU size (1522) |
| | |
| ifSpeed | 1000000000 |
| | |
| ifPhysAddress | ONU_MAC_Address |
| | |
| ifAdminStatus | up |
| | |
| ifOperStatus | Up |
| | |
| ifLastChange | up_time |
| | |
| ifInOctets | ONU1_octets_number |
| | |
| ifInUcastPkts | ONU1_unicast_frame_number |
| | |
| ifInNUcastPkts | ONU1_non_unicast_frame_number |
| | |
| ifInDiscards | ONU1_discard_frame_number |
| | |
| ifInErrors | ONU1_error_frame_number |
| | |
| ifInUnknownProtos | ONU1_unknown_frame_number |
| | |
| ifOutOctets | ONU1_octets_number |
| | |
| ifOutUcastPkts | ONU1_unicast_frame_number |
| | |
| ifOutNUcastPkts | ONU1_non_unicast_frame_number |
| | |
| ifOutDiscards | ONU1_discard_frame_number |
| | |
| ifOutErrors | ONU1_error_frame_number |
| | |
Khermosh Expires August 14, 2006 [Page 20]
Internet-Draft Managed Objects of EPON February 2006
| ifOutQLen | ONU1_queue_frame_number |
+----------------------+-----------------------------------+
Table 5
at the OLT in working mode the interfaces associated with the virtual
links:
+----------+-------------+-------------+-------------+--------------+
| Interfac | Value | Value | Value | Value |
| eMIB | | | | |
| object | | | | |
+----------+-------------+-------------+-------------+--------------+
| ifIndex | 1 | 2 | 3 | 65535 |
| | | | | |
| ifDescr | "I/Fdescrip | "I/Fdescrip | "I/Fdescrip | "I/Fdescript |
| | tion" | tion" | tion" | ion" |
| | | | | |
| ifType | gigabitEthe | gigabitEthe | gigabitEthe | gigabitEther |
| | rnet(117) | rnet(117) | rnet(117) | net(117) |
| | | | | |
| ifMtu | MTUsize(152 | MTUsize(152 | MTUsize(152 | MTUsize(1522 |
| | 2) | 2) | 2) | ) |
| | | | | |
| ifSpeed | 1000000000 | 1000000000 | 1000000000 | 1000000000 |
| | | | | |
| ifPhysAd | OLT_MAC_Add | OLT_MAC_Add | OLT_MAC_Add | OLT_MAC_Addr |
| dress | ress | ress | ress | ess |
| | | | | |
| ifAdminS | up | up | up | up |
| tatus | | | | |
| | | | | |
| ifOperSt | Up | Up | Up | Up |
| atus | | | | |
| | | | | |
| ifLastCh | ONU1_up_tim | ONU2_up_tim | ONU3_up_tim | up_time |
| ange | e | e | e | |
| | | | | |
| ifInOcte | ONU1_octets | ONU2_octets | ONU3_octets | BRCT_octets_ |
| ts | _number | _number | _number | number |
| | | | | |
| ifInUcas | ONU1_unic_f | ONU2_unic_f | ONU3_unic_f | BRCT_unic_fr |
| tPkts | rame_num | rame_num | rame_num | ame_num |
| | | | | |
| ifInNUca | ONU1_non_un | ONU2_non_un | ONU3_non_un | BRCT_non_uni |
| stPkts | ic_frame_nu | ic_frame_nu | ic_frame_nu | c_frame_num |
| | m | m | m | |
| | | | | |
Khermosh Expires August 14, 2006 [Page 21]
Internet-Draft Managed Objects of EPON February 2006
| ifInDisc | ONU1_disc_f | ONU2_disc_f | ONU3_disc_f | BRCT_disc_fr |
| ards | rame_num | rame_num | rame_num | ame_numr |
| | | | | |
| ifInErro | ONU1_err_fr | ONU2_err_fr | ONU3_err_fr | BRCT_err_fra |
| rs | ame_num | ame_num | ame_num | me_num |
| | | | | |
| ifInUnkn | ONU1_unknw_ | ONU2_unknw_ | ONU3_unknw_ | BRCT_unknw_f |
| ownProto | frame_num | frame_num | frame_num | rame_num |
| s | | | | |
| | | | | |
| ifOutOct | ONU1_octets | ONU2_octets | ONU3_octets | BRCT_octets_ |
| ets | _number | _number | _number | number |
| | | | | |
| ifOutUca | ONU1_unic_f | ONU2_unic_f | ONU3_unic_f | BRCT_unic_fr |
| stPkts | rame_num | rame_num | rame_num | ame_num |
| | | | | |
| ifOutNUc | ONU1_non_un | ONU2_non_un | ONU3_non_un | BRCT_non_uni |
| astPkts | ic_frame_nu | ic_frame_nu | ic_frame_nu | c_frame_num |
| | m | m | m | |
| | | | | |
| ifOutDis | ONU1_disc_f | ONU2_disc_f | ONU3_disc_f | BRCT_disc_fr |
| cards | rame_num | rame_num | rame_num | ame_num |
| | | | | |
| ifOutErr | ONU1_err_fr | ONU2_err_fr | ONU3_err_fr | BRCT_err_fra |
| ors | ame_num | ame_num | ame_num | me_num |
| | | | | |
| ifOutQLe | ONU1_queue_ | ONU2_queue_ | ONU3_queue_ | BRCt_queue_f |
| n | frame_num | frame_num | frame_num | rame_num |
+----------+-------------+-------------+-------------+--------------+
Table 6
And the OLT interface:
+----------------------+-----------------------------------+
| Interface MIB object | Value |
+----------------------+-----------------------------------+
| ifIndex | 100000 |
| | |
| ifDescr | "I/F description" |
| | |
| ifType | gigabitEthernet (117) 1000base-Px |
| | |
| ifMtu | MTU size (1522) |
| | |
| ifSpeed | 1000000000 |
| | |
| ifPhysAddress | OLT_MAC_Address |
Khermosh Expires August 14, 2006 [Page 22]
Internet-Draft Managed Objects of EPON February 2006
| 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
As specified above the creation of the rows at the ONU and at the
OLT, for the OLT interface and for the broadcast virtual index, is
done at initialization. The creation and deletion of rows for the
virtual links is done when the virtual link is established (ONU
registers) and when the virtual link is deleted (ONU deregisters).
3.2. Relation to the IEEE 802.3 MAU MIBs
In the amended MAU MIB document the MAU types of the EPON Interfaces
is defined. This document assumes the implementation of the MAU MIB
for this purpose and does not repeat the EPON MAU types. Therefore
implementing this module MUST require implementation of MAU-MIB
module [RFC3636]. For the ONU there is a single row for the
ifMauTable. At the OLT there is a row for each virtual link (N+1),
ifMauIfIndex has a value for each virtual link.
Khermosh Expires August 14, 2006 [Page 23]
Internet-Draft Managed Objects of EPON February 2006
As specified above the creation of the rows at the ONU and at the OLT
for the OLT interface and for the broadcast virtual index, is done at
initialization. The creation and deletion of rows for the virtual
links is done when the virtual link is established (ONU registers)
and when the virtual link is deleted (ONU deregisters).
3.3. Relation to the EFM OAM MIB
The EPON interfaces are aimed to the access optical networks and most
probably will be followed by implementation of the OAM section of the
[802.3ah]. Therefore The EFM OAM MIB module [I-D.ietf-hubmib-efm-
mib] MAY be implemented defining attributes and managed objects that
are complementary to the EFM EPON MIB module. As the OAM is defined
for a point to point link it is implemented using the virtual links
which are defined for the P2MP network, so that an instance is held
for each Logical link (LLID) of the EPON. The respective ifIndex of
the virtual link is used as the ifIndex of the OAM MIB for this
purpose.
3.4. Relation to the bridge MIB
It is very probable that an EPON OLT will implement a bridging
functionality above the EPON interface layer, bridging between the
EPON users and the network. In this scenario the virtual ports of
the EPON are corresponding to the virtual bridge ports. There is a
direct mapping between the bridge ports and the LLIDs, which are
virtual EPON channels.
If the OLT supports bridging then the virtual physical interfaces are
the bridge virtual ports. The values for dot1dBasePortIfIndex would
be the number of the ifIndex for the virtual port (1 for LLID1, 2 for
LLID2,...)
The bridge MIB modules [RFC4188], [RFC1525] MAY be implemented in
this case where the objects of the bridge MIB module are used
accordingly.
Khermosh Expires August 14, 2006 [Page 24]
Internet-Draft Managed Objects of EPON February 2006
4. Relation table of the dot3EPON MIB module objects to the
IEEE802.3ah attributes
oMPCP managed object class (30.3.5)
+----------------------------+-------------------------+------------+
| dot3EPON MIB module object | IEEE802.3ah attribute | Reference |
+----------------------------+-------------------------+------------+
| ifIndex | aMPCPID | 30.3.5.1.1 |
| | | |
| dot3MpcpOperStatus | aMPCPAdminState | 30.3.5.1.2 |
| | | |
| dot3MpcpMode | aMPCPMode | 30.3.5.1.3 |
| | | |
| dot3MpcpLinkID | aMPCPLinkID | 30.3.5.1.4 |
| | | |
| dot3MpcpRemoteMACAddress | aMPCPRemoteMACAddress | 30.3.5.1.5 |
| | | |
| dot3MpcpRegistrationState | aMPCPRegistrationState | 30.3.5.1.6 |
| | | |
| dot3MpcpMACCtrlFramesTrans | aMPCPMACCtrlFramesTrans | 30.3.5.1.7 |
| mitted | mitted | |
| | | |
| dot3MpcpMACCtrlFramesRecei | aMPCPMACCtrlFramesRecei | 30.3.5.1.8 |
| ved | ved | |
| | | |
| dot3MpcpTxGate | aMPCPTxGate | 30.3.5.1.9 |
| | | |
| dot3MpcpTxRegAck | aMPCPTxRegAck | 30.3.5.1.1 |
| | | 0 |
| | | |
| dot3MpcpTxRegister | aMPCPTxRegister | 30.3.5.1.1 |
| | | 1 |
| | | |
| dot3MpcpTxRegRequest | aMPCPTxRegRequest | 30.3.5.1.1 |
| | | 2 |
| | | |
| dot3MpcpTxReport | aMPCPTxReport | 30.3.5.1.1 |
| | | 3 |
| | | |
| dot3MpcpRxGate | aMPCPRxGate | 30.3.5.1.1 |
| | | 4 |
| | | |
| dot3MpcpRxRegAck | aMPCPRxRegAck | 30.3.5.1.1 |
| | | 5 |
| | | |
| dot3MpcpRxRegister | aMPCPRxRegister | 30.3.5.1.1 |
| | | 6 |
Khermosh Expires August 14, 2006 [Page 25]
Internet-Draft Managed Objects of EPON February 2006
| dot3MpcpRxRegRequest | aMPCPRxRegRequest | 30.3.5.1.1 |
| | | 7 |
| | | |
| dot3MpcpRxReport | aMPCPRxReport | 30.3.5.1.1 |
| | | 8 |
| | | |
| dot3MpcpTransmitElapsed | aMPCPTransmitElapsed | 30.3.5.1.1 |
| | | 9 |
| | | |
| dot3MpcpReceiveElapsed | aMPCPReceiveElapsed | 30.3.5.1.2 |
| | | 0 |
| | | |
| dot3MpcpRoundTripTime | aMPCPRoundTripTime | 30.3.5.1.2 |
| | | 1 |
| | | |
| dot3MpcpDiscoveryWindowsSe | aMPCPDiscoveryWindowsSe | 30.3.5.1.2 |
| nt | nt | 2 |
| | | |
| dot3MpcpDiscoveryTimeout | aMPCPDiscoveryTimeout | 30.3.5.1.2 |
| | | 3 |
| | | |
| dot3MpcpMaximumPendingGran | aMPCPMaximumPendingGran | 30.3.5.1.2 |
| ts | ts | 4 |
| | | |
| dot3MpcpAdminState | aMPCPAdminControl | 30.3.5.2.1 |
| | | |
| dot3MpcpSyncTime | SyncTime | 64.3.3.2 |
+----------------------------+-------------------------+------------+
Table 8
Khermosh Expires August 14, 2006 [Page 26]
Internet-Draft Managed Objects of EPON February 2006
oOMPEmulation managed object class (30.3.7)
+-------------------------------------+-----------------+-----------+
| dot3EPON MIB module object | IEEE802.3ah | Reference |
| | attribute | |
+-------------------------------------+-----------------+-----------+
| ifIndex | aOMPEmulationID | 30.3.7.1. |
| | | 1 |
| | | |
| dot3OmpEmulationType | aOMPEmulationTy | 30.3.7.1. |
| | pe | 2 |
| | | |
| dot3OmpEmulationSLDErrors | aSLDErrors | 30.3.7.1. |
| | | 3 |
| | | |
| dot3OmpEmulationCRC8Errors | aCRC8Errors | 30.3.7.1. |
| | | 4 |
| | | |
| dot3OmpEmulationGoodLLID | aGoodLLID | 30.3.7.1. |
| | | 5 |
| | | |
| dot3OmpEmulationOnuPonCastLLID | aONUPONcastLLID | 30.3.7.1. |
| | | 6 |
| | | |
| dot3OmpEmulationOltPonCastLLID | aOLTPONcastLLID | 30.3.7.1. |
| | | 7 |
| | | |
| dot3OmpEmulationBadLLID | aBadLLID | 30.3.7.1. |
| | | 8 |
| | | |
| dot3OmpEmulationBroadcastBitNotOnuL | | |
| Lid | | |
| | | |
| dot3OmpEmulationOnuLLIDNotBroadcast | | |
| | | |
| dot3OmpEmulationBroadcastBitPlusOnu | | |
| Llid | | |
| | | |
| dot3OmpEmulationNotBroadcastBitNotO | | |
| nuLlid | | |
+-------------------------------------+-----------------+-----------+
Table 9
Khermosh Expires August 14, 2006 [Page 27]
Internet-Draft Managed Objects of EPON February 2006
oMAU managed object class (30.5.1)
+--------------------------------+---------------------+------------+
| dot3EPON MIB module object | IEEE802.3ah | Reference |
| | attribute | |
+--------------------------------+---------------------+------------+
| dot3EponFecPCSCodingViolation | aPCSCodingViolation | 30.5.1.1.1 |
| | | 2 |
| | | |
| dot3EponFecAbility | aFECAbility | 30.5.1.1.1 |
| | | 3 |
| | | |
| dot3EponFecMode | aFECmode | 30.5.1.1.1 |
| | | 4 |
| | | |
| dot3EponFecCorrectedBlocks | aFECCorrectedBlocks | 30.5.1.1.1 |
| | | 5 |
| | | |
| dot3EponFecUncorrectableBlocks | aFECUncorrectableBl | 30.5.1.1.1 |
| | ocks | 6 |
| | | |
| dot3EponFecBufferHeadCodingVio | | |
| lation | | |
+--------------------------------+---------------------+------------+
Table 10
Khermosh Expires August 14, 2006 [Page 28]
Internet-Draft Managed Objects of EPON February 2006
5. Definitions - The DOT3 EPON MIB module
DOT3-EPON-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2, OBJECT-TYPE, Counter32,
Integer32, Unsigned32, Counter64
FROM SNMPv2-SMI
TruthValue, MacAddress
FROM SNMPv2-TC
ifIndex
FROM IF-MIB
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF
;
dot3EponMIB MODULE-IDENTITY
LAST-UPDATED "200602080000Z" -- February 8, 2006
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working
Group"
CONTACT-INFO
"WG charter:
http://www.ietf.org/html.charters/hubmib-charter.html
Mailing Lists:
General Discussion: hubmib@ietf.org
To Subscribe: hubmib-request@ietf.org
In Body: subscribe your_email_address
Chair: Dan Romascanu
Postal: Avaya
Atidim Technology Park, Bldg. 3
Tel Aviv 61131
Israel
Tel: +972-3-645-8414
E-mail: dromasca@avaya.com
Editor: Lior Khermosh
Postal: Passave Technologies Inc.
Kohav Hertzelia bldg,
94 Hasadnaot St.
Hertzliya Pituach 46120,
ISRAEL
P.O.Box 2089 Hertzliya Pituach 46120 Israel
Tel: +972-9-9628000 Ext: 302
E-mail: lior.khermosh@passave.com"
DESCRIPTION
Khermosh Expires August 14, 2006 [Page 29]
Internet-Draft Managed Objects of EPON February 2006
"The objects in this MIB module are used to manage the
Ethernet in the First Mile(EFM) Ethernet Passive Optical
Network(EPON) Interfaces as defined in IEEE P802.3ah
clause 60,64,65.
The following reference is used throughout this MIB module:
[802.3ah] refers to:
Information technology - Telecommunications and
information exchange between systems - Local and
metropolitan area networks - Specific requirements -
Part 3: Carrier sense multiple access with collision
detection (CSMA/CD) access method and physical layer
specifications - Media Access Control Parameters,
Physical Layers and Management Parameters for subscriber
access networks. IEEE Std 802.3ah-2004, October 2004.
Of particular interest are Clause 64(Multi-Point Control
Protocol - MPCP), Clause 65(Point to Multipoint
Reconciliation Sublayer - P2MP RS), Clause 60 (Ethernet
Passive Optical Network Physical Medium Dependant - EPON
PMDs), Clause 30, 'Management', and Clause 45, 'Management
Data Input/Output (MDIO) Interface'.
Copyright (C) The Internet Society (2005). This version
of this MIB module is part of XXXX see the RFC itself for
full legal notices.
Key abbreviations:
BER - Bit Error Rate
EFM - Ethernet First Mile
EPON - Ethernet Passive Optical Network
LLID - Logical Link IDentifier
MAC - Media Access Control
MPCP - Multi-Point Control Protocol
OLT - Optical Line Terminal (Server unit of the EPON)
ONU - Optical Network Unit (Client unit of the EPON)
PHY - Physical Layer
PMD - Physical Medium Dependant
RTT - Round Trip Time
"
-- Editor's Note: Replace XXXX with the actual RFC number
-- assigned by RFC Editor and remove this note
REVISION "200602080000Z" -- February 8, 2006
DESCRIPTION "Initial version, published as RFC XXXX."
::= { mib-2 XXX }
Khermosh Expires August 14, 2006 [Page 30]
Internet-Draft Managed Objects of EPON February 2006
-- Editor's Note (to be removed prior to publication): the
-- IANA is requested to assign a value for "XXX" under the
-- 'mib-2' subtree and to record the assignment in the SMI
-- Numbers registry. When the assignment has been made, the
-- RFC Editor is asked to replace "XXX" (here and in the MIB
-- module) with the assigned value and to remove this note.
dot3EponObjects OBJECT IDENTIFIER ::= { dot3EponMIB 1}
dot3EponConformance OBJECT IDENTIFIER ::= { dot3EponMIB 2}
-- MPCP MIB modules definitions ([802.3ah] clause 30.3.5)
dot3EponMpcpObjects
OBJECT IDENTIFIER ::= { dot3EponObjects 1 }
dot3MpcpControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3MpcpControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table for dot3 Multi-Point Control Protocol (MPCP)
MIB management objects. The entries in the table are
control and status entities of the MPCP. Each object has
a row for every virtual link according to the proper
ifIndex. Typically the number of expected virtual link
in a PON is like the number of ONUs 32-64 plus an
additional entry for broadcast LLID (which is marked by
0xffff). In the [802.3ah] the LLID is a 2bytes register
and the number of LLIDs is limited by that."
::= { dot3EponMpcpObjects 1 }
dot3MpcpControlEntry OBJECT-TYPE
SYNTAX Dot3MpcpControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the dot3 MPCP Control table.
Rows in the table are created when ifIndexs are created.
For the ONU rows are created at system initialization.
For the OLT the rows of the OLT ifIndex and the row of
the ifIndex referring to the broadcast virtual link are
created at system initialization. For the ifIndexs
referring to the virtual links at the OLT, a row is
created when a virtual link is established (ONU
Khermosh Expires August 14, 2006 [Page 31]
Internet-Draft Managed Objects of EPON February 2006
registers) and deleted when the virtual link is deleted
(ONU deregisters). Rows exist for an OLT interface and
an ONU interface."
INDEX { ifIndex }
::= { dot3MpcpControlTable 1}
Dot3MpcpControlEntry ::=
SEQUENCE {
dot3MpcpOperStatus TruthValue,
dot3MpcpAdminState TruthValue,
dot3MpcpMode INTEGER,
dot3MpcpSyncTime Unsigned32,
dot3MpcpLinkID Unsigned32,
dot3MpcpRemoteMACAddress MacAddress,
dot3MpcpRegistrationState INTEGER,
dot3MpcpTransmitElapsed Unsigned32,
dot3MpcpReceiveElapsed Unsigned32,
dot3MpcpRoundTripTime Unsigned32,
dot3MpcpMaximumPendingGrants Unsigned32
}
dot3MpcpOperStatus OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable reflects the operational state of the
Multi-Point MAC Control sublayer as defined in [802.3ah]
clause 64. When the value is true(1) the interface will
act as if Multi-point control protocol is enabled.
When the value is false(2) the interface will act as if
it does not have the Multi-point control protocol. The
operational state can be changed using the
dot3MpcpAdminState object.
This object is relevant for an OLT, same for all
virtual links, and for an ONU."
REFERENCE "[802.3ah], 30.3.5.1.2."
::= { dot3MpcpControlEntry 1 }
dot3MpcpAdminState OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable can be used to define the admin state of
the Multi-Point MAC Control sublayer as defined in
[802.3ah] clause 64. When selecting the value as true(1)
the interface Multi-Point control protocol is enabled.
Khermosh Expires August 14, 2006 [Page 32]
Internet-Draft Managed Objects of EPON February 2006
When selecting the value as false(2) the interface acts
as if the Multi-point Control protocol does not exist.
Reading reflects the state of the object and the
operation of the Multi-point control protocol mode of
the interface.
Writing can be done at any time.
This object is relevant for an OLT, same for all
virtual links, and for an ONU."
REFERENCE "[802.3ah], 30.3.5.2.1."
DEFVAL { false }
::= { dot3MpcpControlEntry 2 }
dot3MpcpMode OBJECT-TYPE
SYNTAX INTEGER {
olt(1),
onu(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable can be used to identify the operational
state of the Multi-Point MAC Control sublayer as
defined in [802.3ah] clause 64. Reading olt(1) for an
OLT (server) mode and onu(2) for an ONU (client) mode.
This object is relevant for an OLT, same for all
virtual links, and for an ONU."
REFERENCE "[802.3ah], 30.3.5.1.3."
DEFVAL { 1 }
::= { dot3MpcpControlEntry 3 }
dot3MpcpSyncTime OBJECT-TYPE
SYNTAX Unsigned32
UNITS "TQ (16nsec)"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A value that reports the 'sync lock time' for
an OLT receiver in increments of Time Quanta (TQ) 16ns
as defined in [802.3ah] 60,64,65. The value returned
shall be (sync lock time ns)/16. If this value exceeds
(2^32-1) the value (2^32-1) shall be returned.
This object is relevant for an OLT, same for all
virtual links, and for an ONU."
REFERENCE "[802.3ah], 64.3.3.2."
::= { dot3MpcpControlEntry 4 }
Khermosh Expires August 14, 2006 [Page 33]
Internet-Draft Managed Objects of EPON February 2006
dot3MpcpLinkID OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A value that identifies the Logical Link
identity (LLID) associated with the MAC port as
specified in [802.3ah] clause 65.1.3.2.2.
This object is relevant for an OLT and an ONU. For
the same virtual link the value is the same at the ONU
and OLT. Value is assigned when an ONU is registered.
Value is freed when an ONU deregister."
REFERENCE "[802.3ah], 30.3.5.1.4."
::= { dot3MpcpControlEntry 5 }
dot3MpcpRemoteMACAddress OBJECT-TYPE
SYNTAX MacAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A value that identifies the source_address
parameter of the last MPCPDUs passed to the MAC Control.
This value is updated on reception of a valid frame with
(1) a destination Field equal to the reserved multicast
address for MAC Control specified in [802.3] Annex
31A, (2) lengthOrType field value equal to the reserved
Type for MAC Control as specified in [802.3] Annex
31A. (3) an MPCP subtype value equal to the subtype
reserved for MPCP as specified in [802.3ah] Annex 31A.
This object is relevant for an OLT and an ONU.
The value reflects the MAC address of the remote entry
and therefore the OLT hold a value for each LLID and the
ONU has a single value which is the OLT MAC address. "
REFERENCE "[802.3ah], 30.3.5.1.5."
::= { dot3MpcpControlEntry 6 }
dot3MpcpRegistrationState OBJECT-TYPE
SYNTAX INTEGER {
unregistered(1),
registering(2),
registered(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A value that identifies the operational state
of the Multi-Point MAC Control sublayer as defined in
[802.3ah] clause 64. When this object has the
Khermosh Expires August 14, 2006 [Page 34]
Internet-Draft Managed Objects of EPON February 2006
enumeration unregistered(1) the interface may be used
for registering a link partner. When this object has
the enumeration registering(2) the interface is in the
process of registering a link-partner. When this
object has the enumeration registered(3) the
interface has an established link-partner.
This object is relevant for an OLT and an ONU. For
the OLT it provides an indication per LLID."
REFERENCE "[802.3ah], 30.3.5.1.6."
::= { dot3MpcpControlEntry 7 }
dot3MpcpTransmitElapsed OBJECT-TYPE
SYNTAX Unsigned32
UNITS "TQ (16nsec)"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A value that reports the interval from last
MPCP frame transmission in increments of Time Quanta
(TQ) 16ns. The value returned shall be (interval from
last MPCP frame transmission in ns)/16. If this value
exceeds (2^32-1) the value (2^32-1) shall be returned.
This object is relevant for an OLT and an ONU. For
the OLT it provides an indication per LLID."
REFERENCE "[802.3ah], 30.3.5.1.19."
::= { dot3MpcpControlEntry 8 }
dot3MpcpReceiveElapsed OBJECT-TYPE
SYNTAX Unsigned32
UNITS "TQ (16nsec)"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A value that reports the interval from last
MPCP frame reception in increments of Time Quanta (TQ)
16ns. The value returned shall be (interval from last
MPCP last MPCP frame reception in ns)/16. If this value
exceeds (2^32-1) the value (2^32-1) shall be returned.
This object is relevant for an OLT and an ONU. For
the OLT it provides an indication per LLID."
REFERENCE "[802.3ah], 30.3.5.1.20."
::= { dot3MpcpControlEntry 9 }
dot3MpcpRoundTripTime OBJECT-TYPE
SYNTAX Unsigned32 (0..'ffff'h)
UNITS "TQ (16nsec)"
MAX-ACCESS read-only
STATUS current
Khermosh Expires August 14, 2006 [Page 35]
Internet-Draft Managed Objects of EPON February 2006
DESCRIPTION
"A value that reports the MPCP round trip time
in increments of Time Quanta (TQ) 16ns. The value
returned shall be (round trip time in ns)/16. If this
value exceeds (2^16-1) the value (2^16-1) shall be
returned. This object is relevant for an OLT only.
For the OLT there is a value per LLID"
REFERENCE "[802.3ah], 30.3.5.1.21."
::= { dot3MpcpControlEntry 10 }
dot3MpcpMaximumPendingGrants OBJECT-TYPE
SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A value that indicates the maximum number of
grants an ONU can store. The maximum number of grants an
ONU can store has a range of 0 to 255.
This object is relevant for an OLT and an ONU. For
the OLT there is a value per LLID"
REFERENCE "[802.3ah], 30.3.5.1.24."
::= { dot3MpcpControlEntry 11 }
dot3MpcpStatTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3MpcpStatEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table defines the list of statistics counters for
[802.3ah] clause 64 MPCP interface. Each object has
a row for every virtual link according to the proper
ifIndex. Typically the number of expected virtual link
in a PON is like the number of ONUs 32-64 plus an
additional entry for broadcast LLID (which is marked by
0xffff). In the [802.3ah] the LLID is a 2bytes register
and the number of LLIDs is limited by that."
::= { dot3EponMpcpObjects 2 }
dot3MpcpStatEntry OBJECT-TYPE
SYNTAX Dot3MpcpStatEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table entries for the table of statistics counters of
[802.3ah] clause 64 MPCP interface.
Rows in the table are created when ifIndexs are created.
For the ONU rows are created at system initialization.
Khermosh Expires August 14, 2006 [Page 36]
Internet-Draft Managed Objects of EPON February 2006
For the OLT the rows of the OLT ifIndex and the row of
the ifIndex referring to the broadcast virtual link are
created at system initialization. For the ifIndexs
referring to the virtual links at the OLT, a row is
created when a virtual link is established (ONU
registers) and deleted when the virtual link is deleted
(ONU deregisters). Rows exist for an OLT interface and
an ONU interface."
INDEX { ifIndex}
::= { dot3MpcpStatTable 1 }
Dot3MpcpStatEntry ::=
SEQUENCE {
dot3MpcpMACCtrlFramesTransmitted Counter64,
dot3MpcpMACCtrlFramesReceived Counter64,
dot3MpcpDiscoveryWindowsSent Counter32,
dot3MpcpDiscoveryTimeout Counter32,
dot3MpcpTxRegRequest Counter64,
dot3MpcpRxRegRequest Counter64,
dot3MpcpTxRegAck Counter64,
dot3MpcpRxRegAck Counter64,
dot3MpcpTxReport Counter64,
dot3MpcpRxReport Counter64,
dot3MpcpTxGate Counter64,
dot3MpcpRxGate Counter64,
dot3MpcpTxRegister Counter64,
dot3MpcpRxRegister Counter64
}
dot3MpcpMACCtrlFramesTransmitted OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of MPCP frames passed to the MAC sublayer for
transmission. This counter is incremented when a
MA_CONTROL.request service primitive is generated within
the MAC control sublayer with an opcode indicating a
MPCP frame.
This counter is relevant for an OLT and an ONU. For
the OLT there is a value per LLID."
REFERENCE "[802.3ah], 30.3.5.1.7."
::= { dot3MpcpStatEntry 1 }
dot3MpcpMACCtrlFramesReceived OBJECT-TYPE
SYNTAX Counter64
Khermosh Expires August 14, 2006 [Page 37]
Internet-Draft Managed Objects of EPON February 2006
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of MPCP frames passed by the MAC sublayer to the
MAC Control sublayer. This counter is incremented when a
ReceiveFrame function call returns a valid frame with:
(1) a lengthOrType field value equal to the reserved
Type for 802.3_MAC_Control as specified in 31.4.1.3, and
(2) an opcode indicating a MPCP frame.
This counter is relevant for an OLT and an ONU. For
the OLT there is a value per LLID."
REFERENCE "[802.3ah], 30.3.5.1.8."
::= { dot3MpcpStatEntry 2}
dot3MpcpDiscoveryWindowsSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of discovery windows generated. The counter is
incremented by one for each generated discovery window.
This counter is relevant for an OLT and an ONU. For
the OLT there is a value per LLID. At the ONU value
should be zero."
REFERENCE "[802.3ah], 30.3.5.1.22."
::= { dot3MpcpStatEntry 3}
dot3MpcpDiscoveryTimeout OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the number of times a discovery timeout
occurs. Increment the counter by one for each discovery
processing state-machine reset resulting from timeout
waiting for message arrival.
This counter is relevant for an OLT and an ONU. For
the OLT there is a value per LLID."
REFERENCE "[802.3ah], 30.3.5.1.23."
::= { dot3MpcpStatEntry 4}
dot3MpcpTxRegRequest OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
Khermosh Expires August 14, 2006 [Page 38]
Internet-Draft Managed Objects of EPON February 2006
DESCRIPTION
"A count of the number of times a REGISTER_REQ MPCP
frames transmission occurs. Increment the counter by one
for each REGISTER_REQ MPCP frame transmitted as defined
in [802.3ah] clause 64. This counter is mandatory for an
ONU. This counter is relevant for an OLT and an ONU.
For the OLT there is a value per LLID. At the OLT value
should be zero."
REFERENCE "[802.3ah], 30.3.5.1.12."
::= { dot3MpcpStatEntry 5}
dot3MpcpRxRegRequest OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the number of times a REGISTER_REQ MPCP
frames reception occurs. A single counter at the ONU and
a set of counters, one for each LLID, at the OLT.
Increment the counter by one for each REGISTER_REQ MPCP
frame received for each LLID as defined in [802.3ah]
clause 64. This counter is mandatory for an ONU and for
an OLT. For the OLT there is a value per LLID.
At the ONU value should be zero."
REFERENCE "[802.3ah], 30.3.5.1.17."
::= { dot3MpcpStatEntry 6}
dot3MpcpTxRegAck OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the number of times a REGISTER_ACK MPCP
frames transmission occurs. Increment the counter by one
for each REGISTER_ACK MPCP frame transmitted as defined
in [802.3ah] clause 64. This counter is mandatory for an
ONU. This object is relevant for an OLT and an ONU.
For the OLT there is a value per LLID. At the OLT the
value should be zero."
REFERENCE "[802.3ah], 30.3.5.1.10."
::= { dot3MpcpStatEntry 7}
dot3MpcpRxRegAck OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
Khermosh Expires August 14, 2006 [Page 39]
Internet-Draft Managed Objects of EPON February 2006
STATUS current
DESCRIPTION
"A count of the number of times a REGISTER_ACK MPCP
frames reception occurs. A single counter at the ONU and
a set of counters, one for each LLID, at the OLT.
Increment the counter by one for each REGISTER_ACK MPCP
frame received for each LLID, as defined in [802.3ah]
clause 64. This counter is mandatory for an ONU and for
an OLT. For the OLT there is a value per LLID.
At the ONU the value should be zero."
REFERENCE "[802.3ah], 30.3.5.1.15."
::= { dot3MpcpStatEntry 8}
dot3MpcpTxReport OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the number of times a REPORT MPCP frames
transmission occurs. Increment the counter by one for
each REPORT MPCP frame transmitted as defined in
[802.3ah] clause 64. This counter is mandatory for an
ONU. This counter is relevant for an OLT and an ONU.
For the OLT there is a value per LLID.
At the OLT value should be zero."
REFERENCE "[802.3ah], 30.3.5.1.13."
::= { dot3MpcpStatEntry 9}
dot3MpcpRxReport OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the number of times a REPORT MPCP frames
reception occurs. A single counter at the ONU and a set
of counters, one for each LLID, at the OLT. Increment
the counter by one for each REPORT MPCP frame received
for each LLID, as defined in [802.3ah] clause 64.
This counter is mandatory for an ONU and for an OLT.
For the OLT there is a value per LLID.
At the ONU value should be zero."
REFERENCE "[802.3ah], 30.3.5.1.18."
::= { dot3MpcpStatEntry 10}
dot3MpcpTxGate OBJECT-TYPE
SYNTAX Counter64
Khermosh Expires August 14, 2006 [Page 40]
Internet-Draft Managed Objects of EPON February 2006
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the number of times a GATE MPCP frames
transmission occurs. A set of counters, one for each
LLID, at the OLT. Increment the counter by one for each
GATE MPCP frame transmitted, for each LLID, as defined
in [802.3ah] clause 64. This counter is mandatory for an
OLT. This counter is relevant for an OLT and an ONU.
For the OLT there is a value per LLID.
At the ONU the value should be zero."
REFERENCE "[802.3ah], 30.3.5.1.9."
::= { dot3MpcpStatEntry 11}
dot3MpcpRxGate OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the number of times a GATE MPCP frames
reception occurs. A single counter at the ONU and a set
of counters, one for each LLID ,at the OLT. Increment
the counter by one for each GATE MPCP frame received,
for each LLID, as defined in [802.3ah] clause 64. This
counter is mandatory for an ONU and for an OLT. For the
OLT there is a value per LLID. At the OLT the value
should be zero."
REFERENCE "[802.3ah], 30.3.5.1.14."
::= { dot3MpcpStatEntry 12}
dot3MpcpTxRegister OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the number of times a REGISTER MPCP frames
transmission occurs. A set of counters, one for each
LLID, at the OLT. Increment the counter by one for each
REGISTER MPCP frame transmitted, for each LLID, as
defined in [802.3ah] clause 64. This counter is
mandatory for an OLT. This counter is relevant for an
OLT and an ONU. For the OLT there is a value per LLID.
At the ONU the value should be zero."
REFERENCE "[802.3ah], 30.3.5.1.11."
::= { dot3MpcpStatEntry 13}
Khermosh Expires August 14, 2006 [Page 41]
Internet-Draft Managed Objects of EPON February 2006
dot3MpcpRxRegister OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the number of times a REGISTER MPCP frames
reception occurs. A single counter at the ONU and a set
of counters, one for each LLID, at the OLT. Increment
the counter by one for each REGISTER MPCP frame
received, for each LLID, as defined in [802.3ah] clause
64. This counter is mandatory for an ONU and for an OLT.
For the OLT there is a value per LLID.
at the OLT the value should be zero."
REFERENCE "[802.3ah], 30.3.5.1.16."
::= { dot3MpcpStatEntry 14}
-- OMPEmulation managed object definitions
dot3OmpEmulationObjects OBJECT IDENTIFIER ::={dot3EponObjects 2}
dot3OmpEmulationTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OmpEmulationEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table for dot3 OmpEmulation MIB objects. The table
defines the parameter settings of the OMP Emulation
layer. Each object has a row for every virtual link
according to the proper ifIndex. Typically the number
of expected virtual link in a PON is like the number of
ONUs 32-64 plus an additional entry for broadcast LLID
(which is marked by 0xffff). In the [802.3ah] the LLID
is a 2bytes register and the number of LLIDs limited by
that."
::= { dot3OmpEmulationObjects 1 }
dot3OmpEmulationEntry OBJECT-TYPE
SYNTAX Dot3OmpEmulationEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the dot3 OmpEmulation table.
Khermosh Expires August 14, 2006 [Page 42]
Internet-Draft Managed Objects of EPON February 2006
Rows in the table are created when ifIndexs are created.
For the ONU rows are created at system initialization.
For the OLT the rows of the OLT ifIndex and the row of
the ifIndex referring to the broadcast virtual link are
created at system initialization. For the ifIndexs
referring to the virtual links at the OLT, a row is
created when a virtual link is established (ONU
registers) and deleted when the virtual link is deleted
(ONU deregisters). Rows exist for an OLT interface and
an ONU interface."
INDEX { ifIndex }
::= { dot3OmpEmulationTable 1 }
Dot3OmpEmulationEntry ::=
SEQUENCE {
dot3OmpEmulationType INTEGER
}
dot3OmpEmulationType OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
olt(2),
onu(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A value that indicates that mode of operation
of the Reconciliation Sublayer for Point to Point
Emulation (see [802.3ah] clause 65.1). unknown(1) value
is assigned in initializing, true state or type not yet
known. olt(2) value is assigned when Sublayer operating
in OLT mode. onu(3) value is assigned when Sublayer
operating in ONU mode.
This object is relevant for an OLT, same for all
virtual links, and for an ONU."
REFERENCE "[802.3ah], 30.3.7.1.2."
::= { dot3OmpEmulationEntry 1}
dot3OmpEmulationStatTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OmpEmulationStatEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table defines the list of statistics counters for
[802.3ah] clause 65 OMP interface.
Each object has a row for every virtual link
according to the proper ifIndex. Typically the number
Khermosh Expires August 14, 2006 [Page 43]
Internet-Draft Managed Objects of EPON February 2006
of expected virtual link in a PON is like the number of
ONUs 32-64 plus an additional entry for broadcast LLID
(which is marked by 0xffff). In the [802.3ah] the LLID
is a 2bytes register and the number of LLIDs limited by
that."
::= { dot3OmpEmulationObjects 2}
dot3OmpEmulationStatEntry OBJECT-TYPE
SYNTAX Dot3OmpEmulationStatEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table entries for the table of statistics counters of
[802.3ah] clause 65 OMP interface.
Rows in the table are created when ifIndexs are created.
For the ONU rows are created at system initialization.
For the OLT the rows of the OLT ifIndex and the row of
the ifIndex referring to the broadcast virtual link are
created at system initialization. For the ifIndexs
referring to the virtual links at the OLT, a row is
created when a virtual link is established (ONU
registers) and deleted when the virtual link is deleted
(ONU deregisters). Rows exist for an OLT interface and
an ONU interface."
INDEX { ifIndex}
::= { dot3OmpEmulationStatTable 1 }
Dot3OmpEmulationStatEntry::=
SEQUENCE {
dot3OmpEmulationSLDErrors Counter64,
dot3OmpEmulationCRC8Errors Counter64,
dot3OmpEmulationBadLLID Counter64,
dot3OmpEmulationGoodLLID Counter64,
dot3OmpEmulationOnuPonCastLLID Counter64,
dot3OmpEmulationOltPonCastLLID Counter64,
dot3OmpEmulationBroadcastBitNotOnuLlid Counter64,
dot3OmpEmulationOnuLLIDNotBroadcast Counter64,
dot3OmpEmulationBroadcastBitPlusOnuLlid Counter64,
dot3OmpEmulationNotBroadcastBitNotOnuLlid Counter64
}
dot3OmpEmulationSLDErrors OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of frames received that do not contain a valid
Khermosh Expires August 14, 2006 [Page 44]
Internet-Draft Managed Objects of EPON February 2006
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
OLT there is a value per LLID."
REFERENCE "[802.3ah], 30.3.7.1.3."
::= { dot3OmpEmulationStatEntry 1}
dot3OmpEmulationCRC8Errors OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of frames received that contain a valid SLD
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
65.1.3.3.3.
This counter is relevant for an OLT and an ONU. For the
OLT there is a value per LLID."
REFERENCE "[802.3ah], 30.3.7.1.4."
::= { dot3OmpEmulationStatEntry 2}
dot3OmpEmulationBadLLID OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of frames received that contain a valid SLD
field, as defined in [802.3ah] clause 65.1.3.3.1, and
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
defined in [802.3ah] clause 65.1.3.3.2.
This counter is relevant for an OLT and an ONU. For the
OLT there is a value per LLID."
REFERENCE "[802.3ah], 30.3.7.1.8."
::= { dot3OmpEmulationStatEntry 3}
dot3OmpEmulationGoodLLID OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of frames received that contain a valid SLD
field, as defined in [802.3ah] clause 65.1.3.3.1, and
pass the CRC-8 check, as defined in [802.3ah] clause
65.1.3.3.3.
Khermosh Expires August 14, 2006 [Page 45]
Internet-Draft Managed Objects of EPON February 2006
This counter is relevant for an OLT and an ONU. For the
OLT there is a value per LLID."
REFERENCE "[802.3ah], 30.3.7.1.5."
::= { dot3OmpEmulationStatEntry 4}
dot3OmpEmulationOnuPonCastLLID OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of frames received that contain a valid SLD
field in an ONU, as defined in [802.3ah] 65.1.3.3.1,
passes the CRC-8 check, as defined in [802.3ah]
65.1.3.3.3, and the frame meets the rule for acceptance
defined in [802.3ah] 65.1.3.3.2.
This counter is relevant for an OLT and an ONU. For the
OLT there is a value per LLID.
The value is zero for an OLT."
REFERENCE "[802.3ah], 30.3.7.1.6."
::= { dot3OmpEmulationStatEntry 5}
dot3OmpEmulationOltPonCastLLID OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of frames received that contain a valid SLD
field in an OLT, as defined in [802.3ah] 65.1.3.3.1,
passes the CRC-8 check, as defined in [802.3ah]
65.1.3.3.3, and the frame meets the rule for acceptance
defined in [802.3ah] 65.1.3.3.2.
This counter is relevant for an OLT and an ONU. For the
OLT there is a value per LLID.
The value is zero for an ONU."
REFERENCE "[802.3ah], 30.3.7.1.7."
::= { dot3OmpEmulationStatEntry 6}
dot3OmpEmulationBroadcastBitNotOnuLlid OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of frames received that contain a valid SLD
field in a OLT, as defined in [802.3ah] clause
Khermosh Expires August 14, 2006 [Page 46]
Internet-Draft Managed Objects of EPON February 2006
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
in LLID and not the ONU's LLID (frame accepted) as
defined in [802.3ah] clause 65.
This counter is relevant for an OLT and an ONU. For the
OLT there is a value per LLID."
::= { dot3OmpEmulationStatEntry 7}
dot3OmpEmulationOnuLLIDNotBroadcast OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of frames received that contain a valid SLD
field in a OLT, as defined in [802.3ah] clause
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
as defined in [802.3ah] clause 65. This object is
This counter is relevant for an OLT and an ONU. For the
OLT there is a value per LLID."
::= { dot3OmpEmulationStatEntry 8}
dot3OmpEmulationBroadcastBitPlusOnuLlid OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of frames received that contain a valid SLD
field in a OLT, as defined in [802.3ah] clause
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
bit in LLID and the ONU's LLID (frame reflected) as
defined in [802.3ah] clause 65.
This counter is relevant for an OLT and an ONU. For the
OLT there is a value per LLID."
::= { dot3OmpEmulationStatEntry 9}
dot3OmpEmulationNotBroadcastBitNotOnuLlid OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of frames received that contain a valid SLD
field in a OLT, as defined in [802.3ah] clause
65.1.3.3.1, and pass the CRC-8 check, as defined in
Khermosh Expires August 14, 2006 [Page 47]
Internet-Draft Managed Objects of EPON February 2006
[802.3ah] clause 65.1.3.3.3, and does not contain
the ONU's LLID as defined in [802.3ah] clause 65.
This object is mandatory for an ONU"
::= { dot3OmpEmulationStatEntry 10}
-- FEC managed object definitions (30.5.1)
dot3EponFecObjects OBJECT IDENTIFIER ::={dot3EponObjects 3}
dot3EponFecTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3EponFecEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table for dot3 EPON FEC management objects.
The entries in the table are control and status entities
and statistic counters for the FEC layer.
Each object has a row for every virtual link
according to the proper ifIndex. Typically the number
of expected virtual link in a PON is like the number of
ONUs 32-64 plus an additional entry for broadcast LLID
(which is marked by 0xffff). In the [802.3ah] the LLID
is a 2bytes register and the number of LLIDs limited by
that."
::= { dot3EponFecObjects 1 }
dot3EponFecEntry OBJECT-TYPE
SYNTAX Dot3EponFecEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the dot3 EPON FEC table. The Rows in the
table are created when ifIndexs are created.
For the ONU rows are created at system initialization.
For the OLT the rows of the OLT ifIndex and the row of
the ifIndex referring to the broadcast virtual link are
created at system initialization. For the ifIndexs
referring to the virtual links at the OLT, a row is
created when a virtual link is established (ONU
registers) and deleted when the virtual link is deleted
(ONU deregisters). Rows exist for an OLT interface and
an ONU interface."
INDEX { ifIndex}
::= { dot3EponFecTable 1 }
Khermosh Expires August 14, 2006 [Page 48]
Internet-Draft Managed Objects of EPON February 2006
Dot3EponFecEntry ::=
SEQUENCE {
dot3EponFecPCSCodingViolation Counter64,
dot3EponFecAbility INTEGER,
dot3EponFecMode INTEGER,
dot3EponFecCorrectedBlocks Counter64,
dot3EponFecUncorrectableBlocks Counter64,
dot3EponFecBufferHeadCodingViolation Counter64
}
dot3EponFecPCSCodingViolation OBJECT-TYPE
SYNTAX Counter64
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"For 100 Mb/ s operation it is a count of the number of
times an invalid code-group is received, other than the
/H/ code-group. For 1000 Mb/ s operation it is a count
of the number of times an invalid codegroup is received,
other than the /V/ code-group. /H/ and /V/ denote
special 8b10b codewords of the [802.3] PCS layer (clause
36)."
REFERENCE "[802.3ah], 30.5.1.1.12."
::= { dot3EponFecEntry 1}
dot3EponFecAbility OBJECT-TYPE
SYNTAX INTEGER {
unknown (1),
unsupported (2),
supported (3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A value that indicates the support of
operation of the 1000BASE-PX PHY optional FEC Sublayer
for Forward error correction see [802.3ah] clause
65.2).
unknown(1) value is assigned in initializing, for non
FEC support state or type not yet known. unsupported(2)
value is assigned when Sublayer is not support.
supported(3) value is assigned when Sublayer is
supported."
REFERENCE "[802.3ah], 30.5.1.1.13."
::= { dot3EponFecEntry 2}
dot3EponFecMode OBJECT-TYPE
Khermosh Expires August 14, 2006 [Page 49]
Internet-Draft Managed Objects of EPON February 2006
SYNTAX INTEGER {
unknown (1),
disabled (2),
enabled (3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A read-write value that indicates the mode of operation
of the 1000BASE-PX PHY optional FEC Sublayer for Forward
error correction see [802.3ah] clause 65.2).
A GET operation returns the current mode of operation
the PHY. A SET operation changes the mode of operation
of the PHY to the indicated value. unknown(1) value is
assigned in initializing, for non FEC support state or
type not yet known. disabled(2) value is assigned when
Sublayer operating in disabled mode. enabled(3) value is
assigned when Sublayer operating in FEC mode. writing
can be done at any time."
REFERENCE "[802.3ah], 30.5.1.1.14."
DEFVAL { 1 }
::= { dot3EponFecEntry 3}
dot3EponFecCorrectedBlocks OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"For 10PASS-TS, 2BASE-TL and 1000BASE-PX PHYs, a count
of corrected FEC blocks. This counter will not increment
for other PHY Types. Increment the counter by one for
each received block that is corrected by the FEC
function in the PHY."
REFERENCE "[802.3ah], 30.5.1.1.15."
::= { dot3EponFecEntry 4}
dot3EponFecUncorrectableBlocks OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"For 10PASS-TS, 2BASE-TL and 1000BASE-PX PHYs, a count of
uncorrectable FEC blocks. This counter will not
increment for other PHY Types. Increment the counter by
one for each FEC block that is determined to be
uncorrectable by the FEC function in the PHY."
REFERENCE "[802.3ah], 30.5.1.1.16."
::= { dot3EponFecEntry 5}
Khermosh Expires August 14, 2006 [Page 50]
Internet-Draft Managed Objects of EPON February 2006
dot3EponFecBufferHeadCodingViolation OBJECT-TYPE
SYNTAX Counter64
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"For 1000 Mbps operation it is a counts of the number of
invalid code-group received directly from the link."
::= { dot3EponFecEntry 6}
-- ExtendedPackage managed object definitions
dot3ExtPkgObjects OBJECT IDENTIFIER ::={dot3EponObjects 4}
dot3ExtPkgControlObjects OBJECT IDENTIFIER ::= { dot3ExtPkgObjects 1}
dot3ExtPkgControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3ExtPkgControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table for Extended package Control management
objects. Entries are control and status indication
objects for an EPON interface which are gathered in an
extended package as an addition for the [802.3ah]
attributes.
Each object has a row for every virtual link
according to the proper ifIndex. Typically the number
of expected virtual link in a PON is like the number of
ONUs 32-64 plus an additional entry for broadcast LLID
(which is marked by 0xffff). In the [802.3ah] the LLID
is a 2bytes register and the number of LLIDs limited by
that."
::= { dot3ExtPkgControlObjects 1 }
dot3ExtPkgControlEntry OBJECT-TYPE
SYNTAX Dot3ExtPkgControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Extended package Control table.
Rows in the table are created when ifIndexs are created.
For the ONU rows are created at system initialization.
For the OLT the rows of the OLT ifIndex and the row of
Khermosh Expires August 14, 2006 [Page 51]
Internet-Draft Managed Objects of EPON February 2006
the ifIndex referring to the broadcast virtual link are
created at system initialization. For the ifIndexs
referring to the virtual links at the OLT, a row is
created when a virtual link is established (ONU
registers) and deleted when the virtual link is deleted
(ONU deregisters). Rows exist for an OLT interface and
an ONU interface."
INDEX { ifIndex}
::= { dot3ExtPkgControlTable 1 }
Dot3ExtPkgControlEntry ::=
SEQUENCE {
dot3ExtPkgObjectReset INTEGER,
dot3ExtPkgObjectPowerDown TruthValue,
dot3ExtPkgObjectNumberOfLLIDs Unsigned32,
dot3ExtPkgObjectFecEnabled INTEGER,
dot3ExtPkgObjectReportMaximumNumQueues Unsigned32,
dot3ExtPkgObjectRegisterAction INTEGER
}
dot3ExtPkgObjectReset OBJECT-TYPE
SYNTAX INTEGER {
running(1),
reset(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable is used to reset the EPON interface. The
interface may be unavailable while the reset occurs and
data may be lost. During reading operation it returns
the state of the EPON interface. running(1) indicates
and operates normal operation, reset(2) indicates and
operates reset mode. Writing can be done at any time.
This object is relevant for an OLT, same for all
virtual links, and for an ONU."
DEFVAL { 1 }
::= { dot3ExtPkgControlEntry 1 }
dot3ExtPkgObjectPowerDown OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Setting this variable to true(1) will cause the
interface to be entered into Power down mode. Setting
this variable to false(2) will cause the interface to go
out of power down mode. When getting true(1) the
Khermosh Expires August 14, 2006 [Page 52]
Internet-Draft Managed Objects of EPON February 2006
interface is in power down. When getting false(2) the
interface is not in power down.
Writing can be done at any time.
The variable is relevant when the admin state of the
device is active as set by the dot3MpcpAdminState.
This object is relevant for an OLT, same for all
virtual links, and for an ONU."
DEFVAL { false }
::= { dot3ExtPkgControlEntry 2 }
dot3ExtPkgObjectNumberOfLLIDs OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A read only variable which defines the number of
registered LLIDs (as defined by the [802.3ah] clause 65)
in a EPON network for an OLT and an ONU. Initialization
value is 0.
This object is relevant for an OLT and an ONU.
Typically the number of expected virtual link in a PON
is like the number of ONUs 32-64 plus an additional
entry for broadcast LLID (which is marked by 0xffff). 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 for an interface is one.
This object is relevant for an OLT, same for all
virtual links, and for an ONU."
::= { dot3ExtPkgControlEntry 3 }
dot3ExtPkgObjectFecEnabled OBJECT-TYPE
SYNTAX INTEGER {
noFecEnabled (1),
fecTxEnabled (2),
fecRxEnabled (3),
fecTxRxEnabled (4)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable defines and provides information whether the
EPON interface uses FEC as defined in the [802.3ah] clause
65.2 for EPON. When noFECEnabled(1) the interface does not
support FEC mode. When fecTxEnabled(2) the interface
supports the FEC transmission mode. When fecRxEnabled(3)
Khermosh Expires August 14, 2006 [Page 53]
Internet-Draft Managed Objects of EPON February 2006
the interface supports the FEC Receive mode. When
fecTxRxEnabled(4) the interface supports the FEC
transmission and receive mode.
Writing can be done at any time.
This object is relevant for an OLT and an ONU. For the
OLT there is a value per LLID."
DEFVAL { 1 }
::= { dot3ExtPkgControlEntry 4 }
dot3ExtPkgObjectReportMaximumNumQueues OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An integer for each LLID, that defines the
maximal number of queues in the REPORT message, as
defined in [802.3ah] 64.
This object is relevant for an OLT and an ONU. For the
OLT there is a value per LLID."
DEFVAL { 0 }
::= { dot3ExtPkgControlEntry 5 }
dot3ExtPkgObjectRegisterAction OBJECT-TYPE
SYNTAX INTEGER {
none (1),
register (2),
deregister (3),
reregister (4)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A list of actions for an entry - LLID. Indicates and
defines the state of registration for the remote
interface.
none(1) marks no action, register(2) marks to register
an LLID, deregister(3) marks to deregister an LLID,
reregister(4) marks reregistered LLID.
This object is relevant for an OLT and an ONU. For the
OLT there is a value per LLID."
DEFVAL { 1 }
::= { dot3ExtPkgControlEntry 6 }
dot3ExtPkgQueueTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3ExtPkgQueueEntry
MAX-ACCESS not-accessible
Khermosh Expires August 14, 2006 [Page 54]
Internet-Draft Managed Objects of EPON February 2006
STATUS current
DESCRIPTION
"A table for extended package Queue management objects.
The [802.3ah] MPCP uses for the feedback BW request from
the ONUs a report of some queues occupancy. These queues
serve the ONU transmission and data is gathered there
until the ONU is granted for transmission. Since the
existence of such queuing mechanism is implied in the
[802.3ah] spec and an ONU may not be a switch device,
a management section is added here for the queues,
mainly to gather some statistics of their operation.
Entries are control and status indication
objects for an EPON interface which are gathered in an
extended package as an addition for the [802.3ah]
attributes. The objects in this table are specific for
the queues which are reported in the MPCP REPORT message
as defined in [802.3ah] clause 64.
Each object has a row for every virtual link and for
every queue in the report. Typically the number of
expected virtual link in a PON is like the number of
ONUs 32-64 plus an additional entry for broadcast LLID
(which is marked by 0xffff). In the [802.3ah] the LLID
is a 2bytes register and the number of LLIDs limited by
that.
The number of queues is between 0 and 7 and limited by
dot3ExtPkgObjectReportMaximumNumQueues."
::= { dot3ExtPkgControlObjects 2 }
dot3ExtPkgQueueEntry OBJECT-TYPE
SYNTAX Dot3ExtPkgQueueEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Extended package Queue table. The rows
are added for each ifIndex and dot3QueueIndex at the
OLT. At the ONU the rows are added for each
dot3QueueIndex and a single row of ifIndex.
Rows in the table are created when ifIndexs are created.
For the ONU rows are created at system initialization.
For the OLT the rows of the OLT ifIndex and the row of
the ifIndex referring to the broadcast virtual link are
created at system initialization. For the ifIndexs
referring to the virtual links at the OLT, a row is
created when a virtual link is established (ONU
registers) and deleted when the virtual link is deleted
(ONU deregisters). Rows exist for an OLT interface and
an ONU interface."
INDEX { ifIndex, dot3QueueIndex }
Khermosh Expires August 14, 2006 [Page 55]
Internet-Draft Managed Objects of EPON February 2006
::= { dot3ExtPkgQueueTable 1 }
Dot3ExtPkgQueueEntry ::=
SEQUENCE {
dot3QueueIndex Unsigned32,
dot3ExtPkgObjectReportNumThreshold Unsigned32,
dot3ExtPkgObjectReportMaximumNumThreshold Unsigned32,
dot3ExtPkgStatTxFramesQueue Counter64,
dot3ExtPkgStatRxFramesQueue Counter64,
dot3ExtPkgStatDroppedFramesQueue Counter64
}
dot3QueueIndex OBJECT-TYPE
SYNTAX Unsigned32 (0..7)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A value that identifies the queue index for the queue
table. The queues are 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
dot3ExtPkgObjectReportMaximumNumQueues."
::= { dot3ExtPkgQueueEntry 1 }
dot3ExtPkgObjectReportNumThreshold OBJECT-TYPE
SYNTAX Unsigned32 (0..7)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"An integers for each LLID, that defines the
number of thresholds for each Queue in the REPORT
message, as defined in [802.3ah] 64. Each Queue set
reporting will provide information on the queue
occupancy of frames below the matching Threshold.
Writing can be done at any time.
This object is relevant for an OLT and an ONU. For the
OLT there is a value per LLID."
DEFVAL { 0 }
::= { dot3ExtPkgQueueEntry 2 }
dot3ExtPkgObjectReportMaximumNumThreshold OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An integer for each LLID, that defines the
Khermosh Expires August 14, 2006 [Page 56]
Internet-Draft Managed Objects of EPON February 2006
maximal number of thresholds for each Queue in the
REPORT message, as defined in [802.3ah] 64. Each Queue
set reporting will provide information on the queue
occupancy of frames below the matching Threshold.
This object is relevant for an OLT and an ONU. For the
OLT there is a value per LLID."
DEFVAL { 0 }
::= { dot3ExtPkgQueueEntry 3 }
dot3ExtPkgStatTxFramesQueue OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the number of times a relevant 'Queue' frames
transmission occurs. Increment the counter by one for
each frame transmitted which is an output of the
'Queue'.
The 'Queue' marking matched the REPORT MPCP message
Queue field, as defined in [802.3ah] clause 64. This
counter is mandatory for an ONU only."
::= { dot3ExtPkgQueueEntry 4}
dot3ExtPkgStatRxFramesQueue OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the number of times a relevant 'Queue' frames
reception occurs. Increment the counter by one for each
frame received, which is an output of 'Queue'. The
'Queue' marking matched the REPORT MPCP message
Queue field, as defined in [802.3ah] clause 64.
This counter is mandatory for an ONU only."
::= { dot3ExtPkgQueueEntry 5}
dot3ExtPkgStatDroppedFramesQueue OBJECT-TYPE
SYNTAX Counter64
UNITS "frames"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the number of times a relevant 'Queue' frames
drops occurs. Increment the counter by one for each
Khermosh Expires August 14, 2006 [Page 57]
Internet-Draft Managed Objects of EPON February 2006
frame dropped from 'Queue'. The 'Queue' marking matched
the REPORT MPCP message Queue field, as defined in
[802.3ah] clause 64.
This counter is mandatory for an ONU only."
::= { dot3ExtPkgQueueEntry 6}
dot3ExtPkgQueueSetsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3ExtPkgQueueSetsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table for Extended package Queue_Sets management
objects. Entries are control and status indication
objects for an EPON interface which are gathered in an
extended package as an addition for the [802.3ah]
attributes. The objects in this table are specific for
the queue-sets which are reported in the MPCP REPORT
message as defined in [802.3ah] clause 64.
Each object has a row for every virtual link and for
each queue in the report and for each queue_set in the
queue. Typically the number of expected virtual link in
a PON is like the number of ONUs 32-64 plus an
additional entry for broadcast LLID (which is marked by
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
dot3ExtPkgObjectReportMaximumNumQueues.
The number of queues_sets is between 0 and 7 and limited
by dot3ExtPkgObjectReportMaximumNumThreshold."
::= { dot3ExtPkgControlObjects 3 }
dot3ExtPkgQueueSetsEntry OBJECT-TYPE
SYNTAX Dot3ExtPkgQueueSetsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Extended package Queue sets table. The
rows are added for each ifIndex, dot3QueueSetQueueIndex
and dot3QueueSetIndex at the OLT.
At the ONU the rows are added for each
dot3QueueSetQueueIndex, dot3QueueSetIndex and a single
row for the ifIndex.
Rows in the table are created when ifIndexs are created.
For the ONU rows are created at system initialization.
Khermosh Expires August 14, 2006 [Page 58]
Internet-Draft Managed Objects of EPON February 2006
For the OLT the rows of the OLT ifIndex and the row of
the ifIndex referring to the broadcast virtual link are
created at system initialization. For the ifIndexs
referring to the virtual links at the OLT, a row is
created when a virtual link is established (ONU
registers) and deleted when the virtual link is deleted
(ONU deregisters). Rows exist for an OLT interface and
an ONU interface."
INDEX { ifIndex,
dot3QueueSetQueueIndex,dot3QueueSetIndex}
::= { dot3ExtPkgQueueSetsTable 1 }
Dot3ExtPkgQueueSetsEntry ::=
SEQUENCE {
dot3QueueSetQueueIndex Unsigned32,
dot3QueueSetIndex Unsigned32,
dot3ExtPkgObjectReportThreshold Unsigned32
}
dot3QueueSetQueueIndex OBJECT-TYPE
SYNTAX Unsigned32 (0..7)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A value that identifies the queue index for the queue
set table. The queues are 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
dot3ExtPkgObjectReportMaximumNumQueues.
Value corresponds to the dot3QueueIndex of the queue
table."
::= { dot3ExtPkgQueueSetsEntry 1 }
dot3QueueSetIndex OBJECT-TYPE
SYNTAX Unsigned32 (0..7)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A value that identifies the queue_set index for the
queue_sets table. The queues are reported in the MPCP
REPORT message as defined in [802.3ah] clause 64.
The number of queues_sets is between 0 and 7."
::= { dot3ExtPkgQueueSetsEntry 2 }
dot3ExtPkgObjectReportThreshold OBJECT-TYPE
SYNTAX Unsigned32
UNITS "TQ (16nsec)"
Khermosh Expires August 14, 2006 [Page 59]
Internet-Draft Managed Objects of EPON February 2006
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"An integer that defines the threshold reporting for each
Queue_set in the REPORT message, as defined in [802.3ah]
64. The number of sets is
dot3ExtPkgObjectReportNumThreshold. Each Queue set
reporting will provide information on the queue
occupancy of frames below the matching Threshold.
The value returned shall be in Time quanta (TQ) which
is 16nsec or 2 octets increments.
Writing can be done at any time.
This object is relevant for an OLT and an ONU. For the
OLT there is a value per LLID."
DEFVAL { 0 }
::= { dot3ExtPkgQueueSetsEntry 3 }
--Optical Interface status tables
dot3ExtPkgOptIfTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3ExtPkgOptIfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table defines the list of status control and status
indication for the optical interface of an EPON
interface.
Each object has a row for every virtual link
according to the proper ifIndex. Typically the number
of expected virtual link in a PON is like the number of
ONUs 32-64 plus an additional entry for broadcast LLID
(which is marked by 0xffff). In the [802.3ah] the LLID
is a 2bytes register and the number of LLIDs limited by
that."
::= { dot3ExtPkgControlObjects 5}
dot3ExtPkgOptIfEntry OBJECT-TYPE
SYNTAX Dot3ExtPkgOptIfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table entries for the Table of optical interfaces
control and status indication of EPON interfaces.
Rows in the table are created when ifIndexs are created.
For the ONU rows are created at system initialization.
For the OLT the rows of the OLT ifIndex and the row of
Khermosh Expires August 14, 2006 [Page 60]
Internet-Draft Managed Objects of EPON February 2006
the ifIndex referring to the broadcast virtual link are
created at system initialization. For the ifIndexs
referring to the virtual links at the OLT, a row is
created when a virtual link is established (ONU
registers) and deleted when the virtual link is deleted
(ONU deregisters). Rows exist for an OLT interface and
an ONU interface."
INDEX { ifIndex }
::= { dot3ExtPkgOptIfTable 1 }
Dot3ExtPkgOptIfEntry ::=
SEQUENCE {
dot3ExtPkgOptIfSuspectedFlag TruthValue,
dot3ExtPkgOptIfInputPower Integer32,
dot3ExtPkgOptIfLowInputPower Integer32,
dot3ExtPkgOptIfHighInputPower Integer32,
dot3ExtPkgOptIfLowerInputPowerThreshold Integer32,
dot3ExtPkgOptIfUpperInputPowerThreshold Integer32,
dot3ExtPkgOptIfOutputPower Integer32,
dot3ExtPkgOptIfLowOutputPower Integer32,
dot3ExtPkgOptIfHighOutputPower Integer32,
dot3ExtPkgOptIfLowerOutputPowerThreshold Integer32,
dot3ExtPkgOptIfUpperOutputPowerThreshold Integer32,
dot3ExtPkgOptIfSignalDetect TruthValue,
dot3ExtPkgOptIfTransmitAlarm TruthValue,
dot3ExtPkgOptIfTransmitEnable TruthValue
}
dot3ExtPkgOptIfSuspectedFlag OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If true, the data in this entry may be unreliable."
::= { dot3ExtPkgOptIfEntry 1 }
dot3ExtPkgOptIfInputPower OBJECT-TYPE
SYNTAX Integer32
UNITS "0.1 dbm"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The optical power monitored at the input."
::= { dot3ExtPkgOptIfEntry 2 }
dot3ExtPkgOptIfLowInputPower OBJECT-TYPE
SYNTAX Integer32
Khermosh Expires August 14, 2006 [Page 61]
Internet-Draft Managed Objects of EPON February 2006
UNITS "0.1 dbm"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The lowest optical power monitored at the input during the
current 15-minute interval."
::= { dot3ExtPkgOptIfEntry 3 }
dot3ExtPkgOptIfHighInputPower OBJECT-TYPE
SYNTAX Integer32
UNITS "0.1 dbm"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The highest optical power monitored at the input during the
current 15-minute interval."
::= { dot3ExtPkgOptIfEntry 4 }
dot3ExtPkgOptIfLowerInputPowerThreshold OBJECT-TYPE
SYNTAX Integer32
UNITS "0.1 dbm"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The lower limit threshold on input power. If
dot3ExtPkgOptIfInputPower drops to this value or below,
a Threshold Crossing Alert (TCA) should be sent."
::= { dot3ExtPkgOptIfEntry 5 }
dot3ExtPkgOptIfUpperInputPowerThreshold OBJECT-TYPE
SYNTAX Integer32
UNITS "0.1 dbm"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The upper limit threshold on input power. If
dot3ExtPkgOptIfInputPower reaches or exceeds this value,
a Threshold Crossing Alert (TCA) should be sent."
::= { dot3ExtPkgOptIfEntry 6 }
dot3ExtPkgOptIfOutputPower OBJECT-TYPE
SYNTAX Integer32
UNITS "0.1 dbm"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The optical power monitored at the output."
::= { dot3ExtPkgOptIfEntry 7 }
Khermosh Expires August 14, 2006 [Page 62]
Internet-Draft Managed Objects of EPON February 2006
dot3ExtPkgOptIfLowOutputPower OBJECT-TYPE
SYNTAX Integer32
UNITS "0.1 dbm"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The lowest optical power monitored at the output during the
current 15-minute interval."
::= { dot3ExtPkgOptIfEntry 8 }
dot3ExtPkgOptIfHighOutputPower OBJECT-TYPE
SYNTAX Integer32
UNITS "0.1 dbm"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The highest optical power monitored at the output during the
current 15-minute interval."
::= { dot3ExtPkgOptIfEntry 9 }
dot3ExtPkgOptIfLowerOutputPowerThreshold OBJECT-TYPE
SYNTAX Integer32
UNITS "0.1 dbm"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The lower limit threshold on output power. If
dot3ExtPkgOptIfOutputPower drops to this value or below,
a Threshold Crossing Alert (TCA) should be sent."
::= { dot3ExtPkgOptIfEntry 10 }
dot3ExtPkgOptIfUpperOutputPowerThreshold OBJECT-TYPE
SYNTAX Integer32
UNITS "0.1 dbm"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The upper limit threshold on output power. If
dot3ExtPkgOptIfOutputPower reaches or exceeds this value,
a Threshold Crossing Alert (TCA) should be sent."
::= { dot3ExtPkgOptIfEntry 11 }
dot3ExtPkgOptIfSignalDetect OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"When getting true(1) there is a valid optical signal at
Khermosh Expires August 14, 2006 [Page 63]
Internet-Draft Managed Objects of EPON February 2006
the receive which is above the optical power level for
signal detection. When getting false(2) the optical
signal at the receive is below the optical power level
for signal detection.
This object is relevant for an OLT and an ONU."
DEFVAL { false }
::= { dot3ExtPkgOptIfEntry 12 }
dot3ExtPkgOptIfTransmitAlarm OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"When getting true(1) there is a non-valid optical signal
at the transmit of the interface, either a higher level
or lower level than expected. When getting false(2) the
optical signal at the transmit is valid and in the
required range.
This object is relevant for an OLT and an ONU."
DEFVAL { false }
::= { dot3ExtPkgOptIfEntry 13 }
dot3ExtPkgOptIfTransmitEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Setting this variable to true(1) will cause the optical
interface to start transmission (according to the
control protocol specified for the logical interface).
Setting this variable to false(2) will cause the
interface to stop the optical transmission.
When getting true(1) the optical interface is in
transmit mode (obeying to the logical control protocol).
When getting false(2) the optical interface is not in
transmit mode.
Writing can be done at any time.
The variable is relevant when the admin state of the
device is active as set by the dot3MpcpAdminState.
This object is relevant for an OLT and an ONU."
DEFVAL { false }
::= { dot3ExtPkgOptIfEntry 14 }
-- Conformance Statements
-- Conformance Groups
Khermosh Expires August 14, 2006 [Page 64]
Internet-Draft Managed Objects of EPON February 2006
dot3EponGroups OBJECT IDENTIFIER ::= { dot3EponConformance 1 }
dot3MpcpGroupBase OBJECT-GROUP
OBJECTS {
dot3MpcpOperStatus,
dot3MpcpAdminState,
dot3MpcpMode,
dot3MpcpSyncTime,
dot3MpcpLinkID,
dot3MpcpRemoteMACAddress,
dot3MpcpRegistrationState,
dot3MpcpMaximumPendingGrants,
dot3MpcpTransmitElapsed,
dot3MpcpReceiveElapsed,
dot3MpcpRoundTripTime
}
STATUS current
DESCRIPTION
"A collection of objects of dot3 Mpcp Control entity state
definition. Objects are per LLID."
::= { dot3EponGroups 1 }
dot3MpcpGroupStat OBJECT-GROUP
OBJECTS {
dot3MpcpMACCtrlFramesTransmitted,
dot3MpcpMACCtrlFramesReceived,
dot3MpcpDiscoveryWindowsSent,
dot3MpcpDiscoveryTimeout ,
dot3MpcpTxRegRequest,
dot3MpcpRxRegRequest,
dot3MpcpTxRegAck,
dot3MpcpRxRegAck,
dot3MpcpTxReport,
dot3MpcpRxReport,
dot3MpcpTxGate,
dot3MpcpRxGate,
dot3MpcpTxRegister,
dot3MpcpRxRegister
}
STATUS current
DESCRIPTION
"A collection of objects of dot3 Mpcp Statistics.
Objects are per LLID."
::= { dot3EponGroups 2 }
dot3OmpeGroupID OBJECT-GROUP
OBJECTS {
Khermosh Expires August 14, 2006 [Page 65]
Internet-Draft Managed Objects of EPON February 2006
dot3OmpEmulationType
}
STATUS current
DESCRIPTION
"A collection of objects of dot3 OMP emulation ID entity
state definition. Objects are per LLID."
::= { dot3EponGroups 3 }
dot3OmpeGroupStat OBJECT-GROUP
OBJECTS {
dot3OmpEmulationSLDErrors,
dot3OmpEmulationCRC8Errors,
dot3OmpEmulationBadLLID,
dot3OmpEmulationGoodLLID,
dot3OmpEmulationOnuPonCastLLID,
dot3OmpEmulationOltPonCastLLID,
dot3OmpEmulationBroadcastBitNotOnuLlid,
dot3OmpEmulationOnuLLIDNotBroadcast,
dot3OmpEmulationBroadcastBitPlusOnuLlid,
dot3OmpEmulationNotBroadcastBitNotOnuLlid
}
STATUS current
DESCRIPTION
"A collection of objects of dot3 OMP emulation
Statistics. Objects are per LLID."
::= { dot3EponGroups 4 }
dot3EponFecGroupAll OBJECT-GROUP
OBJECTS {
dot3EponFecPCSCodingViolation,
dot3EponFecAbility,
dot3EponFecMode,
dot3EponFecCorrectedBlocks,
dot3EponFecUncorrectableBlocks,
dot3EponFecBufferHeadCodingViolation
}
STATUS current
DESCRIPTION
"A collection of objects of FEC group definition.
Objects are per LLID."
::= { dot3EponGroups 5 }
dot3ExtPkgGroupControl OBJECT-GROUP
Khermosh Expires August 14, 2006 [Page 66]
Internet-Draft Managed Objects of EPON February 2006
OBJECTS {
dot3ExtPkgObjectReset,
dot3ExtPkgObjectPowerDown,
dot3ExtPkgObjectNumberOfLLIDs,
dot3ExtPkgObjectFecEnabled,
dot3ExtPkgObjectReportMaximumNumQueues,
dot3ExtPkgObjectRegisterAction
}
STATUS current
DESCRIPTION
"A collection of objects of dot3ExtPkg control
definition. Objects are per LLID."
::= { dot3EponGroups 6 }
dot3ExtPkgGroupQueue OBJECT-GROUP
OBJECTS {
dot3ExtPkgObjectReportNumThreshold,
dot3ExtPkgObjectReportMaximumNumThreshold,
dot3ExtPkgStatTxFramesQueue,
dot3ExtPkgStatRxFramesQueue,
dot3ExtPkgStatDroppedFramesQueue
}
STATUS current
DESCRIPTION
"A collection of objects of dot3ExtPkg Queue
definition. Objects are per LLID, per queue."
::= { dot3EponGroups 7 }
dot3ExtPkgGroupQueueSets OBJECT-GROUP
OBJECTS {
dot3ExtPkgObjectReportThreshold
}
STATUS current
DESCRIPTION
"A collection of objects of dot3ExtPkg Queue_sets
definition. Objects are per LLID, per queue, per
queue_set."
::= { dot3EponGroups 8 }
dot3ExtPkgGroupOptIf OBJECT-GROUP
OBJECTS {
dot3ExtPkgOptIfSuspectedFlag,
dot3ExtPkgOptIfInputPower,
dot3ExtPkgOptIfLowInputPower,
dot3ExtPkgOptIfHighInputPower,
dot3ExtPkgOptIfLowerInputPowerThreshold,
Khermosh Expires August 14, 2006 [Page 67]
Internet-Draft Managed Objects of EPON February 2006
dot3ExtPkgOptIfUpperInputPowerThreshold,
dot3ExtPkgOptIfOutputPower,
dot3ExtPkgOptIfLowOutputPower,
dot3ExtPkgOptIfHighOutputPower,
dot3ExtPkgOptIfLowerOutputPowerThreshold,
dot3ExtPkgOptIfUpperOutputPowerThreshold,
dot3ExtPkgOptIfSignalDetect,
dot3ExtPkgOptIfTransmitAlarm,
dot3ExtPkgOptIfTransmitEnable
}
STATUS current
DESCRIPTION
"A collection of objects of Optical interface control and
status indication for the EPON Interfaces.
Objects are per LLID."
::= { dot3EponGroups 9 }
-- Compliance
dot3EponCompliances
OBJECT IDENTIFIER ::= { dot3EponConformance 2 }
dot3MPCPCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION "The compliance statement for Multi-point
control protocol interfaces."
MODULE -- this module
MANDATORY-GROUPS { dot3MpcpGroupBase}
GROUP dot3MpcpGroupStat
DESCRIPTION "This group is mandatory for all MPCP supporting
interfaces for Statistics collection."
::= { dot3EponCompliances 1}
dot3OmpeCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION "The compliance statement for OMPEmulation
interfaces."
MODULE -- this module
MANDATORY-GROUPS { dot3OmpeGroupID}
GROUP dot3OmpeGroupStat
DESCRIPTION "This group is mandatory for all OMPemulation
Khermosh Expires August 14, 2006 [Page 68]
Internet-Draft Managed Objects of EPON February 2006
supporting interfaces for Statistics collection."
::= { dot3EponCompliances 2}
dot3EponFecCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION "The compliance statement for Fec EPON interfaces.
This group is mandatory for all EPON interfaces
Supporting FEC functionality as for Definitions and
BER Statistics collection."
MODULE -- this module
MANDATORY-GROUPS { dot3EponFecGroupAll }
::= { dot3EponCompliances 3}
dot3ExtPkgCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION "The compliance statement for EPON Interfaces
using the extended package."
MODULE -- this module
MANDATORY-GROUPS { dot3ExtPkgGroupControl }
GROUP dot3ExtPkgGroupQueue
DESCRIPTION " This group is mandatory for all OLT EPON interfaces
supporting Report Queue management of the extended
package."
GROUP dot3ExtPkgGroupQueueSets
DESCRIPTION " This group is mandatory for all OLT EPON interfaces
supporting Report Queue_sets management of the
extended package."
GROUP dot3ExtPkgGroupOptIf
DESCRIPTION "This group is mandatory for all EPON interfaces
supporting optical interfaces control and indication
of the extended package."
::= { dot3EponCompliances 4}
END
Khermosh Expires August 14, 2006 [Page 69]
Internet-Draft Managed Objects of EPON February 2006
6. IANA Considerations
The DOT3 EPON MIB module requires the allocation of a single object
identifier for its MODULE-IDENTITY under the MIB-2 tree.
The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
dot3EponMIB { mib-2 XXX }
Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX"
(here and in the MIB module) with the assigned value and to remove
this note.
Khermosh Expires August 14, 2006 [Page 70]
Internet-Draft Managed Objects of EPON February 2006
7. Security Considerations
There are number of managed objects defined in this MIB module that
have a MAX-ACCESS clause of read-write or read-create. Writing to
these objects can have potentially disruptive effects on network
operation: Including:
Changing dot3MpcpAdminState state (Writing can be done at any time)
Changing dot3EponFecMode mode (Writing can be done at any time)
Changing dot3ExtPkgObjectReset mode (Writing can be done at any time)
Changing dot3ExtPkgObjectFecEnabled mode (Writing can be done at any
time)
Changing dot3ExtPkgObjectPowerDown (Writing can be done at any time)
Changing dot3ExtPkgObjectReportNumThreshold (Writing can be done at
any time)
Changing dot3ExtPkgObjectReportThreshold (Writing can be done at any
time)
Changing dot3ExtPkgObjectRegisterAction (Writing can be done at any
time)
Changing dot3ExtPkgRMadlEntryStatus (Writing can be done at any time)
Changing dot3ExtPkgOptIfLowerInputPowerThreshold (Writing can be done
at any time)
Changing dot3ExtPkgOptIfUpperInputPowerThreshold (Writing can be done
at any time)
Changing dot3ExtPkgOptIfLowerOutputPowerThreshold (Writing can be
done at any time)
Changing dot3ExtPkgOptIfUpperOutputPowerThreshold (Writing can be
done at any time)
Changing dot3ExtPkgOptIfTransmitEnable (Writing can be done at any
time)
The user of this MIB module must therefore be aware that support for
SET operations in a non-secure environment without proper protection
can have a negative effect on network operations.
Khermosh Expires August 14, 2006 [Page 71]
Internet-Draft Managed Objects of EPON February 2006
The readable objects in this MIB module (i.e., those with MAX-ACCESS
other than not-accessible) may be considered sensitive in some
environments since, collectively, they provide information about the
performance of network interfaces and can reveal some aspects of
their configuration. In such environments it is important to control
even GET and NOTIFY access to these objects and possibly even to
encrypt their values when sending them over the network via SNMP.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
Khermosh Expires August 14, 2006 [Page 72]
Internet-Draft Managed Objects of EPON February 2006
8. References
8.1. Normative References
[802.3] IEEE, "Institute of Electrical and Electronic Engineers,
IEEE Std 802.3-2002, "IEEE Standard for Carrier Sense
Multiple Access with Collision Detection (CSMA/CD) Access
Method and Physical Layer Specifications", December 2002.
[802.3ah] IEEE, "Institute of Electrical and Electronic Engineers,
IEEE Std 802.3ah-2004. Information technology -
Telecommunications and information exchange between
systems - Local and metropolitan area networks - Specific
requirements - Part 3: Carrier sense multiple access with
collision detection (CSMA/CD) access method and physical
layer specifications - Media Access Control Parameters,
Physical Layers and Management Parameters for subscriber
access networks", IEEE Std 802.3ah-2004, October 2004.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000.
[RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table
Extension to the Interfaces Group MIB", RFC 2864,
June 2000.
[RFC3635] Flick, J., "Definitions of Managed Objects for the
Ethernet-like Interface Types", RFC 3635, September 2003.
[RFC3636] Flick, J., "Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs)", RFC 3636, September 2003.
8.2. Informative References
[I-D.ietf-hubmib-efm-mib]
Squire, M., "Ethernet in the First Mile (EFM) Common MIB",
Khermosh Expires August 14, 2006 [Page 73]
Internet-Draft Managed Objects of EPON February 2006
draft-squire-hubmib-efm-mib-02 (work in progress),
December 2004.
[RFC1525] Decker, E., McCloghrie, K., Langille, P., and A.
Rijsinghani, "Definitions of Managed Objects for Source
Routing Bridges", RFC 1525, September 1993.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
[RFC4188] Norseth, K. and E. Bell, "Definitions of Managed Objects
for Bridges", RFC 4188, September 2005.
Khermosh Expires August 14, 2006 [Page 74]
Internet-Draft Managed Objects of EPON February 2006
Author's Address
Lior Khermosh
Passave Technologies
Kohav Hertzelia bldg,
4 Hasadnaot St.,
Hertzliya Pituach, 46120
ISRAEL
Phone: +972-9-9628000 Ext: 302
Fax: +972-9-9628001
Email: lior.khermosh@passave.com
Khermosh Expires August 14, 2006 [Page 75]
Internet-Draft Managed Objects of EPON February 2006
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
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
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
Khermosh Expires August 14, 2006 [Page 76]
