draft-ietf-hubmib-efm-cu-mib-03.txt   draft-ietf-hubmib-efm-cu-mib-04.txt 
Network Working Group E. Beili Network Working Group E. Beili
Internet-Draft Actelis Networks Internet-Draft Actelis Networks
Expires: October 3, 2005 April 4, 2005 Expires: April 27, 2006 October 24, 2005
Ethernet in the First Mile Copper (EFMCu) Interfaces MIB Ethernet in the First Mile Copper (EFMCu) Interfaces MIB
draft-ietf-hubmib-efm-cu-mib-03.txt draft-ietf-hubmib-efm-cu-mib-04.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions By submitting this Internet-Draft, each author represents that any
of section 3 of RFC 3667. By submitting this Internet-Draft, each applicable patent or other IPR claims of which he or she is aware
author represents that any applicable patent or other IPR claims of have been or will be disclosed, and any of which he or she becomes
which he or she is aware have been or will be disclosed, and any of aware will be disclosed, in accordance with Section 6 of BCP 79.
which he or she become aware will be disclosed, in accordance with
RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as other groups may also distribute working documents as Internet-
Internet-Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 3, 2005. This Internet-Draft will expire on April 27, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2005).
Abstract Abstract
This document defines a Management Information Base (MIB) module for This document defines a Management Information Base (MIB) module for
use with network management protocols in TCP/IP based internets. use with network management protocols in TCP/IP based internets.
This document proposes an extension to the Ethernet-like Interfaces This document proposes an extension to the Ethernet-like Interfaces
MIB and MAU MIB modules with a set of objects for managing an MIB and MAU MIB modules with a set of objects for managing an
Ethernet in the First Mile Copper (EFMCu) interfaces 10PASS-TS and Ethernet in the First Mile Copper (EFMCu) interfaces 10PASS-TS and
2BASE-TL, defined in IEEE Std 802.3ah-2004. 2BASE-TL, defined in IEEE Std 802.3ah-2004.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Relation to other MIB modules . . . . . . . . . . . . . . . . 4 3. Relation to other MIB modules . . . . . . . . . . . . . . . . 4
3.1 Relation to Interfaces Group MIB module . . . . . . . . . 4 3.1. Relation to Interfaces Group MIB module . . . . . . . . . 4
3.1.1 Layering Model . . . . . . . . . . . . . . . . . . . . 4 3.1.1. Layering Model . . . . . . . . . . . . . . . . . . . . 4
3.1.2 PME Aggregation Function (PAF) . . . . . . . . . . . . 6 3.1.2. PME Aggregation Function (PAF) . . . . . . . . . . . . 6
3.1.3 Discovery Operation . . . . . . . . . . . . . . . . . 6 3.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 6
3.1.4 EFMCu ports initialization . . . . . . . . . . . . . . 8 3.1.4. EFMCu ports initialization . . . . . . . . . . . . . . 8
3.1.5 Usage of ifTable . . . . . . . . . . . . . . . . . . . 8 3.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 8
3.2 Relation to SHDSL MIB module . . . . . . . . . . . . . . . 9 3.2. Relation to SHDSL MIB module . . . . . . . . . . . . . . . 9
3.3 Relation to VDSL MIB module . . . . . . . . . . . . . . . 10 3.3. Relation to VDSL MIB module . . . . . . . . . . . . . . . 10
3.4 Relation to Ethernet-Like and MAU MIB modules . . . . . . 10 3.4. Relation to Ethernet-Like and MAU MIB modules . . . . . . 10
4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 11 4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 11
4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2 PME Profiles . . . . . . . . . . . . . . . . . . . . . . . 11 4.2. PME Profiles . . . . . . . . . . . . . . . . . . . . . . . 11
4.3 Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 12 4.3. Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 12
5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 13 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 13
6. Security Considerations . . . . . . . . . . . . . . . . . . . 67 6. Security Considerations . . . . . . . . . . . . . . . . . . . 67
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 69 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 69
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 69 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 69
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69
9.1 Normative References . . . . . . . . . . . . . . . . . . . . 69 9.1. Normative References . . . . . . . . . . . . . . . . . . . 69
9.2 Informative References . . . . . . . . . . . . . . . . . . . 70 9.2. Informative References . . . . . . . . . . . . . . . . . . 70
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 71 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 72
Intellectual Property and Copyright Statements . . . . . . . . 72 Intellectual Property and Copyright Statements . . . . . . . . . . 73
1. Introduction 1. Introduction
New Ethernet-like interfaces have been defined in the Institute of New Ethernet-like interfaces have been defined in the Institute of
Electrical and Electronics Engineers (IEEE) Standard 802.3ah-2004 Electrical and Electronics Engineers (IEEE) Standard 802.3ah-2004
[802.3ah], a.k.a. Ethernet in the First Mile (EFM). In particular [802.3ah], a.k.a. Ethernet in the First Mile (EFM). In particular
2BASE-TL and 10PASS-TS physical interfaces (PHYs), defined over 2BASE-TL and 10PASS-TS physical interfaces (PHYs), defined over
voice-grade copper pairs, have been specified for the long and short voice-grade copper pairs, have been specified for the long and short
reach respectively. These interfaces, collectively called EFMCu, are reach respectively. These interfaces, collectively called EFMCu, are
based on ITU-T G.SHDSL [G.991.2] and VDSL [G.993.1] specifications based on ITU-T G.SHDSL [G.991.2] and VDSL [G.993.1] specifications
skipping to change at page 3, line 31 skipping to change at page 3, line 31
10PASS-TS PHY is capable of providing at least 10Mbps over 750 m long 10PASS-TS PHY is capable of providing at least 10Mbps over 750 m long
single copper pair with a mean BER of 10^-7 (using 6dB target noise single copper pair with a mean BER of 10^-7 (using 6dB target noise
margin). margin).
This memo defines a Management Information Base (MIB) module for use This memo defines a Management Information Base (MIB) module for use
with network management protocols in the Internet community to manage with network management protocols in the Internet community to manage
EFMCu interfaces. EFMCu interfaces.
Note that managed objects for Operation, Administration and Note that managed objects for Operation, Administration and
Management (OAM) and Ethernet over Passive Optical Networks (EPON) Management (OAM) and Ethernet over Passive Optical Networks (EPON)
clauses of IEEE 802.3ah are defined in EFM-COMMON-MIB clauses of IEEE 802.3ah are defined in EFM-COMMON-MIB [I-D.ietf-
[I-D.ietf-hubmib-efm-mib] and EFM-EPON-MIB hubmib-efm-mib] and EFM-EPON-MIB [I-D.ietf-hubmib-efm-epon-mib]
[I-D.ietf-hubmib-efm-epon-mib] respectively. respectively.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, 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 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. A detailed introduction to the current SNMP Management [RFC2580].
Framework can be found in RFC 2570 [RFC2570].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. Relation to other MIB modules 3. Relation to other MIB modules
This section outlines the relationship of this MIB with other MIB This section outlines the relationship of this MIB with other MIB
modules described in the relevant RFCs. Specifically, Interfaces modules described in the relevant RFCs. Specifically, Interfaces
Group MIB (IF-MIB), Ethernet-Like (EtherLike-MIB), MAU (MAU-MIB), Group MIB (IF-MIB), Ethernet-Like (EtherLike-MIB), MAU (MAU-MIB),
SHDSL (HDSL2-SHDSL-LINE-MIB) and VDSL (VDSL-LINE-EXT-MCM-MIB) are SHDSL (HDSL2-SHDSL-LINE-MIB) and VDSL (VDSL-LINE-EXT-MCM-MIB) are
discussed. discussed.
3.1 Relation to Interfaces Group MIB module 3.1. Relation to Interfaces Group MIB module
2BASE-TL and 10PASS-TS PHY's specified in this MIB module are stacked 2BASE-TL and 10PASS-TS PHY's specified in this MIB module are stacked
Ethernet interfaces and as such are managed using generic interface Ethernet interfaces and as such are managed using generic interface
management objects defined in the IF-MIB [RFC2863]. The stack management objects defined in the IF-MIB [RFC2863]. The stack
management is done via the ifStackTable, as defined in the IF-MIB management is done via the ifStackTable, as defined in the IF-MIB
[RFC2863] and ifInvStackTable, as defined in the [RFC2863] and ifInvStackTable, as defined in the IF-INVERTED-STACK-
IF-INVERTED-STACK-MIB [RFC2864]. MIB [RFC2864].
3.1.1 Layering Model 3.1.1. Layering Model
An EFMCu interface can aggregate up to 32 Physical Medium Entity An EFMCu interface can aggregate up to 32 Physical Medium Entity
(PME) sub-layer devices (modems), using so called PME Aggregation (PME) sub-layer devices (modems), using so called PME Aggregation
Function (PAF). Function (PAF).
A generic EFMCu device can have a number of Physical Coding Sublayer A generic EFMCu device can have a number of Physical Coding Sublayer
(PCS) ports, connected to a MAC via Medium Independent Interface (PCS) ports, connected to a MAC via Medium Independent Interface
(MII) at the upper layer, and cross-connected to a number of (MII) at the upper layer, and cross-connected to a number of
underlying PMEs, with a single PCS per PME relationship, see clause underlying PMEs, with a single PCS per PME relationship, see clause
61.1 of [802.3ah] for more details. 61.1 of [802.3ah] for more details.
skipping to change at page 4, line 46 skipping to change at page 4, line 46
table (ifTable) as a separate port with ifType of shdsl(169) for table (ifTable) as a separate port with ifType of shdsl(169) for
2BASE-TL or vdsl(97) for 10PASS-TS. The ifType values are defined in 2BASE-TL or vdsl(97) for 10PASS-TS. The ifType values are defined in
[IANAifType-MIB]. [IANAifType-MIB].
ifSpeed for each PME SHALL return the actual data bitrate of the ifSpeed for each PME SHALL return the actual data bitrate of the
active PME (e.g. for 2BaseTL PMEs it is a multiple of 64Kbps). Zero active PME (e.g. for 2BaseTL PMEs it is a multiple of 64Kbps). Zero
value SHALL be returned when PME is initializing or down. value SHALL be returned when PME is initializing or down.
The ifSpeed of the PCS is the sum of the current operating data rates The ifSpeed of the PCS is the sum of the current operating data rates
of all PMEs in the aggregation group, without the 64/65B of all PMEs in the aggregation group, without the 64/65B
encapsulation overhead and PAF overhead, but acounting for the encapsulation overhead and PAF overhead, but acounting for the Inter-
Inter-Frame Gaps (IFG). Frame Gaps (IFG).
When using the stated definition of ifSpeed for the PCS, there would When using the stated definition of ifSpeed for the PCS, there would
be no frame loss in the following configuration (the test-sets are be no frame loss in the following configuration (the test-sets are
configured to generate 100% of back to back traffic, i.e. minimal configured to generate 100% of back to back traffic, i.e. minimal
IFG, at 10 or 100Mbps, with min and max frame sizes; the EFM IFG, at 10 or 100Mbps, with min and max frame sizes; the EFM
interfaces are obviously aggregated): interfaces are obviously aggregated):
[testset]--10BaseT--[CO]--2BaseTL--[CPE]--10BaseT--[testset] [testset]--10BaseT--[CO]--2BaseTL--[CPE]--10BaseT--[testset]
ifSpeed= 10Mbps 10Mbps 10Mbps ifSpeed= 10Mbps 10Mbps 10Mbps
skipping to change at page 5, line 50 skipping to change at page 5, line 50
The ifStackTable is indexed by the ifIndex values of the aggregated The ifStackTable is indexed by the ifIndex values of the aggregated
EFMCu port (PCS) and the PMEs connected to it. ifStackTable allows a EFMCu port (PCS) and the PMEs connected to it. ifStackTable allows a
Network Management application to determine which PMEs are connected Network Management application to determine which PMEs are connected
to a particular PCS and change connections (if supported by the to a particular PCS and change connections (if supported by the
application). The ifInvStackTable, being an inverted version of the application). The ifInvStackTable, being an inverted version of the
ifStackTable, provides an efficient means for a Network Management ifStackTable, provides an efficient means for a Network Management
application to read a subset of the ifStackTable and thereby application to read a subset of the ifStackTable and thereby
determine which PCS runs on top of a particular PME. determine which PCS runs on top of a particular PME.
A new table ifAvailableStackTable defined in this MIB module, A new table ifAvailableStackTable defined in this MIB module,
specifies for each PCS a list of PMEs, which can possibly be specifies for each PCS a list of PMEs, which can possibly be cross-
cross-connected to that PCS, determined by the cross-connect connected to that PCS, determined by the cross-connect capability of
capability of the device. This table, modeled after ifStackTable, is the device. This table, modeled after ifStackTable, is read only,
read only, reflecting current cross-connect capability, which can be reflecting current cross-connect capability, which can be dynamic in
dynamic in some implementations (e.g. if PMEs are located on a some implementations (e.g. if PMEs are located on a pluggable module
pluggable module and the module is pulled out). Note that PME and the module is pulled out). Note that PME availability per PCS,
availability per PCS, described by ifAvailableStackTable, can be described by ifAvailableStackTable, can be constrained by other
constrained by other parameters, for example by aggregation capacity parameters, for example by aggregation capacity of a PCS or by the
of a PCS or by the PME in question being already connected to another PME in question being already connected to another PCS. So, in order
PCS. So, in order to ensure that a particular PME can be connected to ensure that a particular PME can be connected to the PCS, all
to the PCS, all respective parameters (e.g. ifAvailableStackTable, respective parameters (e.g. ifAvailableStackTable, ifStackTable and
ifStackTable and efmCuPAFCapacity) SHALL be inspected. efmCuPAFCapacity) SHALL be inspected.
3.1.2 PME Aggregation Function (PAF) 3.1.2. PME Aggregation Function (PAF)
The PME Aggregation Function (PAF) allows a number of PMEs to be The PME Aggregation Function (PAF) allows a number of PMEs to be
aggregated onto a PCS port, by fragmenting the Ethernet frames, aggregated onto a PCS port, by fragmenting the Ethernet frames,
transmitting the fragments over multiple PMEs and assembling the transmitting the fragments over multiple PMEs and assembling the
original frames at the remote port. PAF is OPTIONAL, meaning that a original frames at the remote port. PAF is OPTIONAL, meaning that a
device with a single PME MAY perform fragmentation and re-assembly if device with a single PME MAY perform fragmentation and re-assembly if
this function is supported by the device. Note however that the this function is supported by the device. Note however that the
agent is REQUIRED to report on the PAF capability for all EFMCu ports agent is REQUIRED to report on the PAF capability for all EFMCu ports
(2BASE-TL and 10PASS-TS). (2BASE-TL and 10PASS-TS).
This MIB module allows a Network Management application to query PAF This MIB module allows a Network Management application to query PAF
capability and enable/disable it if supported. Note that enabling capability and enable/disable it if supported. Note that enabling
PAF effectively turns on fragmentation and re-assembly, even on a PAF effectively turns on fragmentation and re-assembly, even on a
single-PME port. single-PME port.
3.1.3 Discovery Operation 3.1.3. Discovery Operation
The EFMCu ports may optionally support discovery operation, whereby The EFMCu ports may optionally support discovery operation, whereby
PMEs, during initialization, exchange information about their PMEs, during initialization, exchange information about their
respective aggregation groups (PCS). This information can then be respective aggregation groups (PCS). This information can then be
used to detect copper missconnections or for an automatic assignment used to detect copper missconnections or for an automatic assignment
of the local PMEs into aggregation groups instead of fixed of the local PMEs into aggregation groups instead of fixed pre-
pre-configuration. configuration.
This MIB module allows a Network Management application to control This MIB module allows a Network Management application to control
EFM Discovery mechanism and query its results. Note that the EFM Discovery mechanism and query its results. Note that the
Discovery mechanism can work only if PAF is supported and enabled. Discovery mechanism can work only if PAF is supported and enabled.
Two tables are used by Discovery mechanism: ifStackTable and Two tables are used by Discovery mechanism: ifStackTable and
ifAvailableStackTable defined. The following pseudo-code defines an ifAvailableStackTable defined. The following pseudo-code defines an
example of Discovery and automatic PME assignment for a generic PAF example of Discovery and automatic PME assignment for a generic PAF
enabled multi-PCS EFMCu device, located at Central Office (CO), using enabled multi-PCS EFMCu device, located at Central Office (CO), using
objects defined in this MIB module. [Note that automatic PME objects defined in this MIB module. [Note that automatic PME
skipping to change at page 8, line 10 skipping to change at page 8, line 10
Note that PCS port does not have to be operationally 'down' for the Note that PCS port does not have to be operationally 'down' for the
connection to succeed. In fact, a dynamic PME addition (and removal) connection to succeed. In fact, a dynamic PME addition (and removal)
MAY be implemented whith an available PME being initialized first (by MAY be implemented whith an available PME being initialized first (by
setting its ifAdminStatus to 'up') and then added to an operationally setting its ifAdminStatus to 'up') and then added to an operationally
'up' PCS port, by modifying a respective ifStackTable entry. 'up' PCS port, by modifying a respective ifStackTable entry.
It is RECOMMENDED that a removal of the last operationally 'up' PME It is RECOMMENDED that a removal of the last operationally 'up' PME
from an operationally 'up' PCS would be rejected by the from an operationally 'up' PCS would be rejected by the
implementation, as this action would completely drop the link. implementation, as this action would completely drop the link.
3.1.4 EFMCu ports initialization 3.1.4. EFMCu ports initialization
EFMCu ports being built on top of xDSL technology, require a lengthy EFMCu ports being built on top of xDSL technology, require a lengthy
initialization or 'training' process, before any data can pass. initialization or 'training' process, before any data can pass.
During this initialization both ends of a link (peers) work During this initialization both ends of a link (peers) work
cooperatively to achieve required data rate on a particular copper cooperatively to achieve required data rate on a particular copper
pair. Sometimes, when the copper line is too long or the noise pair. Sometimes, when the copper line is too long or the noise
environment on the line is too high, that 'training' process may fail environment on the line is too high, that 'training' process may fail
to achieve a specific target rate with required characteristics. to achieve a specific target rate with required characteristics.
The ifAdminStatus object from the IF-MIB, controls the desired state The ifAdminStatus object from the IF-MIB, controls the desired state
skipping to change at page 8, line 44 skipping to change at page 8, line 44
connected to the PCS are 'down' the PCS SHALL be considered connected to the PCS are 'down' the PCS SHALL be considered
operationally 'lowerLayerDown'. The PCS SHALL be considered operationally 'lowerLayerDown'. The PCS SHALL be considered
operationally 'notPresent' if it is not connected to any PME. The operationally 'notPresent' if it is not connected to any PME. The
PCS/PME interface SHALL remain operationally 'down' during PCS/PME interface SHALL remain operationally 'down' during
initialization. initialization.
The efmCuPmeOperStatus defined in this MIB module expands PME's The efmCuPmeOperStatus defined in this MIB module expands PME's
ifOperStatus value of 'down' to 'downReady', 'downNotReady' and ifOperStatus value of 'down' to 'downReady', 'downNotReady' and
'init' values, indicating various EFMCu PME specific states. 'init' values, indicating various EFMCu PME specific states.
3.1.5 Usage of ifTable 3.1.5. Usage of ifTable
Both PME and PCS interfaces of the EFMCu PHY are managed using Both PME and PCS interfaces of the EFMCu PHY are managed using
interface specific management objects defined in this MIB module and interface specific management objects defined in this MIB module and
generic interface objects from the ifTable of IF-MIB, with all generic interface objects from the ifTable of IF-MIB, with all
management table entries referenced by the interface index ifIndex. management table entries referenced by the interface index ifIndex.
The following table summarizes EFMCu specific interpretations for The following table summarizes EFMCu specific interpretations for
some of the ifTable objects specified by the mandatory some of the ifTable objects specified by the mandatory
ifGeneralInformationGroup: ifGeneralInformationGroup:
+---------------------------------+---------------------------------+ +---------------+---------------------------------------------------+
| IF-MIB object | EFMCu interpretation | | IF-MIB object | EFMCu interpretation |
+---------------------------------+---------------------------------+ +---------------+---------------------------------------------------+
| ifIndex | Interface index. Note that each | | ifIndex | Interface index. Note that each PME and each PCS |
| | PME and each PCS in the EFMCu | | | in the EFMCu PHY MUST have a unique index, as |
| | PHY MUST have a unique index, | | | there some PCS and PME specific attributes |
| | as there some PCS and PME | | | accessible only on the PCS or PME level. |
| | specific attributes accessible | | ifType | ethernetCsmacd(6) for PCS, shdsl(169) for |
| | only on the PCS or PME level. | | | 2BASE-TL PME, vdsl(97) for 10PASS-TS PME |
| ifType | ethernetCsmacd(6) for PCS, | | ifSpeed | Operating data rate for the PME. For the PCS it |
| | shdsl(169) for 2BASE-TL PME, | | | is the sum of the current operating data rates of |
| | vdsl(97) for 10PASS-TS PME | | | all PMEs in the aggregation group, without the |
| ifSpeed | Operating data rate for the | | | 64/65B encapsulation overhead and PAF overhead, |
| | PME. For the PCS it is the sum | | | but acounting for the Inter-Frame Gaps (IFG) |
| | of the current operating data | | ifAdminStatus | Setting this object to 'up' instructs a |
| | rates of all PMEs in the | | | particular PCS (with all PMEs connected to it) or |
| | aggregation group, without the | | | PME to start initialization process |
| | 64/65B encapsulation overhead | | ifOperStatus | efmCuPmeOperStatus supplements the 'down' value |
| | and PAF overhead, but acounting | | | of ifOperStatus for PMEs. |
| | for the Inter-Frame Gaps (IFG) | +---------------+---------------------------------------------------+
| ifAdminStatus | Setting this object to 'up' |
| | instructs a particular PCS |
| | (with all PMEs connected to it) |
| | or PME to start initialization |
| | process |
| ifOperStatus | efmCuPmeOperStatus supplements |
| | the 'down' value of |
| | ifOperStatus for PMEs. |
+---------------------------------+---------------------------------+
Table 1 Table 1
3.2 Relation to SHDSL MIB module 3.2. Relation to SHDSL MIB module
G.SHDSL.bis modems, similar to PME(s) comprising a 2BASE-TL port, are G.SHDSL.bis modems, similar to PME(s) comprising a 2BASE-TL port, are
described in HDSL2-SHDSL-LINE-MIB [I-D.ietf-adslmib-gshdslbis]. Note described in HDSL2-SHDSL-LINE-MIB [I-D.ietf-adslmib-gshdslbis]. Note
that not all attributes of G.SHDSL modems reflected in that not all attributes of G.SHDSL modems reflected in HDSL2-SHDSL-
HDSL2-SHDSL-LINE-MIB have adequate management objects (Clause 30 LINE-MIB have adequate management objects (Clause 30 attributes and
attributes and Clause 45 registers) in the EFM standard. Clause 45 registers) in the EFM standard.
Because of these differences and for the purposes of simplicity, Because of these differences and for the purposes of simplicity,
unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs
and name consistency (e.g. prefixing the 2BASE-TL PME related and name consistency (e.g. prefixing the 2BASE-TL PME related objects
objects with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided not to
not to reference HDSL2-SHDSL-LINE-MIB objects, but define all the reference HDSL2-SHDSL-LINE-MIB objects, but define all the relevant
relevant objects in this MIB module. objects in this MIB module.
However, if some functionality, not available in this MIB module, is However, if some functionality, not available in this MIB module, is
required and supported by the PME, e.g. performance monitoring, required and supported by the PME, e.g. performance monitoring,
relevant HDSL2-SHDSL-LINE-MIB groups MAY be included and aplied for relevant HDSL2-SHDSL-LINE-MIB groups MAY be included and aplied for
PMEs of 2BASE-TL subtype. PMEs of 2BASE-TL subtype.
3.3 Relation to VDSL MIB module 3.3. Relation to VDSL MIB module
VDSL (DMT) modems, similar to the PME(s) comprising a 10PASS-TS port, VDSL (DMT) modems, similar to the PME(s) comprising a 10PASS-TS port,
are described in VDSL-LINE-EXT-MCM-MIB are described in VDSL-LINE-EXT-MCM-MIB [RFC4070]. Note that not all
[I-D.ietf-adslmib-vdsl-ext-mcm]. Note that not all attributes of attributes of VDSL modems reflected in VDSL-LINE-EXT-MCM-MIB have
VDSL modems reflected in VDSL-LINE-EXT-MCM-MIB have adequate adequate management objects (Clause 30 attributes and Clause 45
management objects (Clause 30 attributes and Clause 45 registers) in registers) in the EFM standard.
the EFM standard.
Because of these differences and for the purposes of simplicity, Because of these differences and for the purposes of simplicity,
unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs
and name consistency, it was decided not to reference and name consistency, it was decided not to reference VDSL-LINE-EXT-
VDSL-LINE-EXT-MCM-MIB objects, but define all the relevant objects in MCM-MIB objects, but define all the relevant objects in this MIB
this MIB module. module.
However, if some functionality, not available in this MIB module, is However, if some functionality, not available in this MIB module, is
required and supported by the PME, relevant VDSL-LINE-EXT-MCM-MIB required and supported by the PME, relevant VDSL-LINE-EXT-MCM-MIB
groups MAY be included and applied for PMEs of 10PASS-TS subtype. groups MAY be included and applied for PMEs of 10PASS-TS subtype.
3.4 Relation to Ethernet-Like and MAU MIB modules 3.4. Relation to Ethernet-Like and MAU MIB modules
The implementation of EtherLike-MIB [RFC3635] and MAU-MIB The implementation of EtherLike-MIB [RFC3635] and MAU-MIB [I-D.ietf-
[I-D.ietf-hubmib-rfc3636bis] is REQUIRED for the EFMCu interfaces. hubmib-rfc3636bis] is REQUIRED for the EFMCu interfaces.
Two new values of ifMauType (OBJECT-IDENTITIES of dot3MauType) and Two new values of ifMauType (OBJECT-IDENTITIES of dot3MauType) and
corresponding bit definitions of ifMauTypeListBits corresponding bit definitions of ifMauTypeListBits
(IANAifMauTypeListBits) have been defined in the IANA-MAU-TC-MIB (IANAifMauTypeListBits) have been defined in the IANA-MAU-TC-MIB
[I-D.ietf-hubmib-rfc3636bis] for the EFMCu MAUs: [I-D.ietf-hubmib-rfc3636bis] for the EFMCu MAUs:
o dot3MauType2BaseTL and b2BaseTL - for 2BASE-TL MAU o dot3MauType2BaseTL and b2BaseTL - for 2BASE-TL MAU
o dot3MauType10PassTS and b10PassTS - for 10PASS-TS MAU o dot3MauType10PassTS and b10PassTS - for 10PASS-TS MAU
skipping to change at page 11, line 13 skipping to change at page 11, line 7
management software to look in the EFM-CU-MIB for the desired management software to look in the EFM-CU-MIB for the desired
information. For example the information on the particular EFMCu information. For example the information on the particular EFMCu
flavor that an EFMCu port is running is available from flavor that an EFMCu port is running is available from
efmCuOperSubType, defined in this MIB module. efmCuOperSubType, defined in this MIB module.
Since EFMCu PMEs are not EtherLike interfaces, they cannot be Since EFMCu PMEs are not EtherLike interfaces, they cannot be
instantiated as MAU interface objects. instantiated as MAU interface objects.
4. MIB Structure 4. MIB Structure
4.1 Overview 4.1. Overview
The main management objects defined in this MIB module are split into The main management objects defined in this MIB module are split into
2 groups: 2 groups:
o efmCuPort - containing objects for configuration, capabilities, o efmCuPort - containing objects for configuration, capabilities,
status and notifications, common to all EFMCu PHYs. status and notifications, common to all EFMCu PHYs.
o efmCuPme - containing objects for configuration, capabilities, o efmCuPme - containing objects for configuration, capabilities,
status and notifications of EFMCu PMEs. status and notifications of EFMCu PMEs.
In addition the ifAvailableStackTable is defined at the same level. In addition the ifAvailableStackTable is defined at the same level.
The efmCuPme group in turn contains efmCuPme2B and efmCuPme10P The efmCuPme group in turn contains efmCuPme2B and efmCuPme10P
groups, which define PME Profiles specific to 2BASE-TL and 10PASS-TS groups, which define PME Profiles specific to 2BASE-TL and 10PASS-TS
PMEs respectively, as well as PME specific status information. PMEs respectively, as well as PME specific status information.
4.2 PME Profiles 4.2. PME Profiles
Since a managed node can have a large number of EFMCu PHYs, Since a managed node can have a large number of EFMCu PHYs,
provisioning every parameter on every EFMCu PHY may become provisioning every parameter on every EFMCu PHY may become
burdensome. Moreover, most PMEs are provisioned identically with the burdensome. Moreover, most PMEs are provisioned identically with the
same set of parameters. To simplify the provisioning process, this same set of parameters. To simplify the provisioning process, this
MIB module makes use of configuration profiles, similar to MIB module makes use of configuration profiles, similar to HDSL2-
HDSL2-SHDSL-LINE-MIB and VDSL-LINE-EXT-MCM-MIB. A profile is a set SHDSL-LINE-MIB and VDSL-LINE-EXT-MCM-MIB. A profile is a set of
of parameters, used either for configuration or representation of a parameters, used either for configuration or representation of a PME.
PME. The same profile can be shared by multiple PME ports, using the The same profile can be shared by multiple PME ports, using the same
same configuration. configuration.
The PME profiles are defined in efmCuPme2BProfileTable and The PME profiles are defined in efmCuPme2BProfileTable and
efmCu10PProfileTable for 2BASE-TL and 10PASS-TS PMEs respectively. efmCu10PProfileTable for 2BASE-TL and 10PASS-TS PMEs respectively.
There are 12 predefined standard profiles for 2BASE-TL and 22 There are 12 predefined standard profiles for 2BASE-TL and 22
standard profiles for 10PASS-TS, defined in 802.3ah and dedicated for standard profiles for 10PASS-TS, defined in 802.3ah and dedicated for
rapid provisioning of EFMCu PHYs in most scenarios. An ability to rapid provisioning of EFMCu PHYs in most scenarios. In addition this
define new configuration profiles is also provided to allow for EFMCu MIB defines two additional predefined profiles for "best-effort"
deployment tailored to specific copper environment and spectral provisioning of 2BASE-TL PMEs. An ability to define new
regulations. configuration profiles is also provided to allow for EFMCu deployment
tailored to specific copper environment and spectral regulations.
A specific configuration or administrative profile is assigned to a A specific configuration or administrative profile is assigned to a
specific PME via efmCuPmeAdminProfile object. If specific PME via efmCuPmeAdminProfile object. If
efmCuPmeAdminProfile is zero, then efmCuAdminProfile object of the efmCuPmeAdminProfile is zero, then efmCuAdminProfile object of the
PCS port, connected to the PME, determines the configuration profile PCS port, connected to the PME, determines the configuration profile
(or a list of possible profiles) for that PME. This mechanism allows (or a list of possible profiles) for that PME. This mechanism allows
to specify a common profile(s) for all PMEs connected to the PCS to specify a common profile(s) for all PMEs connected to the PCS
port, with an ability to change individual PME profiles by setting port, with an ability to change individual PME profiles by setting
efmCuPmeAdminProfile objects, which overwrites profile set by efmCuPmeAdminProfile object, which overwrites profile set by
efmCuAdminProfile. efmCuAdminProfile.
A current operating PME profile is pointed to by efmCuPmeOperProfile A current operating PME profile is pointed to by efmCuPmeOperProfile
object. Note that this profile entry, can be created automatically, object. Note that this profile entry, can be created automatically,
to reflect achieved parameters in adaptive (not fixed) to reflect achieved parameters in adaptive (not fixed)
initialization. initialization.
4.3 Mapping of IEEE 802.3ah Managed Objects 4.3. Mapping of IEEE 802.3ah Managed Objects
This section contains the mapping between managed objects This section contains the mapping between managed objects
(attributes) defined in [802.3ah] Clause 30, and managed objects (attributes) defined in [802.3ah] Clause 30, and managed objects
defined in this document and in associated MIB modules, i.e., the defined in this document and in associated MIB modules, i.e., the IF-
IF-MIB [RFC2863]. MIB [RFC2863].
Note that majority of the objects defined in this MIB module do not Note that majority of the objects defined in this MIB module do not
have direct counterparts in Clause 30 and instead refer to Clause 45 have direct counterparts in Clause 30 and instead refer to Clause 45
registers. registers.
*EdNote: It would be a good idea to update Clause 30 of 802.3ah after
this MIB module is approved. I guess this should be done via a
maintanence request. *
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| IEEE 802.3 Managed Object | Corresponding SNMP Object | | IEEE 802.3 Managed Object | Corresponding SNMP Object |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| oPAF - Basic Package | | | oPAF - Basic Package | |
| (Mandatory) | | | (Mandatory) | |
| aPAFID | ifIndex (IF-MIB) | | aPAFID | ifIndex (IF-MIB) |
| aPhyEnd | efmCuPhySide | | aPhyEnd | efmCuPhySide |
| aPHYCurrentStatus | efmCuStatus | | aPHYCurrentStatus | efmCuStatus |
| aPAFSupported | efmCuPAFSupported | | aPAFSupported | efmCuPAFSupported |
| oPAF - PME Aggregation Package | | | oPAF - PME Aggregation Package | |
skipping to change at page 13, line 29 skipping to change at page 12, line 48
| aRemotePAFSupported | efmCuRemotePAFSupported | | aRemotePAFSupported | efmCuRemotePAFSupported |
| aRemotePAFCapacity | efmCuRemotePAFCapacity | | aRemotePAFCapacity | efmCuRemotePAFCapacity |
| aRemotePMEAggregate | | | aRemotePMEAggregate | |
| oPME - 10P/2B Package | | | oPME - 10P/2B Package | |
| (Mandatory) | | | (Mandatory) | |
| aPMEID | ifIndex (IF-MIB) | | aPMEID | ifIndex (IF-MIB) |
| aPMEAdminState | ifAdminState (IF-MIB) | | aPMEAdminState | ifAdminState (IF-MIB) |
| aPMEStatus | efmCuPmeStatus | | aPMEStatus | efmCuPmeStatus |
| aPMESNRMgn | efmCuPmeSnrMgn | | aPMESNRMgn | efmCuPmeSnrMgn |
| aTCCodingViolations | efmCuPmeTCCodingErrors | | aTCCodingViolations | efmCuPmeTCCodingErrors |
| aTCCRCErrors | efmCuPmeTCCrcErrors |
| aProfileSelect | efmCuAdminProfile, | | aProfileSelect | efmCuAdminProfile, |
| | efmCuPmeAdminProfile | | | efmCuPmeAdminProfile |
| aOperatingProfile | efmCuPmeOperProfile | | aOperatingProfile | efmCuPmeOperProfile |
| aPMEFECCorrectedBlocks | efmCuPme10PFECCorrectedBlocks | | aPMEFECCorrectedBlocks | efmCuPme10PFECCorrectedBlocks |
| aPMEFECUncorrectableBlocks | efmCuPme10PFECUncorrectedBlocks | | aPMEFECUncorrectableBlocks | efmCuPme10PFECUncorrectedBlocks |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
Table 2 Table 2
5. Definitions 5. Definitions
EFM-CU-MIB DEFINITIONS ::= BEGIN EFM-CU-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32,
Unsigned32, Counter32, mib-2 Unsigned32, Counter32, mib-2
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- RFC 2580]
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- [RFC3411] FROM SNMP-FRAMEWORK-MIB -- RFC 3411
ifIndex, ifSpeed, InterfaceIndex ifIndex, ifSpeed, InterfaceIndex
FROM IF-MIB -- [RFC2863] FROM IF-MIB -- RFC 2863
; ;
efmCuMIB MODULE-IDENTITY efmCuMIB MODULE-IDENTITY
LAST-UPDATED "200504040000Z" -- April 04, 2005 LAST-UPDATED "200510240000Z" -- October 24, 2005
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://www.ietf.org/html.charters/hubmib-charter.html http://www.ietf.org/html.charters/hubmib-charter.html
Mailing Lists: Mailing Lists:
General Discussion: hubmib@ietf.org General Discussion: hubmib@ietf.org
To Subscribe: hubmib-request@ietf.org To Subscribe: hubmib-request@ietf.org
In Body: subscribe your_email_address In Body: subscribe your_email_address
skipping to change at page 14, line 31 skipping to change at page 14, line 4
Chair: Dan Romascanu Chair: Dan Romascanu
Postal: Avaya Postal: Avaya
Atidim Technology Park, Bldg. 3 Atidim Technology Park, Bldg. 3
Tel Aviv 61131 Tel Aviv 61131
Israel Israel
Tel: +972 3 645 8414 Tel: +972 3 645 8414
E-mail: dromasca@avaya.com E-mail: dromasca@avaya.com
Editor: Edward Beili Editor: Edward Beili
Postal: Actelis Networks Inc. Postal: Actelis Networks Inc.
25 Bazel St., P.O.B. 10173 25 Bazel St., P.O.B. 10173
Petach-Tikva 10173 Petach-Tikva 10173
Israel Israel
Tel: +972-3-924-3491 Tel: +972-3-924-3491
E-mail: edward.beili@actelis.com" E-mail: edward.beili@actelis.com"
DESCRIPTION DESCRIPTION
"The objects in this MIB module are used to manage "The objects in this MIB module are used to manage
the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces
2BASE-TL and 10PASS-TS, defined in IEEE Draft P802.3ah/D3.3. 2BASE-TL and 10PASS-TS, defined in IEEE Std. 802.3ah-2004.
The following reference is used throughout this MIB module: The following reference is used throughout this MIB module:
[802.3ah] refers to: [802.3ah] refers to:
IEEE Std 802.3ah-2004: 'IEEE Standard for Information IEEE Std 802.3ah-2004: 'IEEE Standard for Information
technology - Telecommunications and information exchange technology - Telecommunications and information exchange
between systems - Local and metropolitan area networks - between systems - Local and metropolitan area networks -
Specific requirements - Specific requirements -
Part 3: Carrier Sense Multiple Access with Collision Part 3: Carrier Sense Multiple Access with Collision
Detection (CSMA/CD) Access Method and Physical Layer Detection (CSMA/CD) Access Method and Physical Layer
skipping to change at page 15, line 30 skipping to change at page 15, line 4
EFMCu - EFM Copper EFMCu - EFM Copper
MDIO - Management Data Input/Output MDIO - Management Data Input/Output
Mgn - Margin Mgn - Margin
PAF - PME Aggregation Function PAF - PME Aggregation Function
PCS - Physical Coding Sublayer PCS - Physical Coding Sublayer
PMD - Physical Medium Dependent PMD - Physical Medium Dependent
PME - Physical Medium Entity PME - Physical Medium Entity
PSD - Power Spectral Density PSD - Power Spectral Density
SNR - Signal to Noise Ratio SNR - Signal to Noise Ratio
TCPAM - Trellis Coded Pulse Amplitude Modulation TCPAM - Trellis Coded Pulse Amplitude Modulation
Copyright (C) The Internet Society (2004). This version Copyright (C) The Internet Society (2004). This version
of this MIB module is part of RFC XXXX; see the RFC of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices." itself for full legal notices."
REVISION "200510240000Z" -- October 24, 2005
DESCRIPTION "Initial version, published as RFC XXXX."
-- EdNote: Replace XXXX with the actual RFC number & -- EdNote: Replace XXXX with the actual RFC number &
-- remove this note -- remove this note
REVISION "200504040000Z" -- April 04, 2005 ::= { mib-2 YYY }
DESCRIPTION "Initial version, published as RFC XXXX."
::= { mib-2 160 }
-- EdNote: Replace YYY with a real OID once it is -- EdNote: Replace YYY with a real OID once it is
-- allocated & remove this note. -- allocated & remove this note.
-- Sections of the module -- Sections of the module
efmCuObjects OBJECT IDENTIFIER ::= { efmCuMIB 1 } efmCuObjects OBJECT IDENTIFIER ::= { efmCuMIB 1 }
efmCuConformance OBJECT IDENTIFIER ::= { efmCuMIB 2 } efmCuConformance OBJECT IDENTIFIER ::= { efmCuMIB 2 }
-- Groups in the module -- Groups in the module
efmCuPort OBJECT IDENTIFIER ::= { efmCuObjects 1 } efmCuPort OBJECT IDENTIFIER ::= { efmCuObjects 1 }
efmCuPme OBJECT IDENTIFIER ::= { efmCuObjects 2 } efmCuPme OBJECT IDENTIFIER ::= { efmCuObjects 2 }
-- Textual Conventions -- Textual Conventions
ProfileIndex ::= TEXTUAL-CONVENTION ProfileIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
skipping to change at page 20, line 17 skipping to change at page 19, line 39
efmCuPortSide. efmCuPortSide.
The value of this object is a list of up to 6 indices of The value of this object is a list of up to 6 indices of
Profiles. If this list consists of a single Profile index, Profiles. If this list consists of a single Profile index,
then all PMEs assigned to this EFMCu port SHALL be configured then all PMEs assigned to this EFMCu port SHALL be configured
according to the Profile referenced by that index, unless it according to the Profile referenced by that index, unless it
is overwritten by corresponding non-zero efmCuPmeAdminProfile, is overwritten by corresponding non-zero efmCuPmeAdminProfile,
which takes precedence over efmCuAdminProfile. which takes precedence over efmCuAdminProfile.
The list, consisting of more than one index, allows each PME The list, consisting of more than one index, allows each PME
in the port to be configured according to any Profile in the port to be configured according to any Profile
specified in the list. specified in the list.
By default this object has a single profile index 1, By default this object has a value of 0x01, referencing 1st
referencing 1st entry in efmCuPme2BProfileTable/ entry in efmCuPme2BProfileTable or efmCuPme10PProfileTable.
efmCuPme2BProfileTable.
This object is writable and readable for the -O subtype This object is writable and readable for the -O subtype
(2BaseTL-O or 10PassTS-O) EFMCu ports. It is unavailable for (2BaseTL-O or 10PassTS-O) EFMCu ports. It is unavailable for
the -R subtype (2BaseTL-R or 10PassTS-R) ports. the -R subtype (2BaseTL-R or 10PassTS-R) ports.
Note that current operational Profile value is available via Note that current operational Profile value is available via
efmCuPmeOperProfile object. efmCuPmeOperProfile object.
Modification of this object must be performed when the link is Modification of this object must be performed when the link is
Down. Attempts to change this object MUST be rejected, if the Down. Attempts to change this object MUST be rejected, if the
skipping to change at page 22, line 27 skipping to change at page 21, line 48
Note that current SNR Margin of the PMEs comprising the EFMCu Note that current SNR Margin of the PMEs comprising the EFMCu
port is represented by efmCuPmeSnrMgn. port is represented by efmCuPmeSnrMgn.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"[802.3ah] 61.1.2" "[802.3ah] 61.1.2"
::= { efmCuPortConfEntry 5 } ::= { efmCuPortConfEntry 5 }
efmCuThreshLowBandwidth OBJECT-TYPE efmCuThreshLowBandwidth OBJECT-TYPE
SYNTAX Unsigned32(0..100000) SYNTAX Unsigned32(400..100000)
UNITS "Kbps" UNITS "Kbps"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the EFMCu port Low Bandwidth alarm "This object configures the EFMCu port Low Bandwidth alarm
threshold. When the current value of ifSpeed for this port threshold. When the current value of ifSpeed for this port
reaches or drops below this threshold, an reaches or drops below this threshold, an
efmCuLowBandwidth notification MAY be generated if enabled by efmCuLowBandwidth notification MAY be generated if enabled by
efmCuLowBandwidthEnable. efmCuLowBandwidthEnable.
The value of 0 means no efmCuLowBandwidth notifications
SHALL ever be generated.
This object is read-write for the -O subtype EFMCu ports This object is read-write for the -O subtype EFMCu ports
(2BaseTL-O/10PassTS-O) and not available for the -R subtypes. (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
::= { efmCuPortConfEntry 6 } ::= { efmCuPortConfEntry 6 }
efmCuLowBandwidthEnable OBJECT-TYPE efmCuLowBandwidthEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at page 41, line 6 skipping to change at page 40, line 23
EfmCuPmeStatusEntry ::= EfmCuPmeStatusEntry ::=
SEQUENCE { SEQUENCE {
efmCuPmeOperStatus INTEGER, efmCuPmeOperStatus INTEGER,
efmCuPmeFltStatus BITS, efmCuPmeFltStatus BITS,
efmCuPmeOperSubType INTEGER, efmCuPmeOperSubType INTEGER,
efmCuPmeOperProfile ProfileIndexOrZero, efmCuPmeOperProfile ProfileIndexOrZero,
efmCuPmeSnrMgn Integer32, efmCuPmeSnrMgn Integer32,
efmCuPmePeerSnrMgn Integer32, efmCuPmePeerSnrMgn Integer32,
efmCuPmeLineAtn Integer32, efmCuPmeLineAtn Integer32,
efmCuPmePeerLineAtn Integer32, efmCuPmePeerLineAtn Integer32,
efmCuPmeTCCodingErrors Counter32 efmCuPmeTCCodingErrors Counter32,
efmCuPmeTCCrcErrors Counter32
} }
efmCuPmeOperStatus OBJECT-TYPE efmCuPmeOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), up(1),
downNotReady(2), downNotReady(2),
downReady(3), downReady(3),
init(4) init(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 46, line 12 skipping to change at page 45, line 30
The value of zero SHALL be returned when PME is down or The value of zero SHALL be returned when PME is down or
initializing. initializing.
If a Clause 45 MDIO Interface to the PME TC is present, then If a Clause 45 MDIO Interface to the PME TC is present, then
this object maps to the TC coding violations register this object maps to the TC coding violations register
(see 45.2.6.12)." (see 45.2.6.12)."
REFERENCE REFERENCE
"[802.3ah] 61.3.3.1, 45.2.6.12" "[802.3ah] 61.3.3.1, 45.2.6.12"
::= { efmCuPmeStatusEntry 9 } ::= { efmCuPmeStatusEntry 9 }
efmCuPmeTCCrcErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A number of TC-CRC errors. This counter is incremented for
each TC-CRC error detected by the 64/65-octet receive function
(see 61.3.3.3 and Figure 61-19).
The value of zero SHALL be returned when PME is down or
initializing.
If a Clause 45 MDIO Interface to the PCME TC is present, then
this object maps to the TC CRC error register
(see 45.2.6.11)."
REFERENCE
"[802.3ah] 61.3.3.3, 45.2.6.11"
::= { efmCuPmeStatusEntry 10 }
-- 2BASE-TL specific PME group -- 2BASE-TL specific PME group
efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 } efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 }
efmCuPme2BProfileTable OBJECT-TYPE efmCuPme2BProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme2BProfileEntry SYNTAX SEQUENCE OF EfmCuPme2BProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table supports definitions of administrative and "This table supports definitions of administrative and
operating Profiles for 2BASE-TL PMEs. operating Profiles for 2BASE-TL PMEs.
First 14 entries in this table SHALL always be defined as First 14 entries in this table SHALL always be defined as
follows (see 802.3ah Annex 63A): follows (see 802.3ah Annex 63A):
-------+------+-----+--------+------------------ -------+------+-----+--------+------------------
Profile Rate Power Region Constellation Profile Rate Power Region Constellation
index (Kbps) (dBm) (G.991.2) index (Kbps) (dBm) (G.991.2)
-------+------+-----+--------+------------------ -------+------+-----+--------+------------------
1 512 13.5 1 16-TCPAM (default) 1 5696 13.5 1 32-TCPAM (default)
2 704 13.5 1 16-TCPAM 2 3072 13.5 1 32-TCPAM
3 1024 13.5 1 16-TCPAM 3 2048 13.5 1 16-TCPAM
4 2048 13.5 1 16-TCPAM 4 1024 13.5 1 16-TCPAM
5 3072 13.5 1 32-TCPAM 5 704 13.5 1 16-TCPAM
6 5696 13.5 1 32-TCPAM 6 512 13.5 1 16-TCPAM
7 512 13.5 2 16-TCPAM 7 5696 14.5 2 32-TCPAM
8 704 13.5 2 16-TCPAM 8 3072 14.5 2 32-TCPAM
9 1024 13.5 2 16-TCPAM 9 2048 14.5 2 16-TCPAM
10 2048 14.5 2 16-TCPAM 10 1024 13.5 2 16-TCPAM
11 3072 14.5 2 32-TCPAM 11 704 13.5 2 16-TCPAM
12 5696 14.5 2 32-TCPAM 12 512 13.5 2 16-TCPAM
13 0 0 1 0 (best effort) 13 0 0 1 0 (best effort)
14 0 0 2 0 (best effort) 14 0 0 2 0 (best effort)
These default entries SHALL be created during agent These default entries SHALL be created during agent
initialization and MUST not be deleted. initialization and MUST not be deleted.
Entries following the first 14, can be dynamically created and Entries following the first 14, can be dynamically created and
deleted, to provide custom administrative (configuration) deleted, to provide custom administrative (configuration)
profiles and automatic operating profiles. profiles and automatic operating profiles.
skipping to change at page 63, line 46 skipping to change at page 63, line 35
efmCuPmeSubTypesSupported, efmCuPmeSubTypesSupported,
efmCuPmeAdminSubType, efmCuPmeAdminSubType,
efmCuPmeOperSubType, efmCuPmeOperSubType,
efmCuPAFRemoteDiscoveryCode, efmCuPAFRemoteDiscoveryCode,
efmCuPmeOperProfile, efmCuPmeOperProfile,
efmCuPmeSnrMgn, efmCuPmeSnrMgn,
efmCuPmePeerSnrMgn, efmCuPmePeerSnrMgn,
efmCuPmeLineAtn, efmCuPmeLineAtn,
efmCuPmePeerLineAtn, efmCuPmePeerLineAtn,
efmCuPmeTCCodingErrors, efmCuPmeTCCodingErrors,
efmCuPmeTCCrcErrors,
efmCuPmeThreshLineAtn, efmCuPmeThreshLineAtn,
efmCuPmeThreshSnrMgn efmCuPmeThreshSnrMgn
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about "A collection of objects providing information about
a 2BASE-TL/10PASS-TS PME." a 2BASE-TL/10PASS-TS PME."
::= { efmCuGroups 5 } ::= { efmCuGroups 5 }
efmCuAlarmConfGroup OBJECT-GROUP efmCuAlarmConfGroup OBJECT-GROUP
skipping to change at page 69, line 40 skipping to change at page 69, line 33
Mathias Riess Mathias Riess
Matt Squire Matt Squire
Mike Heard Mike Heard
Udi Ashkenazi Udi Ashkenazi
9. References 9. References
9.1 Normative References 9.1. Normative References
[802.3ah] IEEE, "IEEE Standard for Information technology - [802.3ah] IEEE, "IEEE Standard for Information technology -
Telecommunications and information exchange between Telecommunications and information exchange between
systems - Local and metropolitan area networks - Specific systems - Local and metropolitan area networks - Specific
requirements - Part 3: Carrier Sense Multiple Access with requirements - Part 3: Carrier Sense Multiple Access with
Collision Detection (CSMA/CD) Access Method and Physical Collision Detection (CSMA/CD) Access Method and Physical
Layer Specifications - Amendment: Media Access Control Layer Specifications - Amendment: Media Access Control
Parameters, Physical Layers and Management Parameters for Parameters, Physical Layers and Management Parameters for
Subscriber Access Networks", IEEE Std 802.3ah-2004, Subscriber Access Networks", IEEE Std 802.3ah-2004,
September 2004. September 2004.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction to Version 3 of the Internet-standard
Network Management Framework", RFC 2570, April 1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, RFC Management Information Version 2 (SMIv2)", STD 58,
2578, April 1999. RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Textual McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
Conventions for SMIv2", STD 58, RFC 2579, April 1999. Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for Internet-
Internet-Standard Management Framework", RFC 3410, Standard Management Framework", RFC 3410, December 2002.
December 2002.
9.2 Informative References 9.2. Informative References
[G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber Line [G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber Line
(SHDSL) transceivers", ITU-T Recommendation G.991.2, (SHDSL) transceivers", ITU-T Recommendation G.991.2,
December 2003. December 2003.
[G.993.1] ITU-T, "Very High speed Digital Subscriber Line [G.993.1] ITU-T, "Very High speed Digital Subscriber Line
transceivers", ITU-T Recommendation G.993.1, June 2004. transceivers", ITU-T Recommendation G.993.1, June 2004.
[I-D.ietf-adslmib-gshdslbis] [I-D.ietf-adslmib-gshdslbis]
Sikes, C., Ray, B. and R. Abbi, "Definitions of Managed Sikes, C., Ray, B., and R. Abbi, "Definitions of Managed
Objects for G.shdsl.bis Lines", Objects for G.shdsl.bis Lines",
draft-ietf-adslmib-gshdslbis-09 (work in progress), March draft-ietf-adslmib-gshdslbis-11 (work in progress),
2005. May 2005.
[I-D.ietf-adslmib-vdsl-ext-mcm]
Dodge, M. and B. Ray, "Definitions of Managed Object
Extensions for Very High Speed Digital Subscriber Lines
(VDSL) Using Multiple Carrier Modulation (MCM) Line
Coding", draft-ietf-adslmib-vdsl-ext-mcm-06 (work in
progress), January 2005.
[I-D.ietf-hubmib-efm-epon-mib] [I-D.ietf-hubmib-efm-epon-mib]
Khermosh, L., "Managed Objects for the Ethernet Passive Khermosh, L., "Managed Objects for the Ethernet Passive
Optical Networks", draft-ietf-hubmib-efm-epon-mib-03 (work Optical Networks", draft-ietf-hubmib-efm-epon-mib-03 (work
in progress), March 2005. in progress), March 2005.
[I-D.ietf-hubmib-efm-mib] [I-D.ietf-hubmib-efm-mib]
Squire, M., "Ethernet in the First Mile (EFM) Common MIB", Squire, M., "Ethernet in the First Mile (EFM) Common MIB",
draft-ietf-hubmib-efm-mib-03 (work in progress), March draft-ietf-hubmib-efm-mib-03 (work in progress),
2005. March 2005.
[I-D.ietf-hubmib-rfc3636bis] [I-D.ietf-hubmib-rfc3636bis]
Beili, E., "Definitions of Managed Objects for IEEE 802.3 Beili, E., "Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs)", Medium Attachment Units (MAUs)",
draft-ietf-hubmib-rfc3636bis-00 (work in progress), draft-ietf-hubmib-rfc3636bis-02 (work in progress),
October 2004. October 2005.
[IANAifType-MIB] [IANAifType-MIB]
Internet Assigned Numbers Authority (IANA), "IANAifType Internet Assigned Numbers Authority (IANA), "IANAifType
Textual Convention definition", Textual Convention definition",
http://www.iana.org/assignments/ianaiftype-mib. http://www.iana.org/assignments/ianaiftype-mib.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table [RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table
Extension to the Interfaces Group MIB", RFC 2864, June Extension to the Interfaces Group MIB", RFC 2864,
2000. June 2000.
[RFC3635] Flick, J., "Definitions of Managed Objects for the [RFC3635] Flick, J., "Definitions of Managed Objects for the
Ethernet-like Interface Types", RFC 3635, September 2003. Ethernet-like Interface Types", RFC 3635, September 2003.
[RFC4070] Dodge, M. and B. Ray, "Definitions of Managed Object
Extensions for Very High Speed Digital Subscriber Lines
(VDSL) Using Multiple Carrier Modulation (MCM) Line
Coding", RFC 4070, May 2005.
Author's Address Author's Address
Edward Beili Edward Beili
Actelis Networks Actelis Networks
Bazel 25 Bazel 25
Petach-Tikva Petach-Tikva
Israel Israel
Phone: +972-3-924-3491 Phone: +972-3-924-3491
EMail: edward.beili@actelis.com Email: edward.beili@actelis.com
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
 End of changes. 72 change blocks. 
186 lines changed or deleted 182 lines changed or added

This html diff was produced by rfcdiff 1.27, available from http://www.levkowetz.com/ietf/tools/rfcdiff/