wdiff draft-ietf-hubmib-efm-cu-mib-05.txt draft-ietf-hubmib-efm-cu-mib-06.txt

Network Working Group E. Beili
Internet-Draft Actelis Networks
Expires: December 19, 2006 June 17, April 15, 2007 October 12, 2006

Ethernet in the First Mile Copper (EFMCu) Interfaces MIB
draft-ietf-hubmib-efm-cu-mib-05.txt
draft-ietf-hubmib-efm-cu-mib-06.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 December 19, 2006. April 15, 2007.

Abstract

This document defines a Management Information Base (MIB) module modules for
use with network management protocols in TCP/IP based internets.
This document proposes an extension to the Ethernet-like Interfaces
MIB and MAU MIB modules with a set of objects for managing an Ethernet
in the First Mile Copper (EFMCu) interfaces 10PASS-TS and 2BASE-TL,
defined in IEEE Std 802.3ah-2004. In addition a set of objects is
defined, describing cross-connect capability of a managed device with
multi-layer (stacked) interfaces, extending the stack management
objects in the Interfaces Group MIB and the Inverted Stack Table MIB
modules.

Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Relation to other MIB modules . . . . . . . . . . . . . . . . 4
3.1. Relation to Interfaces Group MIB module . . . . . . . . . 4
3.1.1. Layering Model . . . . . . . . . . . . . . . . . . . . 4
3.1.2. PME Aggregation Function (PAF) . . . . . . . . . . . . 6
3.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 6 7
3.1.4. EFMCu ports initialization . . . . . . . . . . . . . . 8 9
3.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 8 9
3.2. Relation to SHDSL MIB module . . . . . . . . . . . . . . . 9 10
3.3. Relation to VDSL MIB module . . . . . . . . . . . . . . . 10
3.4. Relation to Ethernet-Like and MAU MIB modules . . . . . . 10 11
4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 11 12
4.1. EFM Copper MIB Overview . . . . . . . . . . . . . . . . . 12
4.2. Interface stack capability MIB Overview . . . . . . . . . 11
4.2. 12
4.3. PME Profiles . . . . . . . . . . . . . . . . . . . . . . . 11
4.3. 13
4.4. Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 12 13
5. Interface Stack Capability MIB Definitions . . . . . . . . . . 14
6. EFM Copper MIB Definitions . . . . . . . . . . . . . . . . . 13
6. . 21
7. Security Considerations . . . . . . . . . . . . . . . . . . . 75
7. 82
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 77
8. 83
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 77
9. 83
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 77
9.1. 84
10.1. Normative References . . . . . . . . . . . . . . . . . . . 77
9.2. 84
10.2. Informative References . . . . . . . . . . . . . . . . . . 78 85
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 80 87
Intellectual Property and Copyright Statements . . . . . . . . . . 81 88

1. Introduction

New Ethernet-like interfaces have been defined in the Institute of
Electrical and Electronics Engineers (IEEE) Standard 802.3ah-2004
[802.3ah], a.k.a. Ethernet in the First Mile (EFM), which is now a
part of the base IEEE Standard 802.3-2005 [802.3]. In particular
2BASE-TL and 10PASS-TS physical interfaces (PHYs), defined over
voice-grade copper pairs, have been specified for the long and short
reach respectively. These interfaces, collectively called EFMCu, are
based on ITU-T G.SHDSL [G.991.2] and VDSL [G.993.1] specifications
and support variable rates and optional Physical Medium Entity (PME)
aggregation (a.k.a. multi-pair bonding).

2BASE-TL PHY is capable of providing at least 2Mbps over 2700 m long
single copper pair with a mean Bit Error Rate (BER) of 10^-7 (using
5dB target noise margin).

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
margin).

This memo defines a Management Information Base (MIB) module for use
with network management protocols in the Internet community to manage
EFMCu interfaces. In addition a MIB module is defined describing
cross-connect capability of a stacked interface.

Note that managed objects for Operation, Administration and
Management (OAM) and Ethernet over Passive Optical Networks (EPON)
clauses of IEEE 802.3ah are defined in EFM-COMMON-MIB [I-D.ietf-
hubmib-efm-mib] and EFM-EPON-MIB [I-D.ietf-hubmib-efm-epon-mib]
respectively.

2. The Internet-Standard Management Framework

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].

The 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 RFC 2119 [RFC2119].

3. Relation to other MIB modules

This section outlines the relationship of this the MIB modules defined in
this document with other MIB modules described in the relevant RFCs.
Specifically, Interfaces Group MIB (IF-MIB), Ethernet-Like
(EtherLike-MIB), MAU (MAU-MIB), SHDSL (HDSL2-SHDSL-LINE-MIB) and VDSL
(VDSL-LINE-EXT-MCM-MIB) are discussed.

3.1. Relation to Interfaces Group MIB module

2BASE-TL and 10PASS-TS PHY's specified in this MIB the EFM-CU-MIB module are
stacked (a.k.a. aggregated or bonded) Ethernet interfaces and as such
are managed using generic interface management objects defined in the
IF-MIB [RFC2863].

The stack
management management, i.e. actual connection of the sub-layers to the
top layer interface, is done via the ifStackTable, as defined in the
IF-MIB [RFC2863] and its inverse ifInvStackTable, as defined in the IF-INVERTED-STACK-
MIB
IF-INVERTED-STACK-MIB [RFC2864].

The new tables ifCapStackTable and its inverse ifInvCapStackTable
defined in the IF-CAP-STACK-MIB module below, extend the stack
management with an ability to describe possible connections or cross-
connect capability, when a flexible cross-connect matrix is present
between the interface layers.

3.1.1. Layering Model

An EFMCu interface can aggregate up to 32 Physical Medium Entity
(PME) sub-layer devices (modems), using so called PME Aggregation
Function (PAF).

A generic EFMCu device can have a number of Physical Coding Sublayer
(PCS) ports, each connected to a MAC via Medium Independent Interface
(MII) at the upper layer, and cross-connected to a number of
underlying PMEs, with a single PCS per PME relationship, see clause
61.1 of [802.3ah] for more details.

Each PME in the aggregated EFMCu port is represented in the Interface
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
[IANAifType-MIB].

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
value SHALL be returned when PME is initializing or down.

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
encapsulation overhead and PAF overhead, but accounting for the
Inter-Frame Gaps (IFG).

When using the stated definition of ifSpeed for the PCS, there would
be no frame loss in the following configuration (the test-sets are
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
interfaces are aggregated, to achieve the shown speed):

[testset]--10BaseT--[CO]--2BaseTL--[CPE]--10BaseT--[testset]
ifSpeed= 10Mbps 10Mbps 10Mbps

[testset]--100BaseT--[CO]--10PassTS--[CPE]--100BaseT--[testset]
ifSpeed= 100Mbps 100Mbps 100Mbps

Figure 1: Example configuration with no frame loss

The following figure shows the layering diagram and corresponding use
of ifTable and ifMauTable:

_________________________ _
| LLC | |
+-------------------------+ | 1 ifEntry
| MAC | | ifType: ethernetCsmacd(6)
+-------------------------+ > ifMauEntry
| Reconsiliation | | ifMauType: dot3MauType2BaseTL or
+-------------------------+ | dot3MauType10PassTS
| PCS | |
+-------------+---+-------+ +
| TC \ | | | |
+-----\ | | | |
| PMA > PME 1 |...| PME N | > N ifEntry (N=1..32)
+-----/ | | | | ifType: shdsl(169) or vdsl(97)
| PMD/ | | | |
-------------+---+------- -

Figure 2: Use of ifTable and ifMauTable for EFMCu ports

The ifStackTable is indexed by the ifIndex values of the aggregated
EFMCu port (PCS) and the PMEs connected to it. ifStackTable allows a
Network Management application to determine which PMEs are connected
to a particular PCS and change connections (if supported by the
application). The ifInvStackTable, being an inverted version of the
ifStackTable, provides an efficient means for a Network Management
application to read a subset of the ifStackTable and thereby
determine which PCS runs on top of a particular PME.

A new table ifAvailableStackTable ifCapStackTable defined in this MIB the IF-CAP-STACK-MIB module,
specifies for each higher-layer interface (e.g. PCS port) a list of PMEs,
lower-layer interfaces (e.g. PMEs), which can possibly be cross-
connected to that PCS, higher-layer interface, determined by the cross-connect cross-
connect capability of the device. This table, modeled after
ifStackTable, is read only, reflecting current cross-connect capability,
capability of a stacked interface, which can be dynamic in some
implementations (e.g. if PMEs are located on a pluggable module and
the module is pulled out). Note that PME availability per PCS,
described by ifAvailableStackTable, ifCapStackTable, can be constrained by other parameters,
for example by aggregation capacity of a PCS or by the PME in
question being already connected to another PCS. So, in order to
ensure that a particular PME can be connected to the PCS, all
respective parameters (e.g. ifAvailableStackTable, ifCapStackTable, ifStackTable and
efmCuPAFCapacity) SHALL be inspected.

3.1.2. PME Aggregation Function (PAF)

The PME Aggregation Function (PAF) allows a number of PMEs to ifInvCapStackTable, also defined in the IF-CAP-STACK-MIB module,
describes which higher-layer interfaces (e.g. PCS ports) can
possibly be
aggregated onto connected to a PCS port, by fragmenting the Ethernet frames,
transmitting particular lower-layer interface (e.g.
PME), providing inverted mapping of ifCapStackTable. While it
contains no additional information beyond that already contained in
the fragments over multiple PMEs and assembling ifCapStackTable, the
original frames at ifInvCapStackTable has the remote ifIndex values in
its INDEX clause in the reverse order, i.e., the lower-layer
interface first, and the higher-layer interface second, providing an
efficient means for a Network Management application to read a subset
of the ifCapStackTable and thereby determine which interfaces can be
connected to run on top of a particular interface.

3.1.2. PME Aggregation Function (PAF)

The PME Aggregation Function (PAF) allows a number of PMEs to be
aggregated onto a PCS port, by fragmenting the Ethernet frames,
transmitting the fragments over multiple PMEs and assembling the
original frames at the remote port. PAF is OPTIONAL, meaning that a
device with a single PME MAY perform fragmentation and re-assembly if
this function is supported by the device. Note however that the
agent is REQUIRED to report on the PAF capability for all EFMCu ports
(2BASE-TL and 10PASS-TS).

This MIB

The EFM-CU-MIB module allows a Network Management application to
query PAF capability and enable/disable it if supported. Note that
enabling PAF effectively turns on fragmentation and re-assembly, even
on a single-PME port.

3.1.3. Discovery Operation

The EFMCu ports may optionally support discovery operation, whereby
PMEs, during initialization, exchange information about their
respective aggregation groups (PCS). This information can then be
used to detect copper misconnections or for an automatic assignment
of the local PMEs into aggregation groups instead of a fixed pre-
configuration.

This

The MIB module allows modules defined in this document allow a Network Management
application to control EFM Discovery mechanism and query its results.
Note that the Discovery mechanism can work only if PAF is supported
and enabled.

Two tables are used by the EFM Discovery mechanism: ifStackTable and
ifAvailableStackTable defined.
ifCapStackTable. The following pseudo-code defines gives an example of the
Discovery and automatic PME assignment for a generic PAF enabled
multi-PCS EFMCu device, located at Central Office (CO), using objects
defined in this these MIB module. modules and in IF-MIB [Note that automatic PME
assignment is only shown here for the purposes of the example. Fixed
PME pre-assignment, manual assignment or auto-assignment by using an
alternative internal algorithm may be chosen by a particular
implementation]:

// Go over all PCS ports in the CO device
FOREACH pcs[i] IN co_device CO_device
{ // Discover Perform discovery and auto-assignment only on PAF enabled ports
// with room for more PMEs
IF ( pcs[i].PAFSupported AND pcs[i].NumPMEs < pcs[i].PAFCapacity )
{ dc = pcs[i].DiscoveryCode = MAC[i]; // unique 6 Byte per PCS
// go Go over all currently disconnected PMEs, which can
// pottentially be connected to PCS[i] the PCS
FOREACH pme[j] IN ifAvailableStackTable[pcs[i]] ifCapStackTable[pcs[i]] AND
NOT IN ifInvStackTable[pme[j]] // unassigned not connected
{ // Try to grab the remote RT_device, by writing the value
// of the local 6 Byte discovery code to the remote
// discovery code register (via handshake mechanism).
// This operation is atomic Set-if-Clear action, i.e. it
// would succeed only if the remote discovery register was
// zero. Read the remote discovery code register via Get
// operation to see if the RT_device, attached via the PME
// is indeed marked as being the CO_device peer.
pme[j].RemoteDiscoveryCode = dc; // Set if Clear Set-if-Clear
r = pme[j].RemoteDiscoveryCode; // Get
IF ( r == dc AND pcs[i].NumPMEs < pcs[i].PAFCapacity)
{ // Remote CPE RT_device connected via PME[j] is/was a peer
// for PCS[i] and there room for another PME in the
// PCS[i] aggregation group (max. PAF capacity is not
// reached yet).
// PCS[i]. Connect this PME to the PCS (there's room) (via ifStackTable,
// ifInvStackTable being inverse of ifStackTable is
// updated automatically)
ADD pme[j] TO ifStackTable[pcs[i]];
// pcs[i] is auto-added to ifInvStackTable[pme[j]]
pcs[i].NumPMEs = pcs[i].NumPMEs + 1;
// Discover all other currently disconnected PMEs,
// attached to the same CPE RT_device and connect them to
// the PCS
// provided there is enough room for more PMEs.
FOREACH pme[k] IN ifAvailableStackTable[pcs[i]] ifCapStackTable[pcs[i]] and
NOT IN ifInvStackTable[pme[k]]
{ r = pme[k].RemoteDiscoveryCode; // Get
IF ( r == dc AND
pcs[i].NumPMEs < pcs[i].PAFCapacity)
{ ADD pme[k] TO ifStackTable[pcs[i]];
// pcs[i] is added TO ifInvStackTable[pme[k]]
pcs[i].NumPMEs = pcs[i].NumPMEs + 1;
}
}
}
// Discovered At this point we have discovered all local PMEs which lead to the
// are physically connected to the same CPE and remote RT_device
// and connected them to PCS[i]. Go to the next PCS.
BREAK;
}
}
}

The

An SNMP Agent for a EFMCu device builds efmCuStackTable ifCapStackTable and its
inverse ifInvCapStackTable according to the information contained in
the Clause 45 PME_Available_register (see [802.3ah] 61.1.5.3 and
45.2.3.20).

Adding a PME to the ifStackTable row for a specific PCS, involves
actual connection of the PME to the PCS, which can be done by
modifying Clause 45 PME_Aggregate_register (see [802.3ah] 61.1.5.3
and 45.2.3.21).

Note that PCS port does not have to be operationally 'down' for the
connection to succeed. In fact, a dynamic PME addition (and removal)
MAY be implemented with an available PME being initialized first (by
setting its ifAdminStatus to 'up') and then added to an operationally
'up' PCS port, by modifying a respective ifStackTable (and respective
ifInvStackTable) entry.

It is RECOMMENDED that a removal of the last operationally 'up' PME
from an operationally 'up' PCS would be rejected by the
implementation, as this action would completely drop the link.

3.1.4. EFMCu ports initialization

EFMCu ports being built on top of xDSL technology, require a lengthy
initialization or 'training' process, before any data can pass.
During this initialization both ends of a link (peers) work
cooperatively to achieve required data rate on a particular copper
pair. Sometimes, when the copper line is too long or the noise on
the line is too high, that 'training' process may fail to achieve a
specific target rate with required characteristics.

The ifAdminStatus object from the IF-MIB, controls the desired state
of a PCS with all the PMEs connected to it or of an individual PME
port. Setting this object to 'up' instructs a particular PCS or PME
to start initialization process, which may take tens of seconds for
EFMCu ports, especially if PAF is involved. The ifOperStatus object
shows the operational state of an interface (extended by
ifMauMediaAvailable object from MAU-MIB for PCS and
efmCuPmeOperStatus defined in this MIB the EFM-CU-MIB module for PME
interfaces).

A disconnected PME may be initialized by changing the ifAdminState
from 'down' to 'up'. Changing the ifAdminState to 'up' on the PCS
initializes all PMEs connected to that particular PCS. Note that in
case of PAF some interfaces may fail to initialize while others
succeed. The PCS is considered operationally 'up' if at least one
PME aggregated by its PAF is operationally 'up'. When all PMEs
connected to the PCS are 'down' the PCS SHALL be considered
operationally 'lowerLayerDown'. The PCS SHALL be considered
operationally 'notPresent' if it is not connected to any PME. The
PCS/PME interface SHALL remain operationally 'down' during
initialization.

The efmCuPmeOperStatus defined in this MIB the EFM-CU-MIB module expands PME's
ifOperStatus value of 'down' to 'downReady', 'downNotReady' and
'init' values, indicating various EFMCu PME specific states.

3.1.5. Usage of ifTable

Both PME and PCS interfaces of the EFMCu PHY are managed using
interface specific management objects defined in this MIB the EFM-CU-MIB
module and generic interface objects from the ifTable of IF-MIB, with
all management table entries referenced by the interface index
ifIndex.

The following table summarizes EFMCu specific interpretations for
some of the ifTable objects specified by the mandatory
ifGeneralInformationGroup:

Table 1

3.2. Relation to SHDSL MIB module

G.SHDSL.bis modems, similar to PME(s) comprising a 2BASE-TL port, are
described in HDSL2-SHDSL-LINE-MIB [RFC4319]. Note that not all
attributes of G.SHDSL modems reflected in HDSL2-SHDSL-LINE-MIB have
adequate management objects (Clause 30 attributes and Clause 45
registers) in the EFM standard.

Because of these differences and for the purposes of simplicity,
unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs
and name consistency (e.g. prefixing the 2BASE-TL PME related objects
with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided not to
reference HDSL2-SHDSL-LINE-MIB objects, but define all the relevant
objects in this MIB the EFM-CU-MIB module.

However, if some functionality, not available in this MIB the EFM-CU-MIB
module, is required and supported by the PME, e.g. performance
monitoring, relevant HDSL2-SHDSL-LINE-MIB groups MAY be included and
applied for PMEs of 2BASE-TL subtype.

3.3. Relation to VDSL MIB module

VDSL (DMT) modems, similar to the PME(s) comprising a 10PASS-TS port,
are described in VDSL-LINE-EXT-MCM-MIB [RFC4070]. Note that not all
attributes of VDSL modems reflected in VDSL-LINE-EXT-MCM-MIB have
adequate management objects (Clause 30 attributes and Clause 45
registers) in the EFM standard.

Because of these differences and for the purposes of simplicity,
unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs
and name consistency, it was decided not to reference VDSL-LINE-EXT-
MCM-MIB objects, but define all the relevant objects in this the EFM-CU-
MIB module.

However, if some functionality, not available in this MIB the EFM-CU-MIB
module, is required and supported by the PME, relevant VDSL-LINE-EXT-MCM-MIB VDSL-LINE-EXT-
MCM-MIB groups MAY be included and applied for PMEs of 10PASS-TS
subtype.

3.4. Relation to Ethernet-Like and MAU MIB modules

The implementation of EtherLike-MIB [RFC3635] and MAU-MIB [I-D.ietf-
hubmib-rfc3636bis] is REQUIRED for the EFMCu interfaces.

Two new values of ifMauType (OBJECT-IDENTITIES of dot3MauType) and
corresponding bit definitions of ifMauTypeListBits
(IANAifMauTypeListBits) have been defined in the IANA-MAU-MIB
[I-D.ietf-hubmib-rfc3636bis] for the EFMCu MAUs:

o dot3MauType2BaseTL and b2BaseTL - for 2BASE-TL MAU

o dot3MauType10PassTS and b10PassTS - for 10PASS-TS MAU

Additionally IANA-MAU-MIB defines two new values of
ifMauMediaAvailable, as a textual convention IANAifMauMediaAvailable
- availableReduced and ready, specifically for the EFMCu ports. Due
to the PME aggregation, the EFMCu interpretation of some possible
ifMauMediaAvailable values differs from other MAUs as follows:

o unknown - the EFMCu interface (PCS with connected PMEs) is
initializing

o ready - the interface is down, at least one PME in the aggregation
group (all PMEs connected to the PCS) is ready for handshake

o available - the interface is up, all PMEs in the aggregation group
are up

o notAvailable - the interface is down, all PMEs in the aggregation
group are down, no handshake tones are detected by any PME
o availableReduced - the interface is up, a link fault is detected
at the receive direction by one or more PMEs in the aggregation
group, but at least one PME is up

o pmdLinkFault - a link fault is detected at the receive direction
by all PMEs in the aggregation group

As an EtherLike interface every EFMCu port (an ifEntry representing a
consolidation of LLC, MAC and PCS (sub)layers) SHALL return an ifType
of ethernetCsmacd(6). While most of the MAU characteristics are not
applicable to the EFMCu ports (no auto-negotiation, false carriers or
jabber), they SHALL return an appropriate ifMauType
(dot3MauType2BaseTL or dot3mauType10PassTS) in order to direct the
management software to look in the EFM-CU-MIB module for the desired
information. For example the information on the particular EFMCu
flavor that an EFMCu port is running is available from
efmCuOperSubType, defined in this MIB the EFM-CU-MIB module.

Since EFMCu PMEs are not EtherLike interfaces, they cannot be
instantiated as MAU interface objects.

4. MIB Structure

4.1. EFM Copper MIB Overview

The main management objects defined in this MIB the EFM-CU-MIB module are
split into 2 groups:

o efmCuPort - containing objects for configuration, capabilities,
status and notifications, common to all EFMCu PHYs.

o efmCuPme - containing objects for configuration, capabilities,
status and notifications of EFMCu PMEs.

In addition the ifAvailableStackTable is defined at the same level.

The efmCuPme group in turn contains efmCuPme2B and efmCuPme10P
groups, which define PME Profiles specific to 2BASE-TL and 10PASS-TS
PMEs respectively, as well as PME specific status information.

4.2. Interface stack capability MIB Overview

The IF-CAP-STACK-MIB module contains 2 tables:

o ifCapStackTable - containing objects that define possible
relationships among the sub-layers of an interface with flexible
cross-connect (cross-connect capability).

o ifInvCapStackTable - an inverse of the ifCapstackTable.

4.3. PME Profiles

Since a managed node can have a large number of EFMCu PHYs,
provisioning every parameter on every EFMCu PHY may become
burdensome. Moreover, most PMEs are provisioned identically with the
same set of parameters. To simplify the provisioning process, this
MIB the
EFM-CU-MIB module makes use of configuration profiles, similar to HDSL2-
SHDSL-LINE-MIB
HDSL2-SHDSL-LINE-MIB and VDSL-LINE-EXT-MCM-MIB. A profile is a set
of parameters, used either for configuration or representation of a
PME. The same profile can be shared by multiple PME ports, using the
same configuration.

The PME profiles are defined in efmCuPme2BProfileTable and
efmCu10PProfileTable for 2BASE-TL and 10PASS-TS PMEs respectively.
There are 12 predefined standard profiles for 2BASE-TL and 22
standard profiles for 10PASS-TS, defined in 802.3ah and dedicated for
rapid provisioning of EFMCu PHYs in most scenarios. In addition this
MIB the
EFM-CU-MIB defines two additional predefined profiles for "best-effort" "best-
effort" provisioning of 2BASE-TL PMEs. An ability to define new
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
specific PME via efmCuPmeAdminProfile object. If
efmCuPmeAdminProfile is zero, then efmCuAdminProfile object of the
PCS port, connected to the PME, determines the configuration profile
(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
port, with an ability to change individual PME profiles by setting
efmCuPmeAdminProfile object, which overwrites profile set by
efmCuAdminProfile.

A current operating PME profile is pointed to by efmCuPmeOperProfile
object. Note that this profile entry, can be created automatically,
to reflect achieved parameters in adaptive (not fixed)
initialization.

4.3.

4.4. Mapping of IEEE 802.3ah Managed Objects

This section contains the mapping between relevant managed objects
(attributes) defined in [802.3ah] Clause 30, and managed objects
defined in this document and in associated MIB modules, i.e., the IF-
MIB [RFC2863].

Note that majority of the objects defined in this MIB the EFM-CU-MIB module do
not have direct counterparts in Clause 30 and instead refer to Clause
45 registers.

Table 2

5. Interface Stack Capability MIB Definitions

EFM-CU-MIB

IF-CAP-STACK-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32,
Unsigned32, Counter32, mib-2
FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress
RowStatus
FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP OBJECT-GROUP
FROM SNMPv2-CONF -- RFC 2580
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC 3411
ifIndex, ifSpeed, InterfaceIndex
ifStackGroup2, ifStackHigherLayer, ifStackLowerLayer
FROM IF-MIB -- RFC 2863
;

efmCuMIB

ifCapStackMIB MODULE-IDENTITY
LAST-UPDATED "200606170000Z" "200610120000Z" -- June 17, October 12, 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: Edward Beili
Postal: Actelis Networks Inc.
25 Bazel St., P.O.B. 10173
Petach-Tikva 10173
Israel
Tel: +972-3-924-3491
E-mail: edward.beili@actelis.com"

DESCRIPTION
"The objects in this MIB module are used to manage
the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces
2BASE-TL describe
cross-connect capabilities of stacked (layered) interfaces,
complementing ifStackTable and 10PASS-TS, ifInvStackTable defined in IEEE Std. 802.3ah-2004,
which is now a part of IEEE Std. 802.3-2005.
IF-MIB and IF-INVERTED-STACK-MIB respectively.

[802.3ah] refers to:
IEEE Std 802.3ah-2004: 'IEEE Standard module is part of RFC XXXX; see the RFC
itself for 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 -
Amendment: Media Access Control Parameters, Physical
Layers and Management Parameters for Subscriber Access
Networks', 07 September 2004.

Of particular interest are Clause 61, 'Physical Coding
Sublayer (PCS) and common specifications, type 10PASS-TS and
type 2BASE-TL', Clause 30, 'Management', Clause 45,
'Management Data Input/Output (MDIO) Interface', Annex 62A,
'PMD profiles for 10PASS-TS' and Annex 63A, 'PMD profiles for
2BASE-TL'.

[G.991.2] refers to:
ITU-T Recommendation G.991.2: 'Single-pair High-speed Digital
Subscriber Line (SHDSL) transceivers', December 2003.

[ANFP] refers to:
NICC Document ND1602:2005/08: 'Specification of the Access
Network Frequency Plan (ANFP) applicable to transmission
systems used on the BT Access Network,' August 2005.

Naming Conventions:
Atn - Attenuation
CO - Central Office
CPE - Customer Premises Equipment
EFM - Ethernet in the First Mile
EFMCu - EFM Copper
MDIO - Management Data Input/Output
Mgn - Margin
PAF - PME Aggregation Function
PBO - Power Back-Off
PCS - Physical Coding Sublayer
PMD - Physical Medium Dependent
PME - Physical Medium Entity
PSD - Power Spectral Density
SNR - Signal to Noise Ratio
TCPAM - Trellis Coded Pulse Amplitude Modulation

Copyright (C) The Internet Society (2006). This version
of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices."
REVISION "200606170000Z" -- June 17, 2006
DESCRIPTION "Initial version, published as RFC XXXX."

-- EdNote: Replace XXXX full legal notices."
REVISION "200610120000Z" -- October 12, 2006
DESCRIPTION "Initial version, published as RFC XXXX."

-- EdNote: Replace XXXX with the actual RFC number &
-- remove this note

::= { mib-2 YYY ZZZ }

-- EdNote: Replace YYY ZZZ with a real OID once it is
-- allocated & remove this note.

-- Sections of the module

efmCuObjects

ifCapStackObjects OBJECT IDENTIFIER ::= { efmCuMIB ifCapStackMIB 1 }

efmCuConformance OBJECT IDENTIFIER ::= { efmCuMIB 2 }

-- Groups in the module

efmCuPort OBJECT IDENTIFIER ::= { efmCuObjects 1 }

efmCuPme OBJECT IDENTIFIER ::= { efmCuObjects 2 }

-- Textual Conventions

ProfileIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS
-- ifCapStackTable group
--

ifCapStackTable OBJECT-TYPE
SYNTAX SEQUENCE OF IfCapStackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unique value, greater than zero, for
"This table, modeled after ifStackTable from IF-MIB,
contains information on the possible 'on-top-of'
relationships between the multiple sub-layers of network
interfaces (as opposed to actual relationships described in
ifStackTable). In particular, it contains information on
which sub-layers MAY possibly run 'on top of' which other
sub-layers, as determined by cross-connect capability of the
device, where each PME configuration
profile sub-layer corresponds to a conceptual row
in the managed EFMCu port. It is RECOMMENDED that
values are assigned contiguously starting from 1. The ifTable. For example, when the sub-layer with ifIndex
value x can be connected to run on top of the sub-layer with
ifIndex value y, then this table contains:

ifCapStackStatus.x.y=active

Note that for most stacked interfaces (e.g. 2BASE-TL)
there's always at least one higher-level interface (e.g. PCS
port) for each profile MUST remain constant lower-level interface (e.g. PME) and at
least from one
re-initialization lower-level interface for each higher-level
interface, that is, there is at least a single 'active' row
for any existing value of the entity's network management system
to the next re-initialization."
SYNTAX Unsigned32 (1..255)

ProfileIndexOrZero x or y.

This table is read only as it describes device capability"
REFERENCE
"IF-MIB, ifStackTable"
::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" { ifCapStackObjects 1 }

ifCapStackEntry OBJECT-TYPE
SYNTAX IfCapStackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This textual convention is an extension
"Information on a particular relationship between two
sub-layers, specifying that one sub-layer runs on 'top' of the ProfileIndex
convention. The latter defines a greater than zero value used
other sub-layer. Each sub-layer corresponds to identify a PME profile conceptual
row in the managed EFMCu port. This
extension permits the additional value of zero. The value of
zero is object-specific ifTable (interface index for lower- and MUST therefore be defined as part
of the description of any object which uses this syntax.
Examples of the usage of zero value might include situations
where current operational profile is unknown."
SYNTAX Unsigned32 (0..255)

ProfileIndexList
higher-layer respectively)."
INDEX {
ifStackHigherLayer,
ifStackLowerLayer
}
::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d:" { ifCapStackTable 1 }

IfCapStackEntry ::= SEQUENCE {
ifCapStackStatus RowStatus
}

ifCapStackStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents a list
"The status of up to 6 ProfileIndex's.
The ProfileIndex textual convention defines a greater than
zero value used to identify a PME profile in the managed EFMCu
port. The value of this object is a concatenation of one or
more (up to 6) octets, where each octet contains an 8-bit
ProfileIndex value. 'cross-connect capability' relationship
between two sub-layers. The ProfileIndexList specifies a list of alternative
profiles, any of which following values can be chosen for configuration returned:
active(1) - indicates that the sub-layer interface,
identified by the ifStackLowerLayer MAY
be connected to run 'below' the sub-layer
interface, identified by the
ifStackHigherLayer index.
notInService(2) - the sub-layer interfaces cannot be
connected temporarily due to
unavailability of an
PME."
SYNTAX OCTET STRING (SIZE(1..6))

TruthValueOrUnknown ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention is an extension the interface(s), e.g.
one of the TruthValue
convention. The latter defines interfaces is located on a boolean value with
possible values of true(1) and false(2). This
extension permits
pluggable module which is absent.

Note that lower-layer interface availability per higher-layer,
indicated by the additional value of unknown(0), which 'active', can be returned as a result constrained by
other parameters, for example by the aggregation capacity of GET operation, when an exact
true
a higher-layer interface or false value of by the object cannot be determined."
SYNTAX INTEGER { unknown(0), true(1), false(2) }

-- Port Notifications Group

efmCuPortNotifications OBJECT IDENTIFIER lower-layer interface in
question being already connected to another higher-layer
interface. In order to ensure that a particular sub-layer can
be connected to another sub-layer, all respective objects
(e.g. ifCapStackTable, ifStackTable and efmCuPAFCapacity for
for EFMCu interfaces) SHALL be inspected.

This object is read only, unlike ifStackStatus, as it
describes a cross-connect capability."
::= { efmCuPort 0 }

efmCuLowRateCrossing NOTIFICATION-TYPE
OBJECTS {
-- ifIndex is not needed here since we are under specific PCS
ifSpeed,
efmCuThreshLowRate ifCapStackEntry 1 }

ifInvCapStackTable OBJECT-TYPE
SYNTAX SEQUENCE OF IfInvCapStackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This notification indicates that
"A table containing information on the EFMCu port' data rate
has reached/dropped below or exceeded possible relationships
between the low rate threshold,
specified by efmCuThreshLowRate. multiple sub-layers of network interfaces. This notification MAY be send for the -O subtype ports
(2BaseTL-O/10PassTS-O) while the port is up, on the crossing
event in both directions:
table, modeled after ifInvStackTable from normal (rate
IF-INVERTED-STACK-MIB, is above an inverse of the
threshold) ifCapStackTable
defined in this MIB module.
In particular, this table contains information on which
sub-layers MAY run 'underneath' which other sub-layers, where
each sub-layer corresponds to low (rate equals a conceptual row in the threshold or below it) and
from low ifTable.
For example, when the sub-layer with ifIndex value x MAY be
connected to normal. run underneath the sub-layer with ifIndex value
y, then this table contains:

ifInvCapStackStatus.x.y=active

This notification is not applicable to table contains exactly the -R subtypes.

It is RECOMMENDED that a small debouncing period same number of 2.5 sec,
between rows as the detection of
ifCapStackTable, but the condition and notification, rows appear in a different order.

This table is implemented to prevent simultaneous LinkUp/LinkDown and
efmCuLowRateCrossing notifications to be sent.

The adaptive nature of the EFMCu technology allows the port to
adapt itself to the changes in the copper environment, e.g.
an impulse noise, alien crosstalk or a micro-interruption may
temporarily drop one or more PMEs in the aggregation group,
causing a rate degradation of the aggregated EFMCu link.
The dropped PMEs would then try to re-initialize, possibly at read only as it describes a lower rate than before, adjusting the rate to provide
required target SNR margin.

Generation of this notification is controlled by the
efmCuLowRateCrossingEnable object." cross-connect
capability."
REFERENCE
"IF-INVERTED-STACK-MIB, ifInvStackTable"
::= { efmCuPortNotifications 1 ifCapStackObjects 2 }

-- PCS Port group

efmCuPortConfTable

ifInvCapStackEntry OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPortConfEntry IfInvCapStackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table for Configuration of EFMCu 2BASE-TL/10PASS-TS (PCS)
Ports. Entries in this table MUST be maintained in
"Information on a
persistent manner"
::= { efmCuPort 1 }

efmCuPortConfEntry OBJECT-TYPE
SYNTAX EfmCuPortConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in particular relationship between two sub-
layers, specifying that one sub-layer MAY run underneath the EFMCu Port Configuration table.
other sub-layer. Each entry represents an EFMCu port indexed by the ifIndex.
Note that an EFMCu PCS port runs on top of sub-layer corresponds to a single
or multiple PME port(s), which are also indexed by ifIndex." conceptual
row in the ifTable."
INDEX { ifIndex ifStackLowerLayer, ifStackHigherLayer }
::= { efmCuPortConfTable ifInvCapStackTable 1 }

EfmCuPortConfEntry
IfInvCapStackEntry ::= SEQUENCE {
efmCuPAFAdminState INTEGER,
efmCuPAFDiscoveryCode PhysAddress,
efmCuAdminProfile ProfileIndexList,
efmCuTargetDataRate Unsigned32,
efmCuTargetSnrMgn Unsigned32,
efmCuAdaptiveSpectra TruthValue,
efmCuThreshLowRate Unsigned32,
efmCuLowRateCrossingEnable TruthValue
ifInvCapStackStatus RowStatus
}

efmCuPAFAdminState

ifInvCapStackStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1),
disabled(2)
} RowStatus
MAX-ACCESS read-write read-only
STATUS current
DESCRIPTION
"Administrative (desired) state
"The status of the PAF possible relationship between two
sub-layers.

An instance of this object exists for each instance of the EFMCu port
(PCS).
When 'disabled', PME Aggregation will not be performed by the
PCS. No more than a single PME can be assigned to this PCS in
this case.
When 'enabled', PAF will be performed by the PCS when the link
is Up, even on a single attached PME, if PAF is supported.

PCS ports incapable of supporting PAF SHALL return a value of
'disabled'. Attempts to 'enable' such ports SHALL be ignored.

PAF 'enabled' port with multiple PMEs assigned cannot be
'disabled'. Attempts to 'disable' such port SHALL be rejected,
until at most one PME is left assigned.

Changing PAFAdminState is a traffic disruptive operation
ifCapStackStatus object, and
as such SHALL be done when the link is Down. Attempts to
change this object SHALL be ignored vice versa. For example, if the link is Up or
Initializing.

This object maps to the Clause 30 attribute aPAFAdminState.

If a Clause 45 MDIO Interface to the PCS is present,
variable ifCapStackStatus.H.L exists, then this
object maps to the PAF enable bit in variable
ifInvStackStatus.L.H must also exist, and vice versa. In
addition, the 10P/2B PCS control
register.

This two variables always have the same value.

The ifInvStackStatus object MUST be maintained in is read-only, as it describes
a persistent manner."
REFERENCE
"[802.3ah] 61.2.2, 45.2.3.18.3" cross-connect capability."
::= { efmCuPortConfEntry ifInvCapStackEntry 1 }
efmCuPAFDiscoveryCode OBJECT-TYPE
SYNTAX PhysAddress
MAX-ACCESS read-write

--
-- ifCapStackConformance group
--

ifCapStackConformance OBJECT IDENTIFIER
::= { ifCapStackObjects 3 }

-- Conformance Statements

ifCapStackGroups OBJECT IDENTIFIER ::=
{ ifCapStackConformance 1 }

ifCapStackCompliances OBJECT IDENTIFIER ::=
{ ifCapStackConformance 2 }

-- Units of Conformance

ifCapStackGroup OBJECT-GROUP
OBJECTS {
ifCapStackStatus,
ifInvCapStackStatus
}
STATUS current
DESCRIPTION
"PAF Discovery Code
"A collection of objects providing information on the EFMCu port (PCS).
A unique 6 Byte long code used by the Discovery function, when
PAF is supported.
PCS ports incapable
cross-connect capability of supporting PAF SHALL return a value of
all zeroes. Attempts to change this object SHALL be ignored in
this case.
This object MUST be instantiated multi-layer (stacked) network
interfaces."
::= { ifCapStackGroups 1 }

-- Compliance Statements

ifCapStackCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for the -O subtype PCS before
writing operations SNMP entities, which provide
information on the efmCuPAFRemoteDiscoveryCode
(Set_if_Clear and Clear_if_Same) are performed by PMEs
associated with the PCS.
The value of this object is read-only for -R port subtypes.
The initial value of this object for -R ports after reset
is 0. This value may be changed as a result of writing
operation on efmCuPAFRemoteDiscoveryCode variable of remote
PME of -O subtype, connected to one cross-connect capability of the local PMEs
associated multi-layer
(stacked) network interfaces, with flexible cross-connect
between the PCS.

Discovery MUST be performed when the link is Down.
Attempts to change this object MUST be rejected sub-layers.
Compliance with the error
inconsistentValue if the link following external compliance statements
is Up or Initializing.

The PAF Discovery code maps to the local Discovery code
variable in PAF (note that it does not have a corresponding
Clause 45 register)"
REFERENCE
"[802.3ah] 61.2.2.8.3, 61.2.2.8.4, 45.2.6.6.1"
::= REQUIRED:

MIB Module Compliance Statement
---------- --------------------
IF-MIB ifCompliance3
IF-INVERTED-STACK-MIB ifInvCompliance"

MODULE -- this module
MANDATORY-GROUPS { efmCuPortConfEntry 2
ifCapStackGroup
}

efmCuAdminProfile OBJECT-TYPE

OBJECT ifCapStackStatus
SYNTAX ProfileIndexList
MAX-ACCESS read-write
STATUS current INTEGER { active(1) }
DESCRIPTION
"Desired configuration Profile(s), common
"Support for all PMEs in the
EFMCu port. This object is a list of pointers to entries in
either efmCuPme2BProfileTable or
efmCuPme10PProfileTable, depending on the current
operating SubType of the EFMCu port as indicated by
efmCuPortSide.
The notInService(2) value of this object is a list of up to 6 indices of
Profiles. If this list consists of a single Profile index,
then all PMEs assigned to this EFMCu port SHALL be configured
according to the Profile referenced by that index, unless it
is overwritten by corresponding non-zero efmCuPmeAdminProfile,
which takes precedence over efmCuAdminProfile.
The list, consisting of more than one index, allows each PME
in the port to be configured according to any Profile
specified in the list.
By default this object has a value of 0x01, referencing 1st
entry in efmCuPme2BProfileTable or efmCuPme10PProfileTable.

This object is writable and readable OPTIONAL for the -O subtype
(2BaseTL-O or 10PassTS-O) EFMCu ports. It is unavailable
implementations supporting pluggable interfaces."

OBJECT ifInvCapStackStatus
SYNTAX INTEGER { active(1) }
DESCRIPTION
"Support for the -R subtype (2BaseTL-R or 10PassTS-R) ports.

Note that current operational Profile notInService(2) value is available via
efmCuPmeOperProfile object.

Modification of this object MUST be performed when the link is
Down. Attempts to change this object MUST be rejected, if the
link is Up or Initializing.
Attempts to set this object to a list with a member
value, that is not the value of the index OPTIONAL for an active entry
in the corresponding profile table, MUST be rejected.

This object MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] 30.11.2.1.6"
DEFVAL
implementations supporting pluggable interfaces."

MODULE IF-MIB
MANDATORY-GROUPS { '01'H
ifStackGroup2
}

MODULE IF-INVERTED-STACK-MIB
MANDATORY-GROUPS {
ifInvStackGroup
}
::= { efmCuPortConfEntry 3 ifCapStackCompliances 1 }

efmCuTargetDataRate OBJECT-TYPE
SYNTAX Unsigned32(1..100000|999999)
UNITS "Kbps"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Desired EFMCu port 'net' (as seen across MII) Data Rate in
Kbps, to be achieved during initialization, under spectral
restrictions placed on each PME via efmCuAdminProfile or
efmCuPmeAdminProfile, with the desired SNR Margin specified by
efmCuTargetSnrMgn.
END

6. EFM Copper MIB Definitions

EFM-CU-MIB DEFINITIONS ::= BEGIN

IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32,
Unsigned32, Counter32, mib-2
FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress
FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC 3411
ifIndex, ifSpeed
FROM IF-MIB -- RFC 2863
;

efmCuMIB MODULE-IDENTITY
LAST-UPDATED "200610120000Z" -- October 12, 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 case of PAF, 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: Edward Beili
Postal: Actelis Networks Inc.

25 Bazel St., P.O.B. 10173
Petach-Tikva 10173
Israel
Tel: +972-3-924-3491
E-mail: edward.beili@actelis.com"

DESCRIPTION
"The objects in this object represents a sum of individual PME
data rates, modified MIB module are used to compensate for fragmentation manage
the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces
2BASE-TL and
64/65B framing overhead (e.g. target data rate of 10Mbps
SHALL allow lossless transmission 10PASS-TS, defined in IEEE Std. 802.3ah-2004,
which is now a part of full-duplex 10Mbps
Ethernet frame stream with minimal inter-frame gap). IEEE Std. 802.3-2005.

The value is limited above by 100Mbps as following references are used throughout this is the max
burst rate across MII MIB module:

[802.3ah] refers to:
IEEE Std 802.3ah-2004: 'IEEE Standard for EFMCu ports.

The value Information
technology - Telecommunications and information exchange
between 1 and 100000 indicates that the total data
rate (ifSpeed) of the EFMCu port after initialization SHALL
be equal to the target data rate or less, if the target data
rate cannot be achieved under spectral restrictions specified
by efmCuAdminProfile/efmCuPmeAdminProfile systems - Local and metropolitan area networks -
Specific requirements -
Part 3: Carrier Sense Multiple Access with desired SNR
margin. In case the copper environment allows to achieve
higher total data rate than that specified by the target, the
excess capability SHALL be either converted to additional SNR
margin or reclaimed by minimizing transmit power as controlled
by efmCuAdaptiveSpectra.

The value of 999999 means that the target data rate is not
fixed Collision
Detection (CSMA/CD) Access Method and SHALL be set to the maximum attainable rate during
initialization (Best Effort), under specified spectral
restrictions Physical Layer
Specifications -
Amendment: Media Access Control Parameters, Physical
Layers and with desired SNR Margin.

This object is read-write Management Parameters for the -O subtype EFMCu ports
(2BaseTL-O/10PassTS-O) Subscriber Access
Networks', 07 September 2004.

Of particular interest are Clause 61, 'Physical Coding
Sublayer (PCS) and not available common specifications, type 10PASS-TS and
type 2BASE-TL', Clause 30, 'Management', Clause 45,
'Management Data Input/Output (MDIO) Interface', Annex 62A,
'PMD profiles for the -R subtypes.

Changing 10PASS-TS' and Annex 63A, 'PMD profiles for
2BASE-TL'.

[G.991.2] refers to:
ITU-T Recommendation G.991.2: 'Single-pair High-speed Digital
Subscriber Line (SHDSL) transceivers', December 2003.

[ANFP] refers to:
NICC Document ND1602:2005/08: 'Specification of the Target Data Rate MUST be performed when the
link is Down. Attempts Access
Network Frequency Plan (ANFP) applicable to change this object MUST be rejected
with the error inconsistentValue, if transmission
systems used on the link is Up or
Initializing.

Note that current BT Access Network,' August 2005.

Naming Conventions:
Atn - Attenuation
CO - Central Office
CPE - Customer Premises Equipment
EFM - Ethernet in the First Mile
EFMCu - EFM Copper
MDIO - Management Data Rate Input/Output
Mgn - Margin
PAF - PME Aggregation Function
PBO - Power Back-Off
PCS - Physical Coding Sublayer
PMD - Physical Medium Dependent
PME - Physical Medium Entity
PSD - Power Spectral Density
SNR - Signal to Noise Ratio
TCPAM - Trellis Coded Pulse Amplitude Modulation

Copyright (C) The Internet Society (2006). This version
of this MIB module is part of RFC XXXX; see the EFMCu port RFC
itself for full legal notices."

REVISION "200610120000Z" -- October 12, 2006
DESCRIPTION "Initial version, published as RFC XXXX."

-- EdNote: Replace XXXX with the actual RFC number &
-- remove this note

::= { mib-2 YYY }

-- EdNote: Replace YYY with a real OID once it is represented
by ifSpeed object
-- allocated & remove this note.

-- Sections of IF-MIB.

This object MUST be maintained the module

efmCuObjects OBJECT IDENTIFIER ::= { efmCuMIB 1 }

efmCuConformance OBJECT IDENTIFIER ::= { efmCuMIB 2 }

-- Groups in a persistent manner." the module

efmCuPort OBJECT IDENTIFIER ::= { efmCuPortConfEntry 4 efmCuObjects 1 }

efmCuTargetSnrMgn OBJECT-TYPE
SYNTAX Unsigned32(0..21)
UNITS "dB"
MAX-ACCESS read-write

efmCuPme OBJECT IDENTIFIER ::= { efmCuObjects 2 }

-- Textual Conventions

ProfileIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Desired
"A unique value, greater than zero, for each PME configuration
profile in the managed EFMCu port SNR Margin to be achieved on all PMEs port. It is RECOMMENDED that
values are assigned to the port, during initializiation. (The SNR margin
is the difference between the desired SNR and the actual SNR).

Note that 802.3ah recommends using default Target SNR Margin
of 5dB for 2BASE-TL ports and 6dB contiguously starting from 1. The value
for 10PASS-TS ports in order
to achieve mean Bit Error Rate (BER) of 10^-7 each profile MUST remain constant at least from one
re-initialization of the PMA
service interface.

This object entity's network management system
to the next re-initialization."
SYNTAX Unsigned32 (1..255)

ProfileIndexOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"This textual convention is read-write for an extension of the -O subtype ProfileIndex
convention. The latter defines a greater than zero value used
to identify a PME profile in the managed EFMCu ports
(2BaseTL-O/10PassTS-O) and not available for port. This
extension permits the -R subtypes.

Changing additional value of the Target SNR Margin MUST be performed when the
link zero. The value of
zero is Down. Attempts to change this object object-specific and MUST therefore be rejected
with the error inconsistentValue, if the link is Up or
Initializing.

Note that current SNR Margin defined as part
of the PMEs comprising description of any object which uses this syntax.
Examples of the EFMCu
port usage of zero value might include situations
where current operational profile is represented by efmCuPmeSnrMgn.

This object MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] 61.1.2"
::= { efmCuPortConfEntry 5 }

efmCuAdaptiveSpectra OBJECT-TYPE unknown."
SYNTAX TruthValue
MAX-ACCESS read-write Unsigned32 (0..255)

ProfileIndexList ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d:"
STATUS current
DESCRIPTION
"Indicates how to utilize excess capacity when the copper
environment allows
"Represents a list of up to achieve higher total data rate than that
specified by the efmCuTargetDataRate.

Value of true(1) indicates that the excess capability SHALL be
reclaimed by minimizing transmit power, e.g. using higher
constellations and Power Back-Off, in order to reduce
interference 6 ProfileIndex's.
The ProfileIndex textual convention defines a greater than
zero value used to other copper pairs identify a PME profile in the binder and the
adverse impact to link/system performance.

Value of false(2) indicates that the excess capability SHALL
be converted to additional SNR margin and spread evenly across
all active PMEs assigned to the (PCS) port, to increase link
robustness.

This object is read-write for the -O subtype managed EFMCu ports
(2BaseTL-O/10PassTS-O) and not available for the -R subtypes.

Changing
port. The value of this object MUST be performed when the link is
Down. Attempts to change this object MUST be rejected with the
error inconsistentValue, if the link is Up a concatenation of one or Initializing.

This object MUST be maintained in
more (up to 6) octets, where each octet contains an 8-bit
ProfileIndex value.
The ProfileIndexList specifies a persistent manner."
::= { efmCuPortConfEntry 6 }

efmCuThreshLowRate OBJECT-TYPE list of alternative
profiles, any of which can be chosen for configuration of an
PME."
SYNTAX Unsigned32(1..100000)
UNITS "Kbps"
MAX-ACCESS read-write OCTET STRING (SIZE(1..6))

TruthValueOrUnknown ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This object configures the EFMCu port low rate crossing alarm
threshold. When textual convention is an extension of the current TruthValue
convention. The latter defines a boolean value with
possible values of ifSpeed for this port
reaches/drops below or exceeds this threshold, an
efmCuLowRateCrossing notification MAY be generated if enabled
by efmCuLowRateCrossingEnable. true(1) and false(2). This object is read-write for
extension permits the -O subtype EFMCu ports
(2BaseTL-O/10PassTS-O) and not available for additional value of unknown(0), which
can be returned as a result of GET operation, when an exact
true or false value of the -R subtypes.

This object MUST cannot be maintained in a persistent manner." determined."
SYNTAX INTEGER { unknown(0), true(1), false(2) }

-- Port Notifications Group

efmCuPortNotifications OBJECT IDENTIFIER ::= { efmCuPortConfEntry 7 efmCuPort 0 }
efmCuLowRateCrossing NOTIFICATION-TYPE
OBJECTS {
-- ifIndex is not needed here since we are under specific PCS
ifSpeed,
efmCuThreshLowRate
}

efmCuLowRateCrossingEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates whether efmCuLowRateCrossing notifications should
be generated for this interface.

Value of true(1) indicates that efmCuLowRateCrossing
"This notification is enabled. Value of false(2) indicates that the notification is disabled. EFMCu port' data rate
has reached/dropped below or exceeded the low rate threshold,
specified by efmCuThreshLowRate.

This object is read-write notification MAY be send for the -O subtype EFMCu ports
(2BaseTL-O/10PassTS-O) while the port is up, on the crossing
event in both directions: from normal (rate is above the
threshold) to low (rate equals the threshold or below it) and
from low to normal. This notification is not available for applicable to
the -R subtypes.

This object MUST be maintained in

It is RECOMMENDED that a persistent manner."
::= { efmCuPortConfEntry 8 }

efmCuPortCapabilityTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPortCapabilityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table for Capabilities small debouncing period of EFMCu 2BASE-TL/10PASS-TS (PCS)
Ports. Entries in this table MUST be maintained in a
persistent manner"
::= { efmCuPort 2 }

efmCuPortCapabilityEntry OBJECT-TYPE
SYNTAX EfmCuPortCapabilityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in 2.5 sec,
between the EFMCu Port Capability table.

Each entry represents an EFMCu port indexed by detection of the ifIndex.
Note that condition and notification,
is implemented to prevent simultaneous LinkUp/LinkDown and
efmCuLowRateCrossing notifications to be sent.

The adaptive nature of the EFMCu technology allows the port to
adapt itself to the changes in the copper environment, e.g.
an impulse noise, alien crosstalk or a micro-interruption may
temporarily drop one or more PMEs in the aggregation group,
causing a rate degradation of the aggregated EFMCu link.
The dropped PMEs would then try to re-initialize, possibly at
a lower rate than before, adjusting the rate to provide
required target SNR margin.

Generation of this notification is controlled by the
efmCuLowRateCrossingEnable object."
::= { efmCuPortNotifications 1 }

-- PCS Port group

efmCuPortConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPortConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table for Configuration of EFMCu 2BASE-TL/10PASS-TS (PCS)
Ports. Entries in this table MUST be maintained in a
persistent manner"
::= { efmCuPort 1 }
efmCuPortConfEntry OBJECT-TYPE
SYNTAX EfmCuPortConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the EFMCu Port Configuration table.
Each entry represents an EFMCu port indexed by the ifIndex.
Note that an EFMCu PCS port runs on top of a single
or multiple PME port(s), which are also indexed by ifIndex."
INDEX { ifIndex }
::= { efmCuPortCapabilityTable efmCuPortConfTable 1 }

EfmCuPortCapabilityEntry

EfmCuPortConfEntry ::=
SEQUENCE {
efmCuPAFSupported
efmCuPAFAdminState INTEGER,
efmCuPAFDiscoveryCode PhysAddress,
efmCuAdminProfile ProfileIndexList,
efmCuTargetDataRate Unsigned32,
efmCuTargetSnrMgn Unsigned32,
efmCuAdaptiveSpectra TruthValue,
efmCuPeerPAFSupported TruthValueOrUnknown,
efmCuPAFCapacity
efmCuThreshLowRate Unsigned32,
efmCuPeerPAFCapacity Unsigned32
efmCuLowRateCrossingEnable TruthValue
}

efmCuPAFSupported

efmCuPAFAdminState OBJECT-TYPE
SYNTAX TruthValue INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-only read-write
STATUS current
DESCRIPTION
"PME Aggregation Function (PAF) Capability
"Administrative (desired) state of the PAF of the EFMCu port
(PCS).
This object has a value of true(1) when the PCS can perform
When 'disabled', PME aggregation on Aggregation will not be performed by the available PMEs.
Ports incapable of PAF SHALL return
PCS. No more than a value of false(2).

This object maps to the Clause 30 attribute aPAFSupported.

If a Clause 45 MDIO Interface single PME can be assigned to the this PCS is present,
then in
this object maps to the case.
When 'enabled', PAF available bit in will be performed by the
10P/2B capability register."
REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.4, 45.2.3.17.1"
::= { efmCuPortCapabilityEntry 1 }

efmCuPeerPAFSupported OBJECT-TYPE
SYNTAX TruthValueOrUnknown
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"PME Aggregation Function (PAF) Capability of PCS when the EFMCu port
(PCS) link partner.
This object has
is Up, even on a value of true(1) when the remote single attached PME, if PAF is supported.

PCS can
perform PME aggregation on its available PMEs.
Ports whose peers are ports incapable of PAF, supporting PAF SHALL return a value of false(2).
Ports whose peers
'disabled'. Attempts to 'enable' such ports SHALL be ignored.

PAF 'enabled' port with multiple PMEs assigned cannot be reached because of
'disabled'. Attempts to 'disable' such port SHALL be rejected,
until at most one PME is left assigned.

Changing PAFAdminState is a traffic disruptive operation and
as such SHALL be done when the link
state, is Down. Attempts to
change this object SHALL return a value be ignored if unknown(0). the link is Up or
Initializing.

This object maps to the Clause 30 attribute
aRemotePAFSupported. aPAFAdminState.

If a Clause 45 MDIO Interface to the PCS is present, then this
object maps to the Remote PAF supported enable bit in the 10P/2B capability register." PCS control
register.

This object MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.9, 45.2.3.17.2" 45.2.3.18.3"
::= { efmCuPortCapabilityEntry 2 efmCuPortConfEntry 1 }

efmCuPAFCapacity

efmCuPAFDiscoveryCode OBJECT-TYPE
SYNTAX Unsigned32 (1..32) PhysAddress
MAX-ACCESS read-only read-write
STATUS current
DESCRIPTION
"Number
"PAF Discovery Code of PMEs that can be aggregated by the local PAF.
The number of PMEs currently assigned to a particular EFMCu port (efmCuNumPMEs) is never greater than
efmCuPAFCapacity.

This object maps to (PCS).
A unique 6 Byte long code used by the Clause 30 attribute
aLocalPAFCapacity."
REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.6"
::= { efmCuPortCapabilityEntry 3 }

efmCuPeerPAFCapacity OBJECT-TYPE
SYNTAX Unsigned32 (0|1..32)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number Discovery function, when
PAF is supported.
PCS ports incapable of PMEs that can supporting PAF SHALL return a value of
all zeroes. Attempts to change this object SHALL be aggregated ignored in
this case.
This object MUST be instantiated for the -O subtype PCS before
writing operations on the efmCuPAFRemoteDiscoveryCode
(Set_if_Clear and Clear_if_Same) are performed by PMEs
associated with the PAF PCS.
The value of the peer
Phy (PCS port).
Value this object is read-only for -R port subtypes.
The initial value of 0 this object for -R ports after reset
is returned 0. This value may be changed as a result of writing
operation on efmCuPAFRemoteDiscoveryCode variable of remote
PME of -O subtype, connected to one of the local PMEs
associated with the PCS.

Discovery MUST be performed when peer PAF Capacity the link is unknown
(peer cannot be reached).

This Down.
Attempts to change this object MUST be rejected with the error
inconsistentValue if the link is Up or Initializing.

The PAF Discovery code maps to the local Discovery code
variable in PAF (note that it does not have a corresponding
Clause 30 attribute
aRemotePAFCapacity." 45 register)"
REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.10" 61.2.2.8.3, 61.2.2.8.4, 45.2.6.6.1"
::= { efmCuPortCapabilityEntry 4 efmCuPortConfEntry 2 }

efmCuPortStatusTable
efmCuAdminProfile OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPortStatusEntry ProfileIndexList
MAX-ACCESS not-accessible read-write
STATUS current
DESCRIPTION
"This table provides overall status information of EFMCu
2BASE-TL/10PASS-TS ports, complementing the generic status
information from the ifTable of IF-MIB and ifMauTable of
MAU-MIB. Additional status information about connected
"Desired configuration Profile(s), common for all PMEs in the
EFMCu port. This object is available from efmCuPmeStatusTable.

This table contains live data from a list of pointers to entries in
either efmCuPme2BProfileTable or
efmCuPme10PProfileTable, depending on the equipment. As such,
it is NOT persistent."
::= { efmCuPort 3 }

efmCuPortStatusEntry OBJECT-TYPE
SYNTAX EfmCuPortStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in
operating SubType of the EFMCu Port Status table.
Each entry represents an EFMCu port indexed as indicated by the ifIndex.
Note that an EFMCu PCS port runs on top
efmCuPortSide.
The value of a single
or multiple PME port(s), which are also indexed by ifIndex."
INDEX { ifIndex }
::= { efmCuPortStatusTable 1 }

EfmCuPortStatusEntry ::=
SEQUENCE {
efmCuFltStatus BITS,
efmCuPortSide INTEGER,
efmCuNumPMEs Unsigned32,
efmCuPAFInErrors Counter32,
efmCuPAFInSmallFragments Counter32,
efmCuPAFInLargeFragments Counter32,
efmCuPAFInBadFragments Counter32,
efmCuPAFInLostFragments Counter32,
efmCuPAFInLostStarts Counter32,
efmCuPAFInLostEnds Counter32,
efmCuPAFInOverflows Counter32
}

efmCuFltStatus OBJECT-TYPE
SYNTAX BITS {
noPeer(0),
peerPowerLoss(1),
pmeSubTypeMismatch(2),
lowRate(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"EFMCu (PCS) port Fault Status. This this object is a bitmap list of possible
conditions. The various bit positions are:
noPeer - peer PHY cannot be reached (e.g.
no PMEs attached, all PMEs are Down
etc.) More info is available in
efmCuPmeFltStatus.
peerPowerLoss - peer PHY has indicated impending unit
failure due up to loss 6 indices of local power
('Dying Gasp').
pmeSubTypeMismatch - local
Profiles. If this list consists of a single Profile index,
then all PMEs in assigned to this EFMCu port SHALL be configured
according to the aggregation group
are not Profile referenced by that index, unless it
is overwritten by corresponding non-zero efmCuPmeAdminProfile,
which takes precedence over efmCuAdminProfile.
The list, consisting of the same sub-type, e.g.
some PMEs more than one index, allows each PME
in the local device are -O
while others are -R subtype.
lowRate - ifSpeed of the port reached to be configured according to any Profile
specified in the list.
By default this object has a value of 0x01, referencing 1st
entry in efmCuPme2BProfileTable or dropped
below efmCuThreshLowRate efmCuPme10PProfileTable.

This object is intended to supplement ifOperStatus object
in IF-MIB writable and ifMauMediaAvailable in MAU-MIB.

Additional information is available via efmCuPmeFltStatus
object readable for each PME in the aggregation group (single PME if
PAF -O subtype
(2BaseTL-O or 10PassTS-O) EFMCu ports. It is disabled)."
REFERENCE
"IF-MIB, ifOperStatus; MAU-MIB, ifMauMediaAvailable;
efmCuPmeFltStatus"
::= { efmCuPortStatusEntry 1 }

efmCuPortSide OBJECT-TYPE
SYNTAX INTEGER {
subscriber(1),
office(2),
unknown(3)
}
MAX-ACCESS read-only
STATUS unavailable for
the -R subtype (2BaseTL-R or 10PassTS-R) ports.

Note that current
DESCRIPTION
"EFM port mode of operation (subtype).
The operational Profile value is available via
efmCuPmeOperProfile object.

Modification of 'subscriber' indicates this object MUST be performed when the port link is designated as
'-R' subtype (all PMEs assigned
Down. Attempts to change this port are of subtype
'-R').
The value of the 'office' indicates that object MUST be rejected, if the port
link is
designated as '-O' subtype (all PMEs assigned Up or Initializing.
Attempts to set this port are
of subtype '-O').
The value of 'unknown' indicates that the port has no assigned
PMEs yet or object to a list with a member
value, that the assigned PMEs are is not the value of the same side
(subTypePMEMismatch). index for an active entry
in the corresponding profile table, MUST be rejected.

This object partially maps to the Clause 30 attribute
aPhyEnd" MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] 61.1, 30.11.1.1.2"
::= 30.11.2.1.6"
DEFVAL { efmCuPortStatusEntry 2 '01'H }

efmCuNumPMEs
::= { efmCuPortConfEntry 3 }

efmCuTargetDataRate OBJECT-TYPE
SYNTAX Unsigned32 (0..32) Unsigned32(1..100000|999999)
UNITS "Kbps"
MAX-ACCESS read-only read-write
STATUS current
DESCRIPTION
"Number of PMEs that is currently aggregated by the local PAF
(assigned to the
"Desired EFMCu port using ifStackTable).
This number is never greater than efmCuPAFCapacity.

This object SHALL 'net' (as seen across MII) Data Rate in
Kbps, to be automatically incremented achieved during initialization, under spectral
restrictions placed on each PME via efmCuAdminProfile or decremented
when
efmCuPmeAdminProfile, with the desired SNR Margin specified by
efmCuTargetSnrMgn.
In case of PAF, this object represents a sum of individual PME
data rates, modified to compensate for fragmentation and
64/65B framing overhead (e.g. target data rate of 10Mbps
SHALL allow lossless transmission of full-duplex 10Mbps
Ethernet frame stream with minimal inter-frame gap).

The value is limited above by 100Mbps as this is added or deleted to/from the max
burst rate across MII for EFMCu port using
ifStackTable."
REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.6"
::= { efmCuPortStatusEntry 3 }

efmCuPAFInErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A number of fragments ports.

The value between 1 and 100000 indicates that have been received across the
gamma interface with RxErr asserted and discarded.
This read-only counter is inactive (not incremented) when total data
rate (ifSpeed) of the
PAF is unsupported EFMCu port after initialization SHALL
be equal to the target data rate or disabled. Upon disabling less, if the PAF, target data
rate cannot be achieved under spectral restrictions specified
by efmCuAdminProfile/efmCuPmeAdminProfile and with desired SNR
margin. In case the
counter retains its previous value.

If a Clause 45 MDIO Interface copper environment allows to achieve
higher total data rate than that specified by the PCS is present, then
this object maps to target, the 10P/2B PAF RX error register."
REFERENCE
"[802.3ah] 45.2.3.21"
::= { efmCuPortStatusEntry 4 }

efmCuPAFInSmallFragments OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A number
excess capability SHALL be either converted to additional SNR
margin or reclaimed by minimizing transmit power as controlled
by efmCuAdaptiveSpectra.

The value of fragments smaller than minFragmentSize
(64 Bytes), which have been received across 999999 means that the gamma
interface target data rate is not
fixed and discarded. SHALL be set to the maximum attainable rate during
initialization (Best Effort), under specified spectral
restrictions and with desired SNR Margin.

This read-only counter object is inactive when read-write for the PAF is
unsupported or disabled. Upon disabling -O subtype EFMCu ports
(2BaseTL-O/10PassTS-O) and not available for the PAF, -R subtypes.

Changing of the counter
retains its previous value.

If a Clause 45 MDIO Interface to Target Data Rate MUST be performed when the PCS
link is present, then Down. Attempts to change this object maps to MUST be rejected
with the 10P/2B PAF small fragments
register."
REFERENCE
"[802.3ah] 45.2.3.22" error inconsistentValue, if the link is Up or
Initializing.

Note that current Data Rate of the EFMCu port is represented
by ifSpeed object of IF-MIB.

This object MUST be maintained in a persistent manner."
::= { efmCuPortStatusEntry 5 efmCuPortConfEntry 4 }

efmCuPAFInLargeFragments

efmCuTargetSnrMgn OBJECT-TYPE
SYNTAX Counter32 Unsigned32(0..21)
UNITS "dB"
MAX-ACCESS read-only read-write
STATUS current
DESCRIPTION
"A number of fragments larger than maxFragmentSize
(512 Bytes), which have been received across
"Desired EFMCu port SNR Margin to be achieved on all PMEs
assigned to the gamma
interface and discarded.
This read-only counter port, during initializiation. (The SNR margin
is inactive when the PAF is
unsupported or disabled. Upon disabling difference between the PAF, desired SNR and the counter
retains its previous value.

If a Clause 45 MDIO Interface actual SNR).

Note that 802.3ah recommends using default Target SNR Margin
of 5dB for 2BASE-TL ports and 6dB for 10PASS-TS ports in order
to achieve mean Bit Error Rate (BER) of 10^-7 at the PCS is present, then
this PMA
service interface.

This object maps to is read-write for the 10P/2B PAF large fragments
register."
REFERENCE
"[802.3ah] 45.2.3.23"
::= { efmCuPortStatusEntry 6 }

efmCuPAFInBadFragments OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A number of fragments which do -O subtype EFMCu ports
(2BaseTL-O/10PassTS-O) and not fit into available for the sequence
expected by -R subtypes.

Changing of the frame assembly function, that have been
received across Target SNR Margin MUST be performed when the gamma interface and discarded (the
frame buffer
link is flushed Down. Attempts to change this object MUST be rejected
with the next valid frame start).
This read-only counter is inactive when error inconsistentValue, if the PAF link is
unsupported Up or disabled. Upon disabling the PAF,
Initializing.

Note that current SNR Margin of the counter
retains its previous value.

If a Clause 45 MDIO Interface to PMEs comprising the PCS EFMCu
port is present, then
this represented by efmCuPmeSnrMgn.

This object maps to the 10P/2B PAF bad fragments
register." MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] 45.2.3.25" 61.1.2"
::= { efmCuPortStatusEntry 7 efmCuPortConfEntry 5 }

efmCuPAFInLostFragments

efmCuAdaptiveSpectra OBJECT-TYPE
SYNTAX Counter32 TruthValue
MAX-ACCESS read-only read-write
STATUS current
DESCRIPTION
"A number of gaps in the sequence of fragments, which have
been received across the gamma interface (the frame buffer is
flushed
"Indicates how to utilize excess capacity when the next valid frame start, when fragment/fragments
expected copper
environment allows to achieve higher total data rate than that
specified by the frame assembly function is/are not received).
This read-only counter is inactive when efmCuTargetDataRate.

Value of true(1) indicates that the PAF is
unsupported or disabled. Upon disabling excess capability SHALL be
reclaimed by minimizing transmit power, e.g. using higher
constellations and Power Back-Off, in order to reduce
interference to other copper pairs in the PAF, binder and the counter
retains its previous value.

If a Clause 45 MDIO Interface
adverse impact to link/system performance.

Value of false(2) indicates that the PCS excess capability SHALL
be converted to additional SNR margin and spread evenly across
all active PMEs assigned to the (PCS) port, to increase link
robustness.

This object is present, then read-write for the -O subtype EFMCu ports
(2BaseTL-O/10PassTS-O) and not available for the -R subtypes.

Changing of this object maps MUST be performed when the link is
Down. Attempts to change this object MUST be rejected with the 10P/2B PAF lost fragment
register."
REFERENCE
"[802.3ah] 45.2.3.26"
error inconsistentValue, if the link is Up or Initializing.

This object MUST be maintained in a persistent manner."
::= { efmCuPortStatusEntry 8 efmCuPortConfEntry 6 }

efmCuPAFInLostStarts

efmCuThreshLowRate OBJECT-TYPE
SYNTAX Counter32 Unsigned32(1..100000)
UNITS "Kbps"
MAX-ACCESS read-only read-write
STATUS current
DESCRIPTION
"A number
"This object configures the EFMCu port low rate crossing alarm
threshold. When the current value of missing StartOfPacket indicators expected ifSpeed for this port
reaches/drops below or exceeds this threshold, an
efmCuLowRateCrossing notification MAY be generated if enabled
by the
frame assembly function. efmCuLowRateCrossingEnable.

This read-only counter is inactive when the PAF object is
unsupported or disabled. Upon disabling the PAF, read-write for the counter
retains its previous value.

If a Clause 45 MDIO Interface to -O subtype EFMCu ports
(2BaseTL-O/10PassTS-O) and not available for the PCS is present, then
this -R subtypes.

This object maps to the 10P/2B PAF lost start of fragment
register."
REFERENCE
"[802.3ah] 45.2.3.27" MUST be maintained in a persistent manner."
::= { efmCuPortStatusEntry 9 efmCuPortConfEntry 7 }

efmCuPAFInLostEnds

efmCuLowRateCrossingEnable OBJECT-TYPE
SYNTAX Counter32 TruthValue
MAX-ACCESS read-only read-write
STATUS current
DESCRIPTION
"A number
"Indicates whether efmCuLowRateCrossing notifications should
be generated for this interface.

Value of missing EndOfPacket indicators expected by the
frame assembly function.
This read-only counter true(1) indicates that efmCuLowRateCrossing
notification is inactive when enabled. Value of false(2) indicates that
the PAF notification is
unsupported or disabled. Upon disabling the PAF,

This object is read-write for the counter
retains its previous value.

If a Clause 45 MDIO Interface to -O subtype EFMCu ports
(2BaseTL-O/10PassTS-O) and not available for the PCS is present, then
this -R subtypes.

This object maps to the 10P/2B PAF lost start of fragment
register."
REFERENCE
"[802.3ah] 45.2.3.28" MUST be maintained in a persistent manner."
::= { efmCuPortStatusEntry 10 efmCuPortConfEntry 8 }

efmCuPAFInOverflows

efmCuPortCapabilityTable OBJECT-TYPE
SYNTAX Counter32 SEQUENCE OF EfmCuPortCapabilityEntry
MAX-ACCESS read-only not-accessible
STATUS current
DESCRIPTION
"A number
"Table for Capabilities of fragments, received across the gamma interface
and discarded, which would have caused the frame assembly
buffer to overflow.
This read-only counter is inactive when the PAF is
unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value.

If a Clause 45 MDIO Interface to the PCS is present, then EFMCu 2BASE-TL/10PASS-TS (PCS)
Ports. Entries in this object maps to the 10P/2B PAF overflow register."
REFERENCE
"[802.3ah] 45.2.3.24" table MUST be maintained in a
persistent manner"
::= { efmCuPortStatusEntry 11 efmCuPort 2 }

efmCuPortCapabilityEntry OBJECT-TYPE
SYNTAX EfmCuPortCapabilityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the EFMCu Port Capability table.
Each entry represents an EFMCu port indexed by the ifIndex.
Note that an EFMCu PCS port runs on top of a single
or multiple PME Notifications Group

efmCuPmeNotifications OBJECT IDENTIFIER port(s), which are also indexed by ifIndex."
INDEX { ifIndex }
::= { efmCuPme 0 efmCuPortCapabilityTable 1 }

efmCuPmeLineAtnCrossing NOTIFICATION-TYPE
OBJECTS

EfmCuPortCapabilityEntry ::=
SEQUENCE {
efmCuPmeLineAtn,
efmCuPmeThreshLineAtn
efmCuPAFSupported TruthValue,
efmCuPeerPAFSupported TruthValueOrUnknown,
efmCuPAFCapacity Unsigned32,
efmCuPeerPAFCapacity Unsigned32
}

efmCuPAFSupported OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This notification indicates that the loop attenuation
threshold (as per
"PME Aggregation Function (PAF) Capability of the efmCuPmeThreshLineAtn
value) EFMCu port
(PCS).
This object has been reached/exceeded for a value of true(1) when the 2BASE-TL/10PASS-TS
PME. This notification MAY be send PCS can perform
PME aggregation on the crossing event in
both directions: from normal to exceeded and from exceeded
to normal.

It is RECOMMENDED that available PMEs.
Ports incapable of PAF SHALL return a small debouncing period value of 2.5 sec,
between false(2).

This object maps to the detection of Clause 30 attribute aPAFSupported.

If a Clause 45 MDIO Interface to the condition and notification, PCS is implemented to prevent intermittent notifications to be
sent.

Generation of present,
then this notification is controlled by object maps to the
efmCuPmeLineAtnCrossingEnable object." PAF available bit in the
10P/2B capability register."
REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.4, 45.2.3.17.1"
::= { efmCuPmeNotifications efmCuPortCapabilityEntry 1 }

efmCuPmeSnrMgnCrossing NOTIFICATION-TYPE
OBJECTS {
efmCuPmeSnrMgn,
efmCuPmeThreshSnrMgn
}
efmCuPeerPAFSupported OBJECT-TYPE
SYNTAX TruthValueOrUnknown
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This notification indicates that the SNR margin threshold
(as per
"PME Aggregation Function (PAF) Capability of the efmCuPmeThreshSnrMgn value) EFMCu port
(PCS) link partner.
This object has been
reached/exceeded for a value of true(1) when the 2BASE-TL/10PASS-TS PME.
This notification MAY be send remote PCS can
perform PME aggregation on the crossing event in
both directions: from normal to exceeded and from exceeded
to normal.

It is RECOMMENDED that its available PMEs.
Ports whose peers are incapable of PAF, SHALL return a small debouncing period value
of 2.5 sec,
between the detection false(2).
Ports whose peers cannot be reached because of the condition and notification,
is implemented link
state, SHALL return a value if unknown(0).

This object maps to prevent intermittent notifications the Clause 30 attribute
aRemotePAFSupported.

If a Clause 45 MDIO Interface to be
sent.

Generation of this notification the PCS is controlled by present, then
this object maps to the
efmCuPmeSnrMgnCrossingEnable object." Remote PAF supported bit in the
10P/2B capability register."
REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.9, 45.2.3.17.2"
::= { efmCuPmeNotifications efmCuPortCapabilityEntry 2 }

efmCuPmeDeviceFault NOTIFICATION-TYPE
OBJECTS {
efmCuPmeFltStatus
}

efmCuPAFCapacity OBJECT-TYPE
SYNTAX Unsigned32 (1..32)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This notification indicates
"Number of PMEs that a fault in the PME has been
detected can be aggregated by a vendor specific diagnostic or a self-test.

Generation the local PAF.
The number of this notification PMEs currently assigned to a particular
EFMCu port (efmCuNumPMEs) is controlled by never greater than
efmCuPAFCapacity.

This object maps to the
efmCuPmeDeviceFaultEnable object." Clause 30 attribute
aLocalPAFCapacity."
REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.6"
::= { efmCuPmeNotifications efmCuPortCapabilityEntry 3 }

efmCuPmeConfigInitFailure NOTIFICATION-TYPE
OBJECTS {
efmCuPmeFltStatus,
efmCuAdminProfile,
efmCuPmeAdminProfile
}

efmCuPeerPAFCapacity OBJECT-TYPE
SYNTAX Unsigned32 (0|1..32)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This notification indicates that PME initialization has
failed, due to inability
"Number of PMEs that can be aggregated by the PME link to achieve requested
configuration profile.

Generation PAF of this notification is controlled by the
efmCuPmeConfigInitFailEnable object."
::= { efmCuPmeNotifications 4 }

efmCuPmeProtocolInitFailure NOTIFICATION-TYPE
OBJECTS {
efmCuPmeFltStatus,
efmCuPmeOperSubType
}
STATUS current
DESCRIPTION
"This notification indicates that peer PME was using
incompatible protocol during initialization.

Generation
Phy (PCS port).
Value of this notification 0 is controlled by returned when peer PAF Capacity is unknown
(peer cannot be reached).

This object maps to the
efmCuPmeProtocolInitFailEnable object." Clause 30 attribute
aRemotePAFCapacity."
REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.10"
::= { efmCuPmeNotifications 5 efmCuPortCapabilityEntry 4 }

-- The PME group

efmCuPmeConfTable

efmCuPortStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPmeConfEntry EfmCuPortStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table for Configuration
"This table provides overall status information of common aspects for EFMCu
2BASE-TL/10PASS-TS PME ports (modems). Configuration ports, complementing the generic status
information from the ifTable of
aspects specific to 2BASE-TL or 10PASS-TS PME types is
represented in efmCuPme2BConfTable IF-MIB and efmCuPme10PConfTable
respectively.

Entries in this ifMauTable of
MAU-MIB. Additional status information about connected PMEs
is available from efmCuPmeStatusTable.

This table MUST be maintained in a persistent
manner." contains live data from the equipment. As such,
it is NOT persistent."
::= { efmCuPme 1 efmCuPort 3 }

efmCuPmeConfEntry

efmCuPortStatusEntry OBJECT-TYPE
SYNTAX EfmCuPmeConfEntry EfmCuPortStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the EFMCu PME Configuration Port Status table.
Each entry represents common aspects of an EFMCu PME port indexed by the ifIndex.
Note that an EFMCu PME PCS port can be
stacked below runs on top of a single PCS port,
or multiple PME port(s), which are also indexed by ifIndex,
possibly together with other PME ports if PAF is enabled." ifIndex."
INDEX { ifIndex }
::= { efmCuPmeConfTable efmCuPortStatusTable 1 }

EfmCuPmeConfEntry

EfmCuPortStatusEntry ::=
SEQUENCE {
efmCuPmeAdminSubType
efmCuFltStatus BITS,
efmCuPortSide INTEGER,
efmCuPmeAdminProfile ProfileIndexOrZero,
efmCuPAFRemoteDiscoveryCode PhysAddress,
efmCuPmeThreshLineAtn Integer32,
efmCuPmeThreshSnrMgn Integer32,
efmCuPmeLineAtnCrossingEnable TruthValue,
efmCuPmeSnrMgnCrossingEnable TruthValue,
efmCuPmeDeviceFaultEnable TruthValue,
efmCuPmeConfigInitFailEnable TruthValue,
efmCuPmeProtocolInitFailEnable TruthValue
efmCuNumPMEs Unsigned32,
efmCuPAFInErrors Counter32,
efmCuPAFInSmallFragments Counter32,
efmCuPAFInLargeFragments Counter32,
efmCuPAFInBadFragments Counter32,
efmCuPAFInLostFragments Counter32,
efmCuPAFInLostStarts Counter32,
efmCuPAFInLostEnds Counter32,
efmCuPAFInOverflows Counter32
}

efmCuPmeAdminSubType

efmCuFltStatus OBJECT-TYPE
SYNTAX INTEGER BITS {
ieee2BaseTLO(1),
ieee2BaseTLR(2),
ieee10PassTSO(3),
ieee10PassTSR(4),
ieee2BaseTLor10PassTSR(5),
ieee2BaseTLor10PassTSO(6),
ieee10PassTSor2BaseTLO(7)
noPeer(0),
peerPowerLoss(1),
pmeSubTypeMismatch(2),
lowRate(3)
}
MAX-ACCESS read-write read-only
STATUS current
DESCRIPTION
"Administrative (desired) sub-type
"EFMCu (PCS) port Fault Status. This is a bitmap of the PME.
Possible values possible
conditions. The various bit positions are:
ieee2BaseTLO - PME SHALL operate as 2BaseTL-O
ieee2BaseTLR - PME SHALL operate as 2BaseTL-R
ieee10PassTSO - PME SHALL operate as 10PassTS-O
ieee10PassTSR - PME SHALL operate as 10PassTS-R
ieee2BaseTLor10PassTSR - PME SHALL operate as 2BaseTL-R or
10PassTS-R. Actual value will be
set by -O link partner during
initialization (handshake).
ieee2BaseTLor10PassTSO
noPeer - PME SHALL operate as 2BaseTL-O
(preferred) or 10PassTS-O. Actual
value will peer PHY cannot be set during
initialization depending on -R
link partner capability (i.e. if
-R reached (e.g.
no PMEs attached, all PMEs are Down
etc.) More info is incapable available in
efmCuPmeFltStatus.
peerPowerLoss - peer PHY has indicated impending unit
failure due to loss of the preferred
2BaseTL mode, 10PassTS will be
used).

ieee10PassTSor2BaseTLO local power
('Dying Gasp').
pmeSubTypeMismatch - PME SHALL operate as 10PassTS-O
(preferred) or 2BaseTL-O. Actual
value will be set during
initialization depending on -R
link partner capability (i.e. if local PMEs in the aggregation group
are not of the same sub-type, e.g.
some PMEs in the local device are -O
while others are -R is incapable subtype.
lowRate - ifSpeed of the preferred
10PassTS mode, 2BaseTL will be
used).

Changing efmCuPmeAdminSubType port reached or dropped
below efmCuThreshLowRate

This object is a traffic disruptive
operation intended to supplement ifOperStatus object
in IF-MIB and as such SHALL be done when the link ifMauMediaAvailable in MAU-MIB.

Additional information is Down.
Attempts to change this available via efmCuPmeFltStatus
object SHALL be ignored if for each PME in the link
is Up or Initializing.
Attempts to change this object to an unsupported subtype
(see efmCuPmeSubTypesSupported) SHALL be rejected.

The current operational sub type is indicated by
efmCuPmeOperSubType variable.

If a Clause 45 MDIO Interface to the PMA/PMD aggregation group (single PME if
PAF is present, then
this object combines values of the Port sub-type select bits
and the PMA/PMD type selection bits in the 10P/2B PMA/PMD
control register" disabled)."
REFERENCE
"[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7"
"IF-MIB, ifOperStatus; MAU-MIB, ifMauMediaAvailable;
efmCuPmeFltStatus"
::= { efmCuPmeConfEntry efmCuPortStatusEntry 1 }

efmCuPmeAdminProfile

efmCuPortSide OBJECT-TYPE
SYNTAX ProfileIndexOrZero INTEGER {
subscriber(1),
office(2),
unknown(3)
}
MAX-ACCESS read-write read-only
STATUS current
DESCRIPTION
"Desired PME configuration Profile. This object is a pointer
to an entry in either efmCuPme2BProfileTable or
efmCuPme10PProfileTable, depending on the current operating
SubType
"EFM port mode of the PME. operation (subtype).
The value of this object is 'subscriber' indicates the index port is designated as
'-R' subtype (all PMEs assigned to this port are of
the referenced profile. subtype
'-R').
The value of zero (default) the 'office' indicates that the PME port is
configured via efmCuAdminProfile object for the PCS port,
designated as '-O' subtype (all PMEs assigned to which this PME is assigned. That is, port are
of subtype '-O').
The value of 'unknown' indicates that the profile referenced
by efmCuPmeAdminProfile takes precedence over port has no assigned
PMEs yet or that the profile(s)
referenced by efmCuAdminProfile. assigned PMEs are not of the same side
(subTypePMEMismatch).

This object is writable and readable for partially maps to the CO subtype Clause 30 attribute
aPhyEnd"
REFERENCE
"[802.3ah] 61.1, 30.11.1.1.2"
::= { efmCuPortStatusEntry 2 }

efmCuNumPMEs OBJECT-TYPE
SYNTAX Unsigned32 (0..32)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of PMEs
(2BaseTL-O or 10PassTS-O). It that is unavailable for currently aggregated by the CPE
subtype (2BaseTL-R or 10PassTS-R).

Note that current operational Profile value is available via
efmCuPmeOperProfile object.

Modification of this object MUST be performed when local PAF
(assigned to the link EFMCu port using ifStackTable).
This number is
Down. Attempts to change this never greater than efmCuPAFCapacity.

This object MUST SHALL be rejected, if the
link is Up automatically incremented or Initializing.
Attempts to set this object to decremented
when a value that PME is not the value
of the index for an active entry in added or deleted to/from the corresponding profile
table, MUST be rejected." EFMCu port using
ifStackTable."
REFERENCE
"[802.3ah] 30.11.2.1.6"
DEFVAL { 0 } 61.2.2, 30.11.1.1.6"
::= { efmCuPmeConfEntry 2 efmCuPortStatusEntry 3 }

efmCuPAFRemoteDiscoveryCode

efmCuPAFInErrors OBJECT-TYPE
SYNTAX PhysAddress Counter32
MAX-ACCESS read-write read-only
STATUS current
DESCRIPTION
"PAF Remote Discovery Code
"A number of fragments that have been received across the PME port at CO.
A 6 Byte long Discovery Code of
gamma interface with RxErr asserted and discarded.
This read-only counter is inactive (not incremented) when the peer PCS connected via
PAF is unsupported or disabled. Upon disabling the PME.
Reading this object results in a Discovery Get operation.
Writing PAF, the
counter retains its previous value.

If a zero Clause 45 MDIO Interface to the PCS is present, then
this object results maps to the 10P/2B PAF RX error register.

Discontinuities in a Discovery
Clear_if_Same operation (the the value of efmCuPAFDiscoveryCode this counter can occur at the peer PCS SHALL be the same as efmCuPAFDiscoveryCode
re-initialization of the local PCS associated with the PME for management system, and at other times
as indicated by the operation to
succeed).
Writing a non-zero value to this object results in a
Discovery Set_if_Clear operation.
This object does not exist of ifCounterDiscontinuityTime,
defined in CPE port subtypes. A zero length
octet string SHALL be returned for CPE port subtypes IF-MIB."
REFERENCE
"[802.3ah] 45.2.3.21"
::= { efmCuPortStatusEntry 4 }

efmCuPAFInSmallFragments OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A number of fragments smaller than minFragmentSize
(64 Bytes), which have been received across the gamma
interface and also
when PAF aggregation discarded.
This read-only counter is not enabled.

Discovery MUST be performed inactive when the link PAF is Down.
Attempts to change this object MUST be rejected with
unsupported or disabled. Upon disabling the error
inconsistentValue, if PAF, the link is Up or Initializing. counter
retains its previous value.

If a Clause 45 MDIO Interface to the PMA/PMD PCS is present, then
this object is a function of maps to the 10P/2B aggregation discovery
control register, Discovery operation result bits PAF small fragments
register.

Discontinuities in 10P/2B
aggregation and discovery status register the value of this counter can occur at
re-initialization of the management system, and
10P/2B aggregation discovery code register" at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 61.2.2.8.4, 45.2.6.6-45.2.6.8" 45.2.3.22"
::= { efmCuPmeConfEntry 3 efmCuPortStatusEntry 5 }

efmCuPmeThreshLineAtn

efmCuPAFInLargeFragments OBJECT-TYPE
SYNTAX Integer32(-127..128)
UNITS "dB" Counter32
MAX-ACCESS read-write read-only
STATUS current
DESCRIPTION
"Desired Line Attenuation Threshold for
"A number of fragments larger than maxFragmentSize
(512 Bytes), which have been received across the 2B/10P PME. gamma
interface and discarded.
This read-only counter is inactive when the PAF is
unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value.

If a Clause 45 MDIO Interface to the PCS is present, then
this object configures maps to the line attenuation alarm threshold.
When 10P/2B PAF large fragments
register.

Discontinuities in the current value of Line Attenuation reaches or
exceeds this threshold, a efmCuPmeLineAtnCrossing
notification MAY be generated, if enabled by
efmCuPmeLineAtnCrossingEnable.

This object is writable for counter can occur at
re-initialization of the CO subtype PMEs (-O).
It is read-only for management system, and at other times
as indicated by the CPE subtype (-R).

Changing value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.3.23"
::= { efmCuPortStatusEntry 6 }

efmCuPAFInBadFragments OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A number of fragments which do not fit into the Line Attenuation Threshold MUST be performed
when sequence
expected by the link frame assembly function, that have been
received across the gamma interface and discarded (the
frame buffer is Down. Attempts flushed to change this object MUST be
rejected with the error inconsistentValue, if next valid frame start).
This read-only counter is inactive when the link PAF is Up
unsupported or Initializing. disabled. Upon disabling the PAF, the counter
retains its previous value.

If a Clause 45 MDIO Interface to the PME PCS is present, then
this object maps to the Loop attenuation threshold bits 10P/2B PAF bad fragments
register.

Discontinuities in the 2B PMD line quality thresholds register" value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.1.36" 45.2.3.25"
::= { efmCuPmeConfEntry 4 efmCuPortStatusEntry 7 }

efmCuPmeThreshSnrMgn

efmCuPAFInLostFragments OBJECT-TYPE
SYNTAX Integer32(-127..128)
UNITS "dB" Counter32
MAX-ACCESS read-write read-only
STATUS current
DESCRIPTION
"Desired SNR Margin Threshold for
"A number of gaps in the 2B/10P PME.
This object configures sequence of fragments, which have
been received across the SNR margin alarm threshold.
When gamma interface (the frame buffer is
flushed to the current value of SNR Margin reaches or exceeds this
threshold, a efmCuPmeSnrMgnCrossing notification MAY be
generated, if enabled next valid frame start, when fragment/fragments
expected by efmCuPmeSnrMgnCrossingEnable. the frame assembly function is/are not received).
This object read-only counter is writable for inactive when the CO subtype PMEs
(2BaseTL-O/10PassTS-R). It PAF is read-only for
unsupported or disabled. Upon disabling the CPE subtype
(2BaseTL-R/10PassTS-R).

Changing of the SNR Margin Threshold MUST be performed when
the link is Down. Attempts to change this object MUST be
rejected with the error inconsistentValue, if PAF, the link is Up
or Initializing. counter
retains its previous value.

If a Clause 45 MDIO Interface to the PME PCS is present, then
this object maps to the SNR margin threshold bits 10P/2B PAF lost fragment
register.

Discontinuities in the 2B PMD
line quality thresholds register" value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.1.36" 45.2.3.26"
::= { efmCuPmeConfEntry 5 efmCuPortStatusEntry 8 }

efmCuPmeLineAtnCrossingEnable

efmCuPAFInLostStarts OBJECT-TYPE
SYNTAX TruthValue Counter32
MAX-ACCESS read-write read-only
STATUS current
DESCRIPTION
"Indicates whether efmCuPmeLineAtnCrossing notifications
should be generated for this interface.

Value
"A number of true(1) indicates that efmCuPmeLineAtnCrossing
notification missing StartOfPacket indicators expected by the
frame assembly function.
This read-only counter is enabled. Value of false(2) indicates that inactive when the notification PAF is disabled."
::= { efmCuPmeConfEntry 6 }

efmCuPmeSnrMgnCrossingEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates whether efmCuPmeSnrMgnCrossing notifications
should be generated for
unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value.

If a Clause 45 MDIO Interface to the PCS is present, then
this interface.

Value object maps to the 10P/2B PAF lost start of true(1) indicates that efmCuPmeSnrMgnCrossing
notification is enabled. Value fragment
register.

Discontinuities in the value of this counter can occur at
re-initialization of false(2) indicates that the notification is disabled." management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.3.27"
::= { efmCuPmeConfEntry 7 efmCuPortStatusEntry 9 }

efmCuPmeDeviceFaultEnable

efmCuPAFInLostEnds OBJECT-TYPE
SYNTAX TruthValue Counter32
MAX-ACCESS read-write read-only
STATUS current
DESCRIPTION
"Indicates whether efmCuPmeDeviceFault notifications
should be generated for this interface.

Value
"A number of true(1) indicates that efmCuPmeDeviceFault
notification is enabled. Value of false(2) indicates that missing EndOfPacket indicators expected by the notification
frame assembly function.
This read-only counter is disabled."
::= { efmCuPmeConfEntry 8 }

efmCuPmeConfigInitFailEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates whether efmCuPmeConfigInitFailure notifications
should be generated for this interface.

Value of true(1) indicates that efmCuPmeConfigInitFailure
notification inactive when the PAF is enabled. Value of false(2) indicates that
unsupported or disabled. Upon disabling the notification PAF, the counter
retains its previous value.

If a Clause 45 MDIO Interface to the PCS is disabled."
::= { efmCuPmeConfEntry 9 }

efmCuPmeProtocolInitFailEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates whether efmCuPmeProtocolInitFailure notifications
should be generated for present, then
this interface.

Value object maps to the 10P/2B PAF lost start of true(1) indicates that efmCuPmeProtocolInitFailure
notification is enabled. Value fragment
register.

Discontinuities in the value of this counter can occur at
re-initialization of false(2) indicates that the notification is disabled." management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.3.28"
::= { efmCuPmeConfEntry efmCuPortStatusEntry 10 }

efmCuPmeCapabilityTable

efmCuPAFInOverflows OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPmeCapabilityEntry Counter32
MAX-ACCESS not-accessible read-only
STATUS current
DESCRIPTION
"Table for Configuration of common aspects for EFMCu
2BASE-TL/10PASS-TS PME ports (modems). Configuration
"A number of
aspects specific fragments, received across the gamma interface
and discarded, which would have caused the frame assembly
buffer to 2BASE-TL overflow.
This read-only counter is inactive when the PAF is
unsupported or 10PASS-TS PME types disabled. Upon disabling the PAF, the counter
retains its previous value.

If a Clause 45 MDIO Interface to the PCS is
represented in efmCuPme2BConfTable and efmCuPme10PConfTable
respectively.

Entries in present, then
this table MUST be maintained in a persistent
manner."
::= { efmCuPme 2 }

efmCuPmeCapabilityEntry OBJECT-TYPE
SYNTAX EfmCuPmeCapabilityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry object maps to the 10P/2B PAF overflow register.

Discontinuities in the EFMCu PME Capability table.
Each entry represents common aspects value of an EFMCu PME port
indexed by the ifIndex. Note that an EFMCu PME port this counter can be
stacked below a single PCS port, also indexed by ifIndex,
possibly together with occur at
re-initialization of the management system, and at other PME ports if PAF is enabled."
INDEX { ifIndex } times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.3.24"
::= { efmCuPmeCapabilityTable 1 efmCuPortStatusEntry 11 }

EfmCuPmeCapabilityEntry

-- PME Notifications Group

efmCuPmeNotifications OBJECT IDENTIFIER ::=
SEQUENCE {
efmCuPmeSubTypesSupported BITS efmCuPme 0 }

efmCuPmeSubTypesSupported OBJECT-TYPE
SYNTAX BITS

efmCuPmeLineAtnCrossing NOTIFICATION-TYPE
OBJECTS {
ieee2BaseTLO(0),
ieee2BaseTLR(1),
ieee10PassTSO(2),
ieee10PassTSR(3)
efmCuPmeLineAtn,
efmCuPmeThreshLineAtn
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"PME supported sub-types.
"This notification indicates that the loop attenuation
threshold (as per the efmCuPmeThreshLineAtn
value) has been reached/exceeded for the 2BASE-TL/10PASS-TS
PME. This notification MAY be send on the crossing event in
both directions: from normal to exceeded and from exceeded
to normal.

It is RECOMMENDED that a bitmap of possible
sub-types. The various bit positions are:
ieee2BaseTLO - PME is capable of operating as 2BaseTL-O
ieee2BaseTLR - PME is capable small debouncing period of operating as 2BaseTL-R
ieee10PassTSO - PME is capable 2.5 sec,
between the detection of operating as 10PassTS-O
ieee10PassTSR - PME the condition and notification,
is capable of operating as 10PassTS-R

An desired mode implemented to prevent intermittent notifications to be
sent.

Generation of operation this notification is determined controlled by
efmCuPmeAdminSubType, while efmCuPmeOperSubType reflects the
current operating mode.

If a Clause 45 MDIO Interface to the PCS is present, then this
object combines
efmCuPmeLineAtnCrossingEnable object."
::= { efmCuPmeNotifications 1 }

efmCuPmeSnrMgnCrossing NOTIFICATION-TYPE
OBJECTS {
efmCuPmeSnrMgn,
efmCuPmeThreshSnrMgn
}
STATUS current
DESCRIPTION
"This notification indicates that the 10PASS-TS capable and 2BASE-TL capable
bits in SNR margin threshold
(as per the 10P/2B PMA/PMD speed ability register efmCuPmeThreshSnrMgn value) has been
reached/exceeded for the 2BASE-TL/10PASS-TS PME.
This notification MAY be send on the crossing event in
both directions: from normal to exceeded and from exceeded
to normal.

It is RECOMMENDED that a small debouncing period of 2.5 sec,
between the
CO supported detection of the condition and CPE supported bits in notification,
is implemented to prevent intermittent notifications to be
sent.

Generation of this notification is controlled by the 10P/2B PMA/PMD
status register"
REFERENCE
"[802.3ah] 61.1, 45.2.1.4.1, 45.2.1.4.2, 45.2.1.12.2,
45.2.1.12.3"
efmCuPmeSnrMgnCrossingEnable object."
::= { efmCuPmeCapabilityEntry 1 efmCuPmeNotifications 2 }

efmCuPmeDeviceFault NOTIFICATION-TYPE
OBJECTS {
efmCuPmeFltStatus
}

efmCuPmeStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPmeStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table provides common status information of EFMCu
2BASE-TL/10PASS-TS notification indicates that a fault in the PME ports. Status information has been
detected by a vendor specific
to 10PASS-TS PME diagnostic or a self-test.

Generation of this notification is represented in efmCuPme10PStatusTable.

This table contains live data from controlled by the equipment. As such,
it is NOT persistent."
efmCuPmeDeviceFaultEnable object."
::= { efmCuPme efmCuPmeNotifications 3 }

efmCuPmeStatusEntry OBJECT-TYPE
SYNTAX EfmCuPmeStatusEntry
MAX-ACCESS not-accessible

efmCuPmeConfigInitFailure NOTIFICATION-TYPE
OBJECTS {
efmCuPmeFltStatus,
efmCuAdminProfile,
efmCuPmeAdminProfile
}
STATUS current
DESCRIPTION
"An entry in the EFMCu
"This notification indicates that PME Status table.
Each entry represents common aspects initialization has
failed, due to inability of an EFMCu the PME port
indexed link to achieve requested
configuration profile.

Generation of this notification is controlled by the ifIndex. Note that an
efmCuPmeConfigInitFailEnable object."
::= { efmCuPmeNotifications 4 }

Generation of this notification is controlled by the
efmCuPmeProtocolInitFailEnable object."
::= { efmCuPmeNotifications 5 }

-- The PME group

efmCuPmeConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPmeConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table for Configuration of common aspects for EFMCu
2BASE-TL/10PASS-TS PME ports (modems). Configuration of
aspects specific to 2BASE-TL or 10PASS-TS PME types is
represented in efmCuPme2BConfTable and efmCuPme10PConfTable
respectively.

Entries in this table MUST be maintained in a persistent
manner."
::= { efmCuPme 1 }

efmCuPmeConfEntry OBJECT-TYPE
SYNTAX EfmCuPmeConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the EFMCu PME Configuration table.
Each entry represents common aspects of an EFMCu PME port
indexed by the ifIndex. Note that an EFMCu PME port can be
stacked below a single PCS port, also indexed by ifIndex,
possibly together with other PME ports if PAF is enabled."
INDEX { ifIndex }
::= { efmCuPmeStatusTable efmCuPmeConfTable 1 }

EfmCuPmeStatusEntry

EfmCuPmeConfEntry ::=
SEQUENCE {
efmCuPmeOperStatus INTEGER,
efmCuPmeFltStatus BITS,
efmCuPmeOperSubType
efmCuPmeAdminSubType INTEGER,
efmCuPmeOperProfile
efmCuPmeAdminProfile ProfileIndexOrZero,
efmCuPmeSnrMgn Integer32,
efmCuPmePeerSnrMgn Integer32,
efmCuPmeLineAtn
efmCuPAFRemoteDiscoveryCode PhysAddress,
efmCuPmeThreshLineAtn Integer32,
efmCuPmePeerLineAtn
efmCuPmeThreshSnrMgn Integer32,
efmCuPmeEquivalentLength Unsigned32,
efmCuPmeTCCodingErrors Counter32,
efmCuPmeTCCrcErrors Counter32
efmCuPmeLineAtnCrossingEnable TruthValue,
efmCuPmeSnrMgnCrossingEnable TruthValue,
efmCuPmeDeviceFaultEnable TruthValue,
efmCuPmeConfigInitFailEnable TruthValue,
efmCuPmeProtocolInitFailEnable TruthValue
}

efmCuPmeOperStatus

efmCuPmeAdminSubType OBJECT-TYPE
SYNTAX INTEGER {
up(1),
downNotReady(2),
downReady(3),
init(4)
ieee2BaseTLO(1),
ieee2BaseTLR(2),
ieee10PassTSO(3),
ieee10PassTSR(4),
ieee2BaseTLor10PassTSR(5),
ieee2BaseTLor10PassTSO(6),
ieee10PassTSor2BaseTLO(7)
}
MAX-ACCESS read-only read-write
STATUS current
DESCRIPTION
"Current PME link Operational Status.
"Administrative (desired) sub-type of the PME.
Possible values are:
up(1) - link is Up and ready to pass 64/65B
encoded frames or fragments.
downNotReady(2)
ieee2BaseTLO - link is Down and the PME does not detect
Handshake tones from its peer. This value
may indicate a possible problem with
the peer PME.
downReady(3) SHALL operate as 2BaseTL-O
ieee2BaseTLR - link is Down and the PME detects Handshake
tones from its peer.
init(4) SHALL operate as 2BaseTL-R
ieee10PassTSO - PME SHALL operate as 10PassTS-O
ieee10PassTSR - PME SHALL operate as 10PassTS-R
ieee2BaseTLor10PassTSR - PME SHALL operate as 2BaseTL-R or
10PassTS-R. Actual value will be
set by -O link is initializing, partner during
initialization (handshake).
ieee2BaseTLor10PassTSO - PME SHALL operate as a result of
ifAdminStatus being 2BaseTL-O
(preferred) or 10PassTS-O. Actual
value will be set to 'up' for a
particular during
initialization depending on -R
link partner capability (i.e. if
-R is incapable of the preferred
2BaseTL mode, 10PassTS will be
used).
ieee10PassTSor2BaseTLO - PME SHALL operate as 10PassTS-O
(preferred) or 2BaseTL-O. Actual
value will be set during
initialization depending on -R
link partner capability (i.e. if
-R is incapable of the preferred
10PassTS mode, 2BaseTL will be
used).

Changing efmCuPmeAdminSubType is a PCS traffic disruptive
operation and as such SHALL be done when the PME link is
connected to.

This Down.
Attempts to change this object SHALL be ignored if the link
is intended Up or Initializing.
Attempts to supplement Down state of
ifOperStatus.

This change this object partially maps to the Clause 30 attribute
aPMEStatus. an unsupported subtype
(see efmCuPmeSubTypesSupported) SHALL be rejected.

The current operational sub type is indicated by
efmCuPmeOperSubType variable.

If a Clause 45 MDIO Interface to the PME PMA/PMD is present, then
this object partially maps to combines values of the Port sub-type select bits
and the PMA/PMD link status type selection bits in the 10P/2B PMA/PMD status register."
control register"
REFERENCE
"[802.3ah] 30.11.2.1.3, 45.2.1.12.4" 61.1, 45.2.1.11.4, 45.2.1.11.7"
::= { efmCuPmeStatusEntry efmCuPmeConfEntry 1 }

efmCuPmeFltStatus

efmCuPmeAdminProfile OBJECT-TYPE
SYNTAX BITS {
lossOfFraming(0),
snrMgnDefect(1),
lineAtnDefect(2),
deviceFault(3),
configInitFailure(4),
protocolInitFailure(5)
} ProfileIndexOrZero
MAX-ACCESS read-only read-write
STATUS current
DESCRIPTION
"Current/Last
"Desired PME link Fault Status. configuration Profile. This object is a bitmap of
possible conditions. The various bit positions are:

lossOfFraming - Loss of Framing for 10P pointer
to an entry in either efmCuPme2BProfileTable or
Loss
efmCuPme10PProfileTable, depending on the current operating
SubType of Sync word for 2B PMD or
Loss the PME. The value of 64/65B Framing
snrMgnDefect - SNR Margin dropped below this object is the Threshold
lineAtnDefect - Line Attenuation exceeds index of
the Threshold
deviceFault - Indicates a vendor-dependent
diagnostic or self-test fault
has been detected.
configInitFailure - Configuration initialization failure,
due to inability referenced profile.
The value of zero (default) indicates that the PME link to
support configuration profile,
requested during initialization.
protocolInitFailure - Protocol initialization failure,
due to incompatible protocol used by is
configured via efmCuAdminProfile object for the Peer PCS port,
to which this PME during init (that could
happen if a peer PMD is a regular
G.SDHSL/VDSL modem instead of a
2BASE-TL/10PASS-TS PME). assigned. That is, the profile referenced
by efmCuPmeAdminProfile takes precedence over the profile(s)
referenced by efmCuAdminProfile.

This object is intended to supplement ifOperStatus in IF-MIB.

This object holds information about writable and readable for the last fault.
efmCuPmeFltStatus CO subtype PMEs
(2BaseTL-O or 10PassTS-O). It is cleared by unavailable for the device restart.
In addition lossOfFraming, configInitFailure and
protocolInitFailure are cleared by PME init.
deviceFault CPE
subtype (2BaseTL-R or 10PassTS-R).

Note that current operational Profile value is cleared by successful diagnostics/test.
snrMgnDefect and lineAtnDefect are cleared by SNR Margin
and line Attenuation respectively returning to norm and by
PME init.

This available via
efmCuPmeOperProfile object.

Modification of this object partially maps to the Clause 30 attribute
aPMEStatus.

If a Clause 45 MDIO Interface to MUST be performed when the PME link is present, then
Down. Attempts to change this object consolidates information from various PMA/PMD
registers, namely: Fault bit in PMA/PMD status 1 register,
10P/2B PMA/PMD MUST be rejected, if the
link loss register,
10P outgoing indicator bits status register,
10P incoming indicator bits status register,
2B state defects register." is Up or Initializing.
Attempts to set this object to a value that is not the value
of the index for an active entry in the corresponding profile
table, MUST be rejected."
REFERENCE
"[802.3ah] 30.11.2.1.3, 45.2.1.2.1, 45.2.1.38,
45.2.1.39, 45.2.1.54" 30.11.2.1.6"
DEFVAL { 0 }
::= { efmCuPmeStatusEntry efmCuPmeConfEntry 2 }

efmCuPmeOperSubType

efmCuPAFRemoteDiscoveryCode OBJECT-TYPE
SYNTAX INTEGER {
ieee2BaseTLO(1),
ieee2BaseTLR(2),
ieee10PassTSO(3),
ieee10PassTSR(4)
} PhysAddress
MAX-ACCESS read-only read-write
STATUS current
DESCRIPTION
"Current operational sub-type
"PAF Remote Discovery Code of the PME.
Possible values are:
ieee2BaseTLO - PME operates as 2BaseTL-O
ieee2BaseTLR - PME operates as 2BaseTL-R
ieee10PassTSO - PME operates as 10PassTS-O
ieee10PassTSR - PME operates as 10PassTS-R

The operational sub type port at CO.
A 6 Byte long Discovery Code of the PME can be configured peer PCS connected via
efmCuPmeAdminSubType variable.

If
the PME.
Reading this object results in a Clause 45 MDIO Interface Discovery Get operation.
Writing a zero to the PMA/PMD is present, then this object combines values results in a Discovery
Clear_if_Same operation (the value of efmCuPAFDiscoveryCode
at the Port sub-type select
bits, peer PCS SHALL be the PMA/PMD type selection bits in same as efmCuPAFDiscoveryCode of
the 10P/2B
PMA/PMD control register and local PCS associated with the PMA/PMD link status bits in PME for the 10P/2B PMA/PMD status register."
REFERENCE
"[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7, 45.2.1.12.4"
::= { efmCuPmeStatusEntry 3 }

efmCuPmeOperProfile OBJECT-TYPE
SYNTAX ProfileIndexOrZero
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"PME current operating Profile. This object is operation to
succeed).
Writing a pointer non-zero value to
an entry this object results in either efmCuPme2BProfileTable or
efmCuPme10PProfileTable, depending on the current
operating SubType of the PME as indicated by
efmCuPmeOperSubType.
Note that a profile entry, to which efmCuPmeOperProfile is
pointing to, can be created automatically, to reflect achieved
parameters
Discovery Set_if_Clear operation.
This object does not exist in adaptive (not fixed) initialization,
i.e. values of efmCuPmeOperProfile and efmCuAdminProfile or
efmCuPmeAdminProfile MAY differ.
The value of CPE port subtypes. A zero indicates that PME length
octet string SHALL be returned for CPE port subtypes and also
when PAF aggregation is down or initializing.

This object partially maps to not enabled.

Discovery MUST be performed when the aOperatingProfile
attribute in Clause 30."
REFERENCE
"[802.3ah] 30.11.2.1.7"
::= { efmCuPmeStatusEntry 4 }

efmCuPmeSnrMgn OBJECT-TYPE
SYNTAX Integer32(-127..128|65535)
UNITS "dB"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current Signal-to-Noise Ratio (SNR) margin with respect link is Down.
Attempts to change this object MUST be rejected with the received signal as perceived by error
inconsistentValue, if the local PME.
The value of 65535 is returned when PME link is down Up or
initializing.

This object maps to the aPMESNRMgn attribute in Clause 30. Initializing.

If a Clause 45 MDIO Interface to the PMA/PMD is present, then
this object maps to the is a function of 10P/2B RX SNR margin register." aggregation discovery
control register, Discovery operation result bits in 10P/2B
aggregation and discovery status register and
10P/2B aggregation discovery code register"
REFERENCE
"[802.3ah] 30.11.2.1.4, 45.2.1.16" 61.2.2.8.4, 45.2.6.6-45.2.6.8"
::= { efmCuPmeStatusEntry 5 efmCuPmeConfEntry 3 }

efmCuPmePeerSnrMgn

efmCuPmeThreshLineAtn OBJECT-TYPE
SYNTAX Integer32(-127..128|65535) Integer32(-127..128)
UNITS "dB"
MAX-ACCESS read-only read-write
STATUS current
DESCRIPTION
"The current SNR margin in dB with respect to the received
signal, as perceived by
"Desired Line Attenuation Threshold for the remote (link partner) 2B/10P PME.
The value of 65535 is returned when PME is down
This object configures the line attenuation alarm threshold.
When the current value of Line Attenuation reaches or
initializing.
exceeds this threshold, a efmCuPmeLineAtnCrossing
notification MAY be generated, if enabled by
efmCuPmeLineAtnCrossingEnable.

This object is not supported by -R PME subtypes. writable for the CO subtype PMEs (-O).
It is read-only for the CPE subtype (-R).

Changing of the Line Attenuation Threshold MUST be performed
when the link is Down. Attempts to change this object MUST be
rejected with the error inconsistentValue, if the link is Up
or Initializing.

If a Clause 45 MDIO Interface to the PME is present, then this
object maps to the 10P/2B link partner RX SNR margin
register." Loop attenuation threshold bits in
the 2B PMD line quality thresholds register"
REFERENCE
"[802.3ah] 45.2.1.17" 45.2.1.36"
::= { efmCuPmeStatusEntry 6}

efmCuPmeLineAtn efmCuPmeConfEntry 4 }

efmCuPmeThreshSnrMgn OBJECT-TYPE
SYNTAX Integer32(-127..128|65535) Integer32(-127..128)
UNITS "dB"
MAX-ACCESS read-only read-write
STATUS current
DESCRIPTION
"The current Line Attenuation in dB as perceived by
"Desired SNR Margin Threshold for the local 2B/10P PME.
The
This object configures the SNR margin alarm threshold.
When the current value of 65535 SNR Margin reaches or exceeds this
threshold, a efmCuPmeSnrMgnCrossing notification MAY be
generated, if enabled by efmCuPmeSnrMgnCrossingEnable.

This object is returned writable for the CO subtype PMEs
(2BaseTL-O/10PassTS-R). It is read-only for the CPE subtype
(2BaseTL-R/10PassTS-R).

Changing of the SNR Margin Threshold MUST be performed when PME
the link is down Down. Attempts to change this object MUST be
rejected with the error inconsistentValue, if the link is Up
or
initializing. Initializing.

If a Clause 45 MDIO Interface to the PME is present, then this
object maps to the Line Attenuation SNR margin threshold bits in the 2B PMD
line quality thresholds register"
REFERENCE
"[802.3ah] 45.2.1.18" 45.2.1.36"
::= { efmCuPmeStatusEntry 7 efmCuPmeConfEntry 5 }

efmCuPmePeerLineAtn

efmCuPmeLineAtnCrossingEnable OBJECT-TYPE
SYNTAX Integer32(-127..128|65535)
UNITS "dB" TruthValue
MAX-ACCESS read-only read-write
STATUS current
DESCRIPTION
"The current Line Attenuation in dB as perceived by the remote
(link partner) PME.
The value
"Indicates whether efmCuPmeLineAtnCrossing notifications
should be generated for this interface.

Value of 65535 is returned when PME is down or
initializing.

This object is not supported by CPE port subtypes.

If a Clause 45 MDIO Interface true(1) indicates that efmCuPmeLineAtnCrossing
notification is present, then this
object maps to enabled. Value of false(2) indicates that
the 20P/2B link partner Line Attenuation
register."
REFERENCE
"[802.3ah] 45.2.1.19" notification is disabled."
::= { efmCuPmeStatusEntry 8 efmCuPmeConfEntry 6 }

efmCuPmeEquivalentLength

efmCuPmeSnrMgnCrossingEnable OBJECT-TYPE
SYNTAX Unsigned32(0..8192|65535)
UNITS "m" TruthValue
MAX-ACCESS read-only read-write
STATUS current
DESCRIPTION
"An estimate
"Indicates whether efmCuPmeSnrMgnCrossing notifications
should be generated for this interface.

Value of the equivalent loop's Physical Length in
meters, as perceived by the PME after the link is established.
An equivalent loop true(1) indicates that efmCuPmeSnrMgnCrossing
notification is a hypothetical 26AWG (0.4mm) loop with a
perfect square root attenuation characteristic, without any
bridged taps.
The value enabled. Value of 65535 is returned if the link is Down or
Initializing or the PME is unable to estimate the Equivalent
Length.

For 10BASE-TL PME, if a Clause 45 MDIO Interface to false(2) indicates that
the PME notification is
present, then this object maps to the 10P Electrical Length
register"
REFERENCE
"[802.3ah] 45.2.1.21" disabled."
::= { efmCuPmeStatusEntry 9 efmCuPmeConfEntry 7 }

efmCuPmeTCCodingErrors

efmCuPmeDeviceFaultEnable OBJECT-TYPE
SYNTAX Counter32 TruthValue
MAX-ACCESS read-only read-write
STATUS current
DESCRIPTION
"A number
"Indicates whether efmCuPmeDeviceFault notifications
should be generated for this interface.

Value of 64/65-octet encapsulation errors. This counter true(1) indicates that efmCuPmeDeviceFault
notification is
incremented for each 64/65-octet encapsulation error detected
by the 64/65-octet receive function.
The value enabled. Value of zero SHALL be returned when PME false(2) indicates that
the notification is down or
initializing.

If a Clause 45 MDIO Interface to the PME TC is present, then
this object maps to the TC coding violations register
(see 45.2.6.12)."
REFERENCE
"[802.3ah] 61.3.3.1, 45.2.6.12" disabled."
::= { efmCuPmeStatusEntry 10 efmCuPmeConfEntry 8 }

efmCuPmeTCCrcErrors

efmCuPmeConfigInitFailEnable OBJECT-TYPE
SYNTAX Counter32 TruthValue
MAX-ACCESS read-only read-write
STATUS current
DESCRIPTION
"A number of TC-CRC errors. This counter is incremented
"Indicates whether efmCuPmeConfigInitFailure notifications
should be generated for
each TC-CRC error detected by the 64/65-octet receive function
(see 61.3.3.3 and Figure 61-19).
The value this interface.

Value of zero SHALL be returned when PME true(1) indicates that efmCuPmeConfigInitFailure
notification is down or
initializing.

If a Clause 45 MDIO Interface to enabled. Value of false(2) indicates that
the PCME TC notification 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" disabled."
::= { efmCuPmeStatusEntry 11 efmCuPmeConfEntry 9 }

-- 2BASE-TL specific PME group

efmCuPme2B OBJECT IDENTIFIER

Value of true(1) indicates that efmCuPmeProtocolInitFailure
notification is enabled. Value of false(2) indicates that
the notification is disabled."
::= { efmCuPme 5 efmCuPmeConfEntry 10 }

efmCuPme2BProfileTable

efmCuPmeCapabilityTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme2BProfileEntry EfmCuPmeCapabilityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table supports definitions
"Table for Configuration of administrative and
operating Profiles common aspects for EFMCu
2BASE-TL/10PASS-TS PME ports (modems). Configuration of
aspects specific to 2BASE-TL PMEs.
First 14 entries or 10PASS-TS PME types is
represented in efmCuPme2BConfTable and efmCuPme10PConfTable
respectively.

Entries in this table SHALL always MUST be defined as
follows (see 802.3ah Annex 63A):
-------+-------+-------+-----+------+------------------
Profile MinRate MaxRate Power Region Constellation
index (Kbps) (Kbps) (dBm)
-------+-------+-------+-----+------+------------------
1 5696 5696 13.5 1 32-TCPAM (default) maintained in a persistent
manner."
::= { efmCuPme 2 3072 3072 13.5 1 32-TCPAM
3 2048 2048 13.5 1 16-TCPAM
4 1024 1024 13.5 1 16-TCPAM
5 704 704 13.5 1 16-TCPAM
6 512 512 13.5 1 16-TCPAM
7 5696 5696 14.5 2 32-TCPAM
8 3072 3072 14.5 2 32-TCPAM
9 2048 2048 14.5 2 16-TCPAM
10 1024 1024 13.5 2 16-TCPAM
11 704 704 13.5 2 16-TCPAM
12 512 512 13.5 2 16-TCPAM
13 192 5696 0 1 0 (best effort)
14 192 5696 0 2 0 (best effort)

These default entries SHALL be created during agent
initialization and MUST NOT be deleted.

Entries following }

efmCuPmeCapabilityEntry OBJECT-TYPE
SYNTAX EfmCuPmeCapabilityEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the first 14, EFMCu PME Capability table.
Each entry represents common aspects of an EFMCu PME port
indexed by the ifIndex. Note that an EFMCu PME port can be dynamically created and
deleted, to provide custom administrative (configuration)
profiles and automatic operating profiles.

This table MUST be maintained in
stacked below a persistent manner."
REFERENCE
"[802.3ah] Annex 63A, 30.11.2.1.6" single PCS port, also indexed by ifIndex,
possibly together with other PME ports if PAF is enabled."
INDEX { ifIndex }
::= { efmCuPme2B 2 efmCuPmeCapabilityTable 1 }

efmCuPme2BProfileEntry

EfmCuPmeCapabilityEntry ::=
SEQUENCE {
efmCuPmeSubTypesSupported BITS
}

efmCuPmeSubTypesSupported OBJECT-TYPE
SYNTAX EfmCuPme2BProfileEntry BITS {
ieee2BaseTLO(0),
ieee2BaseTLR(1),
ieee10PassTSO(2),
ieee10PassTSR(3)
}
MAX-ACCESS not-accessible read-only
STATUS current
DESCRIPTION
"Each entry corresponds to
"PME supported sub-types. This is a single 2BASE-TL bitmap of possible
sub-types. The various bit positions are:
ieee2BaseTLO - PME profile.
Each profile contains a set is capable of parameters, used either for
configuration or representation operating as 2BaseTL-O
ieee2BaseTLR - PME is capable of a 2BASE-TL PME.
In case a particular profile operating as 2BaseTL-R
ieee10PassTSO - PME is referenced via
efmCuPmeAdminProfile object (or efmCuAdminProfile if
efmCuPmeAdminProfile capable of operating as 10PassTS-O
ieee10PassTSR - PME is zero), it represent the capable of operating as 10PassTS-R

An desired
parameters mode of operation is determined by
efmCuPmeAdminSubType, while efmCuPmeOperSubType reflects the 2BaseTL-O PME initialization.
current operating mode.

If a profile Clause 45 MDIO Interface to the PCS is referenced via efmCuPmeOperProfile object,
it represents current operating parameters of present, then this
object combines the
operational PME.

Profiles may be created/deleted using 10PASS-TS capable and 2BASE-TL capable
bits in the row creation/
deletion mechanism via efmCuPme2BProfileRowStatus. If an
active entry is referenced, 10P/2B PMA/PMD speed ability register and the entry MUST remain 'active'
until all references are removed.
Default entries MUST NOT be removed."
INDEX { efmCuPme2BProfileIndex }
CO supported and CPE supported bits in the 10P/2B PMA/PMD
status register"
REFERENCE
"[802.3ah] 61.1, 45.2.1.4.1, 45.2.1.4.2, 45.2.1.12.2,
45.2.1.12.3"
::= { efmCuPme2BProfileTable efmCuPmeCapabilityEntry 1 }
EfmCuPme2BProfileEntry ::=
SEQUENCE {
efmCuPme2BProfileIndex ProfileIndex,
efmCuPme2BProfileDescr SnmpAdminString,
efmCuPme2BRegion INTEGER,
efmCuPme2BsMode ProfileIndexOrZero,
efmCuPme2BMinDataRate Unsigned32,
efmCuPme2BMaxDataRate Unsigned32,
efmCuPme2BPower Unsigned32,
efmCuPme2BConstellation INTEGER,
efmCuPme2BProfileRowStatus RowStatus
}

efmCuPme2BProfileIndex

efmCuPmeStatusTable OBJECT-TYPE
SYNTAX ProfileIndex SEQUENCE OF EfmCuPmeStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"2BASE-TL
"This table provides common status information of EFMCu
2BASE-TL/10PASS-TS PME ports. Status information specific
to 10PASS-TS PME Profile index.
This object is the unique index associated with this profile.
Entries represented in this efmCuPme10PStatusTable.

This table are referenced via efmCuAdminProfile
or efmCuPmeAdminProfile objects." contains live data from the equipment. As such,
it is NOT persistent."
::= { efmCuPme2BProfileEntry 1 efmCuPme 3 }

efmCuPme2BProfileDescr

efmCuPmeStatusEntry OBJECT-TYPE
SYNTAX SnmpAdminString EfmCuPmeStatusEntry
MAX-ACCESS read-create not-accessible
STATUS current
DESCRIPTION
"A textual string containing information about 2BASE-TL
"An entry in the EFMCu PME
Profile. The string MAY include information about data rate
and spectral limitations Status table.
Each entry represents common aspects of this particular profile." an EFMCu PME port
indexed by the ifIndex. Note that an EFMCu PME port can be
stacked below a single PCS port, also indexed by ifIndex,
possibly together with other PME ports if PAF is enabled."
INDEX { ifIndex }
::= { efmCuPme2BProfileEntry 2 efmCuPmeStatusTable 1 }

efmCuPme2BRegion

EfmCuPmeStatusEntry ::=
SEQUENCE {
efmCuPmeOperStatus INTEGER,
efmCuPmeFltStatus BITS,
efmCuPmeOperSubType INTEGER,
efmCuPmeOperProfile ProfileIndexOrZero,
efmCuPmeSnrMgn Integer32,
efmCuPmePeerSnrMgn Integer32,
efmCuPmeLineAtn Integer32,
efmCuPmePeerLineAtn Integer32,
efmCuPmeEquivalentLength Unsigned32,
efmCuPmeTCCodingErrors Counter32,
efmCuPmeTCCrcErrors Counter32
}

efmCuPmeOperStatus OBJECT-TYPE
SYNTAX INTEGER {
region1(1),
region2(2)
up(1),
downNotReady(2),
downReady(3),
init(4)
}
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION
"Regional settings for 2BASE-TL PME, as specified in the
relevant Regional Annex of [G.991.2].
Regional settings specify Power Spectral Density (PSD) mask,
Power Back-Off (PBO) values and place limitations on the max
allowed data rate, power and constellation.
"Current PME link Operational Status. Possible values for this object are:
region1
up(1) - Annexes A link is Up and F (e.g. North America)
region2 ready to pass 64/65B
encoded frames or fragments.
downNotReady(2) - Annexes B and G (e.g. Europe)

Annex A/B specify regional settings for data rates 192-2304
Kbps using 16-TCPAM encoding.
Annex F/G specify regional settings for rates 2320-3840 Kbps
using 16-TCPAM encoding link is Down and 768-5696 Kbps using 32-TCPAM
encoding.

If a Clause 45 MDIO Interface to the PME is present, then this
object partially maps to does not detect
Handshake tones from its peer. This value
may indicate a possible problem with
the Region bits in peer PME.
downReady(3) - link is Down and the 2B general
parameter register."
REFERENCE
"[802.3ah] 45.2.1.42; [G.991.2] Annexes A, B, F and G"
::= { efmCuPme2BProfileEntry 3 }

efmCuPme2BsMode OBJECT-TYPE
SYNTAX ProfileIndexOrZero
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Desired custom Spectral Mode for 2BASE-TL PME. This object PME detects Handshake
tones from its peer.
init(4) - link is initializing, as a pointer result of
ifAdminStatus being set to an entry in efmCuPme2BsModeTable and 'up' for a block
of entries in efmCuPme2BRateReachTable, which together define
(country-specific) reach dependent rate limitations in
addition
particular PME or a PCS the PME is
connected to.

This object is intended to those defined by efmCuPme2BRegion.

The value supplement Down state of this
ifOperStatus.

This object is partially maps to the index of Clause 30 attribute
aPMEStatus.

If a Clause 45 MDIO Interface to the referenced
spectral mode.
The value of zero (default) indicates that no specific
spectral mode PME is applicable.

Attempts to set present, then this
object partially maps to a value that is not the value
of the index for an active entry PMA/PMD link status bits in the corresponding spectral
mode table, MUST be rejected." 10P/2B
PMA/PMD status register."
REFERENCE
"efmCuPme2BsModeTable, efmCuPme2BRateReachTable"
DEFVAL { 0 }
"[802.3ah] 30.11.2.1.3, 45.2.1.12.4"
::= { efmCuPme2BProfileEntry 4 efmCuPmeStatusEntry 1 }

efmCuPme2BMinDataRate

efmCuPmeFltStatus OBJECT-TYPE
SYNTAX Unsigned32(192..5696)
UNITS "Kbps" BITS {
lossOfFraming(0),
snrMgnDefect(1),
lineAtnDefect(2),
deviceFault(3),
configInitFailure(4),
protocolInitFailure(5)
}
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION
"Minimum Data Rate for the 2BASE-TL PME.
"Current/Last PME link Fault Status. This object can take values is a bitmap of (n x 64)Kbps,
where n=3..60
possible conditions. The various bit positions are:

lossOfFraming - Loss of Framing for 16-TCPAM and n=12..89 10P or
Loss of Sync word for 32-TCPAM encoding.

The data rate 2B PMD or
Loss of 64/65B Framing
snrMgnDefect - SNR Margin dropped below the 2BASE-TL PME is considered 'fixed' when Threshold
lineAtnDefect - Line Attenuation exceeds the value of this object equals that Threshold
deviceFault - Indicates a vendor-dependent
diagnostic or self-test fault
has been detected.
configInitFailure - Configuration initialization failure,
due to inability of efmCuPme2BMaxDataRate.
If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in the administrative PME link to
support configuration profile,
requested during initialization.
protocolInitFailure - Protocol initialization failure,
due to incompatible protocol used by
the data rate Peer PME during init (that could
happen if a peer PMD is considered
'adaptive', and SHALL be set a regular
G.SDHSL/VDSL modem instead of a
2BASE-TL/10PASS-TS PME).

This object is intended to supplement ifOperStatus in IF-MIB.

This object holds information about the maximum attainable rate
not exceeding efmCuPme2BMaxDataRate, under the spectral
limitations placed last fault.
efmCuPmeFltStatus is cleared by the efmCuPme2BRegion device restart.
In addition lossOfFraming, configInitFailure and
efmCuPme2BsMode.

Note that current operational data rate of the
protocolInitFailure are cleared by PME init.
deviceFault is
represented cleared by ifSpeed successful diagnostics/test.
snrMgnDefect and lineAtnDefect are cleared by SNR Margin
and line Attenuation respectively returning to norm and by
PME init.

This object of IF-MIB. partially maps to the Clause 30 attribute
aPMEStatus.

If a Clause 45 MDIO Interface to the PME is present, then this
object maps to the Min Data Rate1 bits consolidates information from various PMA/PMD
registers, namely: Fault bit in the PMA/PMD status 1 register,
10P/2B PMA/PMD link loss register,
10P outgoing indicator bits status register,
10P incoming indicator bits status register,
2B PMD
parameters register.

This object MUST be maintained in a persistent manner." state defects register."
REFERENCE
"[802.3ah] 45.2.1.43" 30.11.2.1.3, 45.2.1.2.1, 45.2.1.38,
45.2.1.39, 45.2.1.54"
::= { efmCuPme2BProfileEntry 5 efmCuPmeStatusEntry 2 }

efmCuPme2BMaxDataRate

efmCuPmeOperSubType OBJECT-TYPE
SYNTAX Unsigned32(192..5696)
UNITS "Kbps" INTEGER {
ieee2BaseTLO(1),
ieee2BaseTLR(2),
ieee10PassTSO(3),
ieee10PassTSR(4)
}
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION
"Maximum Data Rate for
"Current operational sub-type of the 2BASE-TL PME.
This object can take
Possible values of (n x 64)Kbps,
where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM encoding.

The data rate of the 2BASE-TL are:
ieee2BaseTLO - PME is considered 'fixed' when
the value of this object equals that of efmCuPme2BMinDataRate.
If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in
the administrative profile, the data rate is considered
'adaptive', and SHALL be set to the maximum attainable rate
not exceeding efmCuPme2BMaxDataRate, under the spectral
limitations placed by the efmCuPme2BRegion and
efmCuPme2BsMode.

Note that current operates as 2BaseTL-O
ieee2BaseTLR - PME operates as 2BaseTL-R
ieee10PassTSO - PME operates as 10PassTS-O
ieee10PassTSR - PME operates as 10PassTS-R

The operational data rate sub type of the PME is
represented by ifSpeed object of IF-MIB. can be configured via
efmCuPmeAdminSubType variable.

If a Clause 45 MDIO Interface to the PME PMA/PMD is present, then
this object maps to combines values of the Max Data Rate1 Port sub-type select
bits, the PMA/PMD type selection bits in the 2B PMD
parameters register.

This object MUST be maintained 10P/2B
PMA/PMD control register and the PMA/PMD link status bits in a persistent manner."
the 10P/2B PMA/PMD status register."
REFERENCE
"[802.3ah] 45.2.1.43" 61.1, 45.2.1.11.4, 45.2.1.11.7, 45.2.1.12.4"
::= { efmCuPme2BProfileEntry 6 efmCuPmeStatusEntry 3 }

efmCuPme2BPower

efmCuPmeOperProfile OBJECT-TYPE
SYNTAX Unsigned32(0|10..42)
UNITS "0.5 dBm" ProfileIndexOrZero
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION
"Signal Transmit Power. Multiple of 0.5dBm.
The value of 0
"PME current operating Profile. This object is a pointer to
an entry in either efmCuPme2BProfileTable or
efmCuPme10PProfileTable, depending on the administrative profile means that current
operating SubType of the
signal transmit power PME as indicated by
efmCuPmeOperSubType.
Note that a profile entry, to which efmCuPmeOperProfile is not fixed and SHALL
pointing to, can be set created automatically, to reflect achieved
parameters in adaptive (not fixed) initialization,
i.e. values of efmCuPmeOperProfile and efmCuAdminProfile or
efmCuPmeAdminProfile MAY differ.
The value of zero indicates that PME is down or initializing.

This object partially maps to
maximize the attainable rate, under aOperatingProfile
attribute in Clause 30."
REFERENCE
"[802.3ah] 30.11.2.1.7"
::= { efmCuPmeStatusEntry 4 }

efmCuPmeSnrMgn OBJECT-TYPE
SYNTAX Integer32(-127..128|65535)
UNITS "dB"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current Signal-to-Noise Ratio (SNR) margin with respect
to the spectral limitations
placed received signal as perceived by the efmCuPme2BRegion and efmCuPme2BsMode. local PME.
The value of 65535 is returned when PME is down or
initializing.

This object maps to the aPMESNRMgn attribute in Clause 30.

If a Clause 45 MDIO Interface to the PME is present, then this
object maps to the Power1 bits in the 2B PMD parameters
register" 10P/2B RX SNR margin register."
REFERENCE
"[802.3ah] 45.2.1.43" 30.11.2.1.4, 45.2.1.16"
::= { efmCuPme2BProfileEntry 7 efmCuPmeStatusEntry 5 }

efmCuPme2BConstellation

efmCuPmePeerSnrMgn OBJECT-TYPE
SYNTAX INTEGER {
adaptive(0),
tcpam16(1),
tcpam32(2)
} Integer32(-127..128|65535)
UNITS "dB"
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION
"TCPAM Constellation of
"The current SNR margin in dB with respect to the 2BASE-TL received
signal, as perceived by the remote (link partner) PME.
The possible values are:
adaptive(0) - either 16- or 32-TCPAM
tcpam16(1) - 16-TCPAM
tcpam32(2) - 32-TCPAM

The value of adaptive(0) in the administrative profile means
that the constellation 65535 is returned when PME is down or
initializing.

This object is not fixed and SHALL be set to
maximize the attainable rate, under the spectral limitations
placed supported by the efmCuPme2BRegion and efmCuPme2BsMode. -R PME subtypes.

If a Clause 45 MDIO Interface to the PME is present, then this
object maps to the Constellation1 bits in the 2B general
parameter 10P/2B link partner RX SNR margin
register."
REFERENCE
"[802.3ah] 45.2.1.43" 45.2.1.17"
::= { efmCuPme2BProfileEntry 8 }

efmCuPme2BProfileRowStatus efmCuPmeStatusEntry 6}

efmCuPmeLineAtn OBJECT-TYPE
SYNTAX RowStatus Integer32(-127..128|65535)
UNITS "dB"
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION
"This object controls creation/deletion of the associated
entry
"The current Line Attenuation in efmCuPme2BProfileTable per dB as perceived by the semantics local
PME.
The value of
RowStatus.
If an 'active' entry 65535 is referenced via efmCuAdminProfile returned when PME is down or
efmCuPmeAdminProfile,
initializing.

If a Clause 45 MDIO Interface is present, then this
object maps to the entry MUST remain 'active' until all
references are removed." Line Attenuation register"
REFERENCE
"[802.3ah] 45.2.1.18"
::= { efmCuPme2BProfileEntry 9 efmCuPmeStatusEntry 7 }

efmCuPme2BsModeTable

efmCuPmePeerLineAtn OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme2BsModeEntry Integer32(-127..128|65535)
UNITS "dB"
MAX-ACCESS not-accessible read-only
STATUS current
DESCRIPTION
"This table, together with efmCu2BReachRateTable, supports
definition of administrative custom spectral modes for
2BASE-TL PMEs, describing spectral limitations
"The current Line Attenuation in addition to
those specified dB as perceived by efmCuPme2BRegion.

Some countries spectral regulations (e.g. UK ANFP) limit the
length remote
(link partner) PME.
The value of the loops for certain data rates. 65535 is returned when PME is down or
initializing.

This table allows
these country-specific limitations to be specified.

Entries in this table referenced object is not supported by the efmCuPme2BsMode
MUST NOT be deleted until all the active references are
removed.

This table MUST be maintained in CPE port subtypes.

If a persistent manner." Clause 45 MDIO Interface is present, then this
object maps to the 20P/2B link partner Line Attenuation
register."
REFERENCE
"efmCu2BReachRateTable"
"[802.3ah] 45.2.1.19"
::= { efmCuPme2B 3 efmCuPmeStatusEntry 8 }

efmCuPme2BsModeEntry

efmCuPmeEquivalentLength OBJECT-TYPE
SYNTAX EfmCuPme2BsModeEntry Unsigned32(0..8192|65535)
UNITS "m"
MAX-ACCESS not-accessible read-only
STATUS current
DESCRIPTION
"Each entry specifies spectral mode description and its index,
which is used to reference corresponding entries
"An estimate of the equivalent loop's Physical Length in
meters, as perceived by the
efmCu2BReachRateTable.

Entries may be created/deleted using PME after the link is established.
An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a
perfect square root attenuation characteristic, without any
bridged taps.
The value of 65535 is returned if the link is Down or
Initializing or the row creation/
deletion mechanism via efmCuPme2BsModeRowStatus."
INDEX { efmCuPme2BsModeIndex }
::= { efmCuPme2BsModeTable 1 }

EfmCuPme2BsModeEntry ::=
SEQUENCE {
efmCuPme2BsModeIndex ProfileIndex,
efmCuPme2BsModeDescr SnmpAdminString,
efmCuPme2BsModeRowStatus RowStatus
}

efmCuPme2BsModeIndex OBJECT-TYPE
SYNTAX ProfileIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"2BASE-TL PME Spectral Mode index.
This object is unable to estimate the unique index associated with this spectral
mode.
Entries in Equivalent
Length.

For 10BASE-TL PME, if a Clause 45 MDIO Interface to the PME is
present, then this table are referenced via efmCuPme2BsMode
object." object maps to the 10P Electrical Length
register"
REFERENCE
"[802.3ah] 45.2.1.21"
::= { efmCuPme2BsModeEntry 1 efmCuPmeStatusEntry 9 }

efmCuPme2BsModeDescr

efmCuPmeTCCodingErrors OBJECT-TYPE
SYNTAX SnmpAdminString Counter32
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION
"A textual string containing information about 2BASE-TL number of 64/65-octet encapsulation errors. This counter is
incremented for each 64/65-octet encapsulation error detected
by the 64/65-octet receive function.

This object maps to aTCCodingViolations attribute in
clause 30.

If a Clause 45 MDIO Interface to the PME
spectral mode. The string MAY include information about
corresponding (country-specific) spectral regulations
and rate/reach limitations TC is present, then
this object maps to the TC coding violations register
(see 45.2.6.12).

Discontinuities in the value of this particular spectral mode." counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 61.3.3.1, 30.11.2.1.5, 45.2.6.12"
::= { efmCuPme2BsModeEntry 2 efmCuPmeStatusEntry 10 }

efmCuPme2BsModeRowStatus

efmCuPmeTCCrcErrors OBJECT-TYPE
SYNTAX RowStatus Counter32
MAX-ACCESS read-create read-only
STATUS current
DESCRIPTION
"This object controls creation/deletion
"A number of TC-CRC errors. This counter is incremented for
each TC-CRC error detected by the associated
entry 64/65-octet receive function
(see 61.3.3.3 and Figure 61-19).

This object maps to aTCCRCErrors attribute in efmCuPme2BsModeTable per the semantics of
RowStatus.
clause 30.

If an 'active' entry a Clause 45 MDIO Interface to the PCME TC is referenced via efmCuPme2BsMode, present, then
this object maps to the
entry MUST remain 'active' until all references are removed." TC CRC error register
(see 45.2.6.11).

Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 61.3.3.3, 30.11.2.1.10, 45.2.6.11"
::= { efmCuPme2BsModeEntry 3 efmCuPmeStatusEntry 11 }

efmCuPme2BReachRateTable

-- 2BASE-TL specific PME group
efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 }

efmCuPme2BProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme2BReachRateEntry EfmCuPme2BProfileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table supports definition definitions of administrative custom
spectral modes and
operating Profiles for 2BASE-TL PMEs, providing spectral
limitations in addition to those specified by
efmCuPme2BRegion.

The spectral regulations PMEs.
First 14 entries in some countries (e.g. UK ANFP)
limit the length of the loops for certain data rates.
This table allows these country-specific limitations to be
specified.

Below is an example of this table for [ANFP]:
----------+-------+-------+
Equivalent MaxRate SHALL always be defined as
follows (see 802.3ah Annex 63A):
-------+-------+-------+-----+------+------------------
Profile MinRate MaxRate
Length PAM16 PAM32
(m) Power Region Constellation
index (Kbps) (Kbps)
----------+-------+-------+
975 2304 (dBm)
-------+-------+-------+-----+------+------------------
1 5696
1125 2304 5504
1275 2304 5120
1350 2304 4864
1425 2304 4544
1500 2304 4288
1575 2304 3968
1650 2304 3776
1725 2304 3520
1800 2304 3264
1875 2304 5696 13.5 1 32-TCPAM (default)
2 3072
1950 3072 13.5 1 32-TCPAM
3 2048 2688
2100 1792 2368
2250 1536 0
2400 1408 0
2550 1280 0
2775 1152 0
2925 1152 0
3150 1088 0
3375 2048 13.5 1 16-TCPAM
4 1024 1024 13.5 1 16-TCPAM
5 704 704 13.5 1 16-TCPAM
6 512 512 13.5 1 16-TCPAM
7 5696 5696 14.5 2 32-TCPAM
8 3072 3072 14.5 2 32-TCPAM
9 2048 2048 14.5 2 16-TCPAM
10 1024 1024 13.5 2 16-TCPAM
11 704 704 13.5 2 16-TCPAM
12 512 512 13.5 2 16-TCPAM
13 192 5696 0
----------+-------+-------+

Entries in this table referenced by the efmCuPme2BsMode 1 0 (best effort)
14 192 5696 0 2 0 (best effort)

These default entries SHALL be created during agent
initialization and MUST NOT be deleted until all deleted.

Entries following the active references are
removed. first 14, can be dynamically created and
deleted, to provide custom administrative (configuration)
profiles and automatic operating profiles.

This table MUST be maintained in a persistent manner."
REFERENCE
"[ANFP]"
"[802.3ah] Annex 63A, 30.11.2.1.6"
::= { efmCuPme2B 4 2 }

efmCuPme2BReachRateEntry

efmCuPme2BProfileEntry OBJECT-TYPE
SYNTAX EfmCuPme2BReachRateEntry EfmCuPme2BProfileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry specifies maximum corresponds to a single 2BASE-TL PME data rates
allowed for profile.

Each profile contains a certain equivalent loop length, when using
16-TCPAM set of parameters, used either for
configuration or 32-TCPAM encoding.

When representation of a 2BASE-TL PME PME.
In case a particular profile is initialized, its data rate MUST NOT
exceed one of referenced via
efmCuPmeAdminProfile object (or efmCuAdminProfile if
efmCuPmeAdminProfile is zero), it represent the following limitations:
- desired
parameters the value of efmCuPme2BMaxDataRate
- maximum data rate allowed by efmCuPme2BRegion and
efmCuPme2BPower
- maximum data rate for 2BaseTL-O PME initialization.
If a given encoding specified in the
efmCuPme2BsModeEntry, corresponding to the equivalent loop
length, estimated by profile is referenced via efmCuPmeOperProfile object,
it represents current operating parameters of the
operational PME.

It is RECOMMENDED that the efmCuPme2BEquivalentLength values
are assigned in the increasing order, starting from the
minimum value.

Entries may be created/deleted using

Profiles may be created/deleted using the row creation/
deletion mechanism via efmCuPme2ReachRateRowStatus." efmCuPme2BProfileRowStatus. If an
active entry is referenced, the entry MUST remain 'active'
until all references are removed.
Default entries MUST NOT be removed."
INDEX { efmCuPme2BsModeIndex, efmCuPme2BEquivalentLength efmCuPme2BProfileIndex }
::= { efmCuPme2BReachRateTable efmCuPme2BProfileTable 1 }

EfmCuPme2BReachRateEntry

EfmCuPme2BProfileEntry ::=
SEQUENCE {
efmCuPme2BEquivalentLength
efmCuPme2BProfileIndex ProfileIndex,
efmCuPme2BProfileDescr SnmpAdminString,
efmCuPme2BRegion INTEGER,
efmCuPme2BsMode ProfileIndexOrZero,
efmCuPme2BMinDataRate Unsigned32,
efmCuPme2BMaxDataRatePam16
efmCuPme2BMaxDataRate Unsigned32,
efmCuPme2BMaxDataRatePam32
efmCuPme2BPower Unsigned32,
efmCuPme2BReachRateRowStatus
efmCuPme2BConstellation INTEGER,
efmCuPme2BProfileRowStatus RowStatus
}

efmCuPme2BEquivalentLength

efmCuPme2BProfileIndex OBJECT-TYPE
SYNTAX Unsigned32(0..8192)
UNITS "m" ProfileIndex
MAX-ACCESS read-create not-accessible
STATUS current
DESCRIPTION
"Maximum allowed Equivalent loop's Physical Length in meters
for the specified data rates.
An equivalent loop
"2BASE-TL PME Profile index.
This object is a hypothetical 26AWG (0.4mm) loop the unique index associated with a
perfect square root attenuation characteristic, without any
bridged taps."
REFERENCE
"" this profile.
Entries in this table are referenced via efmCuAdminProfile
or efmCuPmeAdminProfile objects."
::= { efmCuPme2BReachRateEntry efmCuPme2BProfileEntry 1 }

efmCuPme2BMaxDataRatePam16

efmCuPme2BProfileDescr OBJECT-TYPE
SYNTAX Unsigned32(0|192..5696)
UNITS "Kbps" SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Maximum data rate for
"A textual string containing information about 2BASE-TL PME at the specified
Equivalent loop's Length using TC-PAM16 encoding.
Profile. The value string MAY include information about data rate
and spectral limitations of zero means that TC-PAM16 encoding should not be
used at this distance."
REFERENCE
"" particular profile."
::= { efmCuPme2BReachRateEntry efmCuPme2BProfileEntry 2 }

efmCuPme2BMaxDataRatePam32

efmCuPme2BRegion OBJECT-TYPE
SYNTAX Unsigned32(0|192..5696)
UNITS "Kbps" INTEGER {
region1(1),
region2(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Maximum data rate
"Regional settings for 2BASE-TL PME at the PME, as specified
Equivalent loop's Length using TC-PAM32 encoding.
The value of zero means that TC-PAM32 encoding should not be
used at this distance."
REFERENCE
""
::= { efmCuPme2BReachRateEntry 3 }

efmCuPme2BReachRateRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object controls creation/deletion of the associated
entry in efmCuPme2BReachRateTable per the semantics
relevant Regional Annex of
RowStatus. [G.991.2].
Regional settings specify Power Spectral Density (PSD) mask,
Power Back-Off (PBO) values and place limitations on the max
allowed data rate, power and constellation.

Possible values for this object are:
region1 - Annexes A and F (e.g. North America)
region2 - Annexes B and G (e.g. Europe)

If a Clause 45 MDIO Interface to the PME is present, then this
object partially maps to the Region bits in the 2B general
parameter register."
REFERENCE
"[802.3ah] 45.2.1.42; [G.991.2] Annexes A, B, F and G"
::= { efmCuPme2BProfileEntry 3 }

efmCuPme2BsMode OBJECT-TYPE
SYNTAX ProfileIndexOrZero
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Desired custom Spectral Mode for 2BASE-TL PME. This object
is a pointer to an 'active' entry in efmCuPme2BsModeTable and a block
of entries in efmCuPme2BRateReachTable, which together define
(country-specific) reach dependent rate limitations in
addition to those defined by efmCuPme2BRegion.

The value of this object is the index of the referenced via efmCuPme2BsMode,
spectral mode.

The value of zero (default) indicates that no specific
spectral mode is applicable.

Attempts to set this object to a value that is not the value
of the index for an active entry in the corresponding spectral
mode table, MUST remain 'active' until all references are removed."
::= be rejected."
REFERENCE
"efmCuPme2BsModeTable, efmCuPme2BRateReachTable"
DEFVAL { efmCuPme2BReachRateEntry 4 0 }
-- 10PASS-TS specific PME group

efmCuPme10P OBJECT IDENTIFIER
::= { efmCuPme 6 efmCuPme2BProfileEntry 4 }

efmCuPme10PProfileTable

efmCuPme2BMinDataRate OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme10PProfileEntry Unsigned32(192..5696)
UNITS "Kbps"
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
"This table supports definitions
"Minimum Data Rate for the 2BASE-TL PME.
This object can take values of configuration profiles (n x 64)Kbps,
where n=3..60 for
10PassTL PMEs.
First 22 entries in 16-TCPAM and n=12..89 for 32-TCPAM encoding.

The data rate of the 2BASE-TL PME is considered 'fixed' when
the value of this table object equals that of efmCuPme2BMaxDataRate.
If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in
the administrative profile, the data rate is considered
'adaptive', and SHALL always be defined as
follows (see 802.3ah Annex 62B.3):
-------+--------+----+---------+-----+------------
Profile Bandplan UPBO BandNotch DRate URate
Index PSDMask# p# p# p# p#
-------+--------+----+---------+-----+------------
1 1 3 2,6,10,11 20 20(default)
2 13 5 0 20 20
3 1 1 0 20 20
4 16 0 0 100 100
5 16 0 0 70 50
6 6 0 0 50 10
7 17 0 0 30 30
8 8 0 0 30 5
9 4 0 0 25 25
10 4 0 0 15 15
11 23 0 0 10 10
12 23 0 0 5 set to the maximum attainable rate
not exceeding efmCuPme2BMaxDataRate, under the spectral
limitations placed by the efmCuPme2BRegion and
efmCuPme2BsMode.

Note that current operational data rate of the PME is
represented by ifSpeed object of IF-MIB.

If a Clause 45 MDIO Interface to the PME is present, then this
object maps to the Min Data Rate1 bits in the 2B PMD
parameters register.

This object MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] 45.2.1.43"
::= { efmCuPme2BProfileEntry 5
13 16 0 2,5,9,11 100 100
14 16 0 2,5,9,11 70 50
15 6 0 2,6,10,11 50 10
16 17 }

efmCuPme2BMaxDataRate OBJECT-TYPE
SYNTAX Unsigned32(192..5696)
UNITS "Kbps"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Maximum Data Rate for the 2BASE-TL PME.
This object can take values of (n x 64)Kbps,
where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM encoding.

The data rate of the 2BASE-TL PME is considered 'fixed' when
the value of this object equals that of efmCuPme2BMinDataRate.
If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in
the administrative profile, the data rate is considered
'adaptive', and SHALL be set to the maximum attainable rate
not exceeding efmCuPme2BMaxDataRate, under the spectral
limitations placed by the efmCuPme2BRegion and
efmCuPme2BsMode.

Note that current operational data rate of the PME is
represented by ifSpeed object of IF-MIB.

If a Clause 45 MDIO Interface to the PME is present, then this
object maps to the Max Data Rate1 bits in the 2B PMD
parameters register.

This object MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] 45.2.1.43"
::= { efmCuPme2BProfileEntry 6 }

efmCuPme2BPower OBJECT-TYPE
SYNTAX Unsigned32(0|10..42)
UNITS "0.5 dBm"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Signal Transmit Power. Multiple of 0.5dBm.
The value of 0 2,5,9,11 30 30
17 8 in the administrative profile means that the
signal transmit power is not fixed and SHALL be set to
maximize the attainable rate, under the spectral limitations
placed by the efmCuPme2BRegion and efmCuPme2BsMode.

If a Clause 45 MDIO Interface to the PME is present, then this
object maps to the Power1 bits in the 2B PMD parameters
register"
REFERENCE
"[802.3ah] 45.2.1.43"
::= { efmCuPme2BProfileEntry 7 }

efmCuPme2BConstellation OBJECT-TYPE
SYNTAX INTEGER {
adaptive(0),
tcpam16(1),
tcpam32(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"TCPAM Constellation of the 2BASE-TL PME.
The possible values are:
adaptive(0) - either 16- or 32-TCPAM
tcpam16(1) - 16-TCPAM
tcpam32(2) - 32-TCPAM

The value of adaptive(0) in the administrative profile means
that the constellation is not fixed and SHALL be set to
maximize the attainable rate, under the spectral limitations
placed by the efmCuPme2BRegion and efmCuPme2BsMode.

If a Clause 45 MDIO Interface to the PME is present, then this
object maps to the Constellation1 bits in the 2B general
parameter register."
REFERENCE
"[802.3ah] 45.2.1.43"
::= { efmCuPme2BProfileEntry 8 }

efmCuPme2BProfileRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object controls creation/deletion of the associated
entry in efmCuPme2BProfileTable per the semantics of
RowStatus.
If an 'active' entry is referenced via efmCuAdminProfile or
efmCuPmeAdminProfile, the entry MUST remain 'active' until all
references are removed."
::= { efmCuPme2BProfileEntry 9 }

efmCuPme2BsModeTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme2BsModeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table, together with efmCu2BReachRateTable, supports
definition of administrative custom spectral modes for
2BASE-TL PMEs, describing spectral limitations in addition to
those specified by efmCuPme2BRegion.

Some countries spectral regulations (e.g. UK ANFP) limit the
length of the loops for certain data rates. This table allows
these country-specific limitations to be specified.

Entries in this table referenced by the efmCuPme2BsMode
MUST NOT be deleted until all the active references are
removed.

This table MUST be maintained in a persistent manner."
REFERENCE
"efmCu2BReachRateTable"
::= { efmCuPme2B 3 }

efmCuPme2BsModeEntry OBJECT-TYPE
SYNTAX EfmCuPme2BsModeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry specifies spectral mode description and its index,
which is used to reference corresponding entries in the
efmCu2BReachRateTable.

Entries may be created/deleted using the row creation/
deletion mechanism via efmCuPme2BsModeRowStatus."
INDEX { efmCuPme2BsModeIndex }
::= { efmCuPme2BsModeTable 1 }

EfmCuPme2BsModeEntry ::=
SEQUENCE {
efmCuPme2BsModeIndex ProfileIndex,
efmCuPme2BsModeDescr SnmpAdminString,
efmCuPme2BsModeRowStatus RowStatus
}

efmCuPme2BsModeIndex OBJECT-TYPE
SYNTAX ProfileIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"2BASE-TL PME Spectral Mode index.
This object is the unique index associated with this spectral
mode.
Entries in this table are referenced via efmCuPme2BsMode
object."
::= { efmCuPme2BsModeEntry 1 }

efmCuPme2BsModeDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A textual string containing information about 2BASE-TL PME
spectral mode. The string MAY include information about
corresponding (country-specific) spectral regulations
and rate/reach limitations of this particular spectral mode."
::= { efmCuPme2BsModeEntry 2 }

efmCuPme2BsModeRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object controls creation/deletion of the associated
entry in efmCuPme2BsModeTable per the semantics of
RowStatus.
If an 'active' entry is referenced via efmCuPme2BsMode, the
entry MUST remain 'active' until all references are removed."
::= { efmCuPme2BsModeEntry 3 }

efmCuPme2BReachRateTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme2BReachRateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table supports definition of administrative custom
spectral modes for 2BASE-TL PMEs, providing spectral
limitations in addition to those specified by
efmCuPme2BRegion.

The spectral regulations in some countries (e.g. UK ANFP)
limit the length of the loops for certain data rates.
This table allows these country-specific limitations to be
specified.

Below is an example of this table for [ANFP]:
----------+-------+-------+
Equivalent MaxRate MaxRate
Length PAM16 PAM32
(m) (Kbps) (Kbps)
----------+-------+-------+
975 2304 5696
1125 2304 5504
1275 2304 5120
1350 2304 4864
1425 2304 4544
1500 2304 4288
1575 2304 3968
1650 2304 3776
1725 2304 3520
1800 2304 3264
1875 2304 3072
1950 2048 2688
2100 1792 2368
2250 1536 0 2,6,10,11 30 5
18 4
2400 1408 0 2,6,10,11 25 25
19 4
2550 1280 0 2,6,10,11 15 15
20 23
2775 1152 0 2,5,9,11 10 10
21 23
2925 1152 0 2,5,9,11 5 5
22 30
3150 1088 0
3375 1024 0 200 50

These default entries SHALL be created
----------+-------+-------+

Entries in this table referenced by during agent
initialization and the efmCuPme2BsMode
MUST NOT be deleted.

Entries following deleted until all the first 22, can be dynamically created and
deleted, to provide custom administrative (configuration)
profiles and automatic operating profiles. active references are
removed.

This table MUST be maintained in a persistent manner."
REFERENCE
"[802.3ah] Annex 62B.3, 30.11.2.1.6"
"[ANFP]"
::= { efmCuPme10P 1 efmCuPme2B 4 }

efmCuPme10PProfileEntry

efmCuPme2BReachRateEntry OBJECT-TYPE
SYNTAX EfmCuPme10PProfileEntry EfmCuPme2BReachRateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry corresponds to a single 10PASS-TS specifies maximum 2BASE-TL PME
profile.
Each profile contains a set of parameters, used either data rates
allowed for
configuration a certain equivalent loop length, when using
16-TCPAM or representation 32-TCPAM encoding.

When 2BASE-TL PME is initialized, its data rate MUST NOT
exceed one of the following limitations:
- the value of efmCuPme2BMaxDataRate
- maximum data rate allowed by efmCuPme2BRegion and
efmCuPme2BPower
- maximum data rate for a 10PASS-TS given encoding specified in the
efmCuPme2BsModeEntry, corresponding to the equivalent loop
length, estimated by the PME.
In case a particular profile is referenced via
efmCuPmeAdminProfile object (or efmCuAdminProfile if
efmCuPmeAdminProfile

It is zero), it represent RECOMMENDED that the desired
parameters efmCuPme2BEquivalentLength values
are assigned in the 10PassTS-O PME initialization.
If a profile is referenced via efmCuPmeOperProfile object,
it represents current operating parameters of increasing order, starting from the PME.

Profiles
minimum value.

Entries may be created/deleted using the row creation/
deletion mechanism via efmCuPme10PProfileRowStatus. If an
'active' entry is referenced, the entry MUST remain 'active'
until all references are removed.
Default entries MUST NOT be removed." efmCuPme2ReachRateRowStatus."
INDEX { efmCuPme10PProfileIndex efmCuPme2BsModeIndex, efmCuPme2BReachRateIndex }
::= { efmCuPme10PProfileTable efmCuPme2BReachRateTable 1 }

EfmCuPme10PProfileEntry

EfmCuPme2BReachRateEntry ::=
SEQUENCE {
efmCuPme10PProfileIndex
efmCuPme2BReachRateIndex ProfileIndex,
efmCuPme10PProfileDescr SnmpAdminString,
efmCuPme10PBandplanPSDMskProfile INTEGER,
efmCuPme10PUPBOReferenceProfile INTEGER,
efmCuPme10PBandNotchProfiles BITS,
efmCuPme10PPayloadURateProfile INTEGER,
efmCuPme10PPayloadDRateProfile INTEGER,
efmCuPme10PProfileRowStatus
efmCuPme2BEquivalentLength Unsigned32,
efmCuPme2BMaxDataRatePam16 Unsigned32,
efmCuPme2BMaxDataRatePam32 Unsigned32,
efmCuPme2BReachRateRowStatus RowStatus
}

efmCuPme10PProfileIndex

efmCuPme2BReachRateIndex OBJECT-TYPE
SYNTAX ProfileIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"10PASS-TS PME Profile Index.
"2BASE-TL custom spectral mode Reach-Rate table index.
This object is the unique index associated with this profile.
Entries in this table are referenced via efmCuAdminProfile or
efmCuPmeAdminProfile." each enry."
::= { efmCuPme10PProfileEntry efmCuPme2BReachRateEntry 1 }

efmCuPme10PProfileDescr

efmCuPme2BEquivalentLength OBJECT-TYPE
SYNTAX SnmpAdminString Unsigned32(0..8192)
UNITS "m"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A textual string containing information about 10PASS-TS PME
Profile. The string MAY include information about
"Maximum allowed Equivalent loop's Physical Length in meters
for the specified data rate
and spectral limitations of this particular profile." rates.
An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a
perfect square root attenuation characteristic, without any
bridged taps."
::= { efmCuPme10PProfileEntry efmCuPme2BReachRateEntry 2 }

efmCuPme10PBandplanPSDMskProfile

efmCuPme2BMaxDataRatePam16 OBJECT-TYPE
SYNTAX INTEGER {
profile1(1),
profile2(2),
profile3(3),
profile4(4),
profile5(5),
profile6(6),
profile7(7),
profile8(8),
profile9(9),
profile10(10),
profile11(11),
profile12(12),
profile13(13),
profile14(14),
profile15(15),
profile16(16),
profile17(17),
profile18(18),
profile19(19),
profile20(20),
profile21(21),
profile22(22),
profile23(23),
profile24(24),
profile25(25),
profile26(26),
profile27(27),
profile28(28),
profile29(29)
} Unsigned32(0|192..5696)
UNITS "Kbps"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"10PASS-TS
"Maximum data rate for 2BASE-TL PME Bandplan and PSD Mask profile,
as specified in 802.3ah Annex 62A. Possible values are:
--------------+------------------------+-----------+---------
Profile Name PSD Mask Bands Bandplan
--------------+------------------------+-----------+---------
profile1(1) - T1.424/T-U P1 FTTCab.M1 x/D/U/D/U A
profile2(2) - T1.424/T-U P1 FTTEx.M1
profile3(3) - T1.424/T-U P1 FTTCab.M2
profile4(4) - T1.424/T-U P1 FTTEx.M2
profile5(5) - T1.424/T-U P1 FTTCab.M1 D/D/U/D/U
profile6(6) - T1.424/T-U P1 FTTEx.M1
profile7(7) - T1.424/T-U P1 FTTCab.M2
profile8(8) - T1.424/T-U P1 FTTEx.M2
profile9(9) - T1.424/T-U P1 FTTCab.M1 U/D/U/D/x
profile10(10) - T1.424/T-U P1 FTTEx.M1
profile11(11) - T1.424/T-U P1 FTTCab.M2
profile12(12) - T1.424/T-U P1 FTTEx.M2
profile13(13) - TS1 101 270-1 Pcab.M1.A x/D/U/D/U B
profile14(14) - TS1 101 270-1 Pcab.M1.B
profile15(15) - TS1 101 270-1 Pex.P1.M1
profile16(16) - TS1 101 270-1 Pex.P2.M1
profile17(17) - TS1 101 270-1 Pcab.M2
profile18(18) - TS1 101 270-1 Pex.P1.M2
profile19(19) - TS1 101 270-1 Pex.P2.M2
profile20(20) - TS1 101 270-1 Pcab.M1.A U/D/U/D/x
profile21(21) - TS1 101 270-1 Pcab.M1.B
profile22(22) - TS1 101 270-1 Pex.P1.M1
profile23(23) - TS1 101 270-1 Pex.P2.M1
profile24(24) - TS1 101 270-1 Pcab.M2
profile25(25) - TS1 101 270-1 Pex.P1.M2
profile26(26) - TS1 101 270-1 Pex.P2.M2
profile27(27) - G.993.1 F.1.2.1 (VDSLoPOTS) x/D/U/D/U F
profile28(28) - G.993.1 F.1.2.2 (VDSLoTCM-ISDN)
profile29(29) - G.993.1 F.1.2.3 (PSD reduction)

This object maps to at the aBandplanPSDMaskProfile attribute
in Clause 30."
REFERENCE
"[802.3ah] Annex 62A, 30.5.1.1.22" specified
Equivalent loop's Length using TC-PAM16 encoding.
The value of zero means that TC-PAM16 encoding should not be
used at this distance."
::= { efmCuPme10PProfileEntry efmCuPme2BReachRateEntry 3 }

efmCuPme10PUPBOReferenceProfile

efmCuPme2BMaxDataRatePam32 OBJECT-TYPE
SYNTAX INTEGER {
profile1(1),
profile2(2),
profile3(3),
profile4(4),
profile5(5),
profile6(6),
profile7(7),
profile8(8),
profile9(9)
} Unsigned32(0|192..5696)
UNITS "Kbps"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"10PASS-TS
"Maximum data rate for 2BASE-TL PME Upstream Power Back-Off (UPBO) Reference PSD
Profile, as specified in 802.3ah Annex 62A. Possible values
are:
profile1(1) - T1.424/T-U Noise A M1
profile2(2) - T1.424/T-U Noise A M2
profile3(3) - T1.424/T-U Noise F M1
profile4(4) - T1.424/T-U Noise F M2
profile5(5) - ETSI TS 101 270-1 Noise A&B
profile6(6) - ETSI TS 101 270-1 Noise C
profile7(7) - ETSI TS 101 270-1 Noise D
profile8(8) - ETSI TS 101 270-1 Noise E
profile9(9) - ETSI TS 101 270-1 Noise F

This object maps to at the aUPBOReferenceProfile attribute
in Clause 30."
REFERENCE
"[802.3ah] Annex 62A.3.4, 30.5.1.1.23" specified
Equivalent loop's Length using TC-PAM32 encoding.
The value of zero means that TC-PAM32 encoding should not be
used at this distance."
::= { efmCuPme10PProfileEntry efmCuPme2BReachRateEntry 4 }

efmCuPme10PBandNotchProfiles

efmCuPme2BReachRateRowStatus OBJECT-TYPE
SYNTAX BITS {
profile0(0),
profile1(1),
profile2(2),
profile3(3),
profile4(4),
profile5(5),
profile6(6),
profile7(7),
profile8(8),
profile9(9),
profile10(10),
profile11(11)
} RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"10PASS-TS
"This object controls creation/deletion of the associated
entry in efmCuPme2BReachRateTable per the semantics of
RowStatus.
If an 'active' entry is referenced via efmCuPme2BsMode, the
entry MUST remain 'active' until all references are removed."
::= { efmCuPme2BReachRateEntry 5 }

-- 10PASS-TS specific PME Egress Control Band Notch Profile bitmap,
as specified group

efmCuPme10P OBJECT IDENTIFIER ::= { efmCuPme 6 }

efmCuPme10PProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme10PProfileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table supports definitions of configuration profiles for
10PassTL PMEs.
First 22 entries in this table SHALL always be defined as
follows (see 802.3ah Annex 62A. Possible values are:
--------------+---------+----------+-----------+------+----- 62B.3):
-------+--------+----+---------+-----+------------
Profile Name G.991.3 T1.424/T-U TS101 270-1 StartF EndF
Table Table Table (MHz) (MHz)
--------------+---------+----------+-----------+------+-----
profile0(0) - no profile
profile1(1) - F-5 #01 - - 1.810 1.825
profile2(2) - 6-2 15-1 Bandplan UPBO BandNotch DRate URate
Index PSDMask# p# p# p# p#
-------+--------+----+---------+-----+------------
1 1 3 2,6,10,11 20 20(default)
2 13 5 0 20 20
3 1 1 0 20 20
4 16 0 0 100 100
5 16 0 0 70 50
6 6 0 0 50 10
7 17 1.810 2.000
profile3(3) - F-5 #02 - - 1.907 1.912
profile4(4) - F-5 #03 - - 3.500 3.575
profile5(5) - 6-2 - 0 0 30 30
8 8 0 0 30 5
9 4 0 0 25 25
10 4 0 0 15 15
11 23 0 0 10 10
12 23 0 0 5 5
13 16 0 2,5,9,11 100 100
14 16 0 2,5,9,11 70 50
15 6 0 2,6,10,11 50 10
16 17 3.500 3.800
profile6(6) - - 15-1 - 3.500 4.000
profile7(7) - F-5 #04 - - 3.747 3.754
profile8(8) - F-5 #05 - - 3.791 3.805
profile9(9) - 6-2 - 0 2,5,9,11 30 30
17 7.000 7.100
profile10(10) - F-5 #06 15-1 - 7.000 7.300
profile11(11) - 6-2 15-1 1 10.100 10.150

Any combination of profiles can 8 0 2,6,10,11 30 5
18 4 0 2,6,10,11 25 25
19 4 0 2,6,10,11 15 15
20 23 0 2,5,9,11 10 10
21 23 0 2,5,9,11 5 5
22 30 0 0 200 50

These default entries SHALL be specified created by ORing
individual profiles, for example value of 0x0622 selects during agent
initialization and MUST NOT be deleted.

Entries following the first 22, can be dynamically created and
deleted, to provide custom administrative (configuration)
profiles 2,6,10 and 11. automatic operating profiles.

This object maps to the aBandNotchProfile attribute table MUST be maintained in Clause 30." a persistent manner."
REFERENCE
"[802.3ah] Annex 62A.3.5, 30.5.1.1.19" 62B.3, 30.11.2.1.6"
::= { efmCuPme10PProfileEntry 5 efmCuPme10P 1 }

efmCuPme10PPayloadURateProfile

efmCuPme10PProfileEntry OBJECT-TYPE
SYNTAX INTEGER {
profile5(5),
profile10(10),
profile15(15),
profile20(20),
profile25(25),
profile30(30),
profile50(50),
profile70(70),
profile100(100)
} EfmCuPme10PProfileEntry
MAX-ACCESS read-create not-accessible
STATUS current
DESCRIPTION
"10PASS-TS
"Each entry corresponds to a single 10PASS-TS PME Upstream Payload Rate Profile,
as specified in 802.3ah Annex 62A. Possible values are:
profile5(5) - 2.5 Mbps
profile10(10) - 5 Mbps
profile15(15) - 7.5 Mbps
profile20(20) - 10 Mbps
profile25(25) - 12.5 Mbps
profile30(30) - 15 Mbps
profile50(50) - 25 Mbps
profile70(70) - 35 Mbps
profile100(100) - 50 Mbps
profile.
Each value represents profile contains a target set of parameters, used either for
configuration or representation of a 10PASS-TS PME.
In case a particular profile is referenced via
efmCuPmeAdminProfile object (or efmCuAdminProfile if
efmCuPmeAdminProfile is zero), it represent the PME's Upstream Payload
Bitrate as seen at desired
parameters the MII. 10PassTS-O PME initialization.
If the payload rate a profile is referenced via efmCuPmeOperProfile object,
it represents current operating parameters of the
selected profile cannot PME.

Profiles may be achieved based on created/deleted using the loop
environment, bandplan and PSD mask, row creation/
deletion mechanism via efmCuPme10PProfileRowStatus. If an
'active' entry is referenced, the entry MUST remain 'active'
until all references are removed.

Default entries MUST NOT be removed."
INDEX { efmCuPme10PProfileIndex }
::= { efmCuPme10PProfileTable 1 }

EfmCuPme10PProfileEntry ::=
SEQUENCE {
efmCuPme10PProfileIndex ProfileIndex,
efmCuPme10PProfileDescr SnmpAdminString,
efmCuPme10PBandplanPSDMskProfile INTEGER,
efmCuPme10PUPBOReferenceProfile INTEGER,
efmCuPme10PBandNotchProfiles BITS,
efmCuPme10PPayloadURateProfile INTEGER,
efmCuPme10PPayloadDRateProfile INTEGER,
efmCuPme10PProfileRowStatus RowStatus
}

efmCuPme10PProfileIndex OBJECT-TYPE
SYNTAX ProfileIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"10PASS-TS PME initialization
SHALL fail. Profile Index.
This object maps to is the aPayloadRateProfileUpstream
attribute unique index associated with this profile.
Entries in Clause 30."
REFERENCE
"[802.3ah] Annex 62A.3.6, 30.5.1.1.20" this table are referenced via efmCuAdminProfile or
efmCuPmeAdminProfile."
::= { efmCuPme10PProfileEntry 6 1 }

efmCuPme10PPayloadDRateProfile

efmCuPme10PProfileDescr OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"A textual string containing information about 10PASS-TS PME
Profile. The string MAY include information about data rate
and spectral limitations of this particular profile."
::= { efmCuPme10PProfileEntry 2 }

efmCuPme10PBandplanPSDMskProfile OBJECT-TYPE
SYNTAX INTEGER {
profile1(1),
profile2(2),
profile3(3),
profile4(4),
profile5(5),
profile6(6),
profile7(7),
profile8(8),
profile9(9),
profile10(10),
profile11(11),
profile12(12),
profile13(13),
profile14(14),
profile15(15),
profile16(16),
profile17(17),
profile18(18),
profile19(19),
profile20(20),
profile21(21),
profile22(22),
profile23(23),
profile24(24),
profile25(25),
profile30(30),
profile50(50),
profile70(70),
profile100(100),
profile140(140),
profile200(200)
profile26(26),
profile27(27),
profile28(28),
profile29(29)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"10PASS-TS PME Downstream Payload Rate Profile, Bandplan and PSD Mask profile,
as specified in 802.3ah Annex 62A. Possible values are:
--------------+------------------------+-----------+---------
Profile Name PSD Mask Bands Bandplan
--------------+------------------------+-----------+---------
profile1(1) - T1.424/T-U P1 FTTCab.M1 x/D/U/D/U A
profile2(2) - T1.424/T-U P1 FTTEx.M1
profile3(3) - T1.424/T-U P1 FTTCab.M2
profile4(4) - T1.424/T-U P1 FTTEx.M2
profile5(5) - 2.5 Mbps T1.424/T-U P1 FTTCab.M1 D/D/U/D/U
profile6(6) - T1.424/T-U P1 FTTEx.M1
profile7(7) - T1.424/T-U P1 FTTCab.M2
profile8(8) - T1.424/T-U P1 FTTEx.M2
profile9(9) - T1.424/T-U P1 FTTCab.M1 U/D/U/D/x
profile10(10) - 5 Mbps
profile15(15) T1.424/T-U P1 FTTEx.M1
profile11(11) - T1.424/T-U P1 FTTCab.M2
profile12(12) - T1.424/T-U P1 FTTEx.M2
profile13(13) - TS1 101 270-1 Pcab.M1.A x/D/U/D/U B
profile14(14) - TS1 101 270-1 Pcab.M1.B
profile15(15) - TS1 101 270-1 Pex.P1.M1
profile16(16) - TS1 101 270-1 Pex.P2.M1
profile17(17) - TS1 101 270-1 Pcab.M2
profile18(18) - TS1 101 270-1 Pex.P1.M2
profile19(19) - 7.5 Mbps TS1 101 270-1 Pex.P2.M2
profile20(20) - 10 Mbps
profile25(25) TS1 101 270-1 Pcab.M1.A U/D/U/D/x
profile21(21) - 12.5 Mbps
profile30(30) TS1 101 270-1 Pcab.M1.B
profile22(22) - 15 Mbps
profile50(50) TS1 101 270-1 Pex.P1.M1
profile23(23) - 25 Mbps
profile70(70) TS1 101 270-1 Pex.P2.M1
profile24(24) - 35 Mbps
profile100(100) TS1 101 270-1 Pcab.M2
profile25(25) - 50 Mbps
profile140(140) TS1 101 270-1 Pex.P1.M2
profile26(26) - 70 Mbps
profile200(200) TS1 101 270-1 Pex.P2.M2
profile27(27) - 100 Mbps
Each value represents a target for the PME's Downstream
Payload Bitrate as seen at the MII. If the payload rate of
the selected profile cannot be achieved based on the loop
environment, bandplan and PSD mask, the PME initialization
SHALL fail. G.993.1 F.1.2.1 (VDSLoPOTS) x/D/U/D/U F
profile28(28) - G.993.1 F.1.2.2 (VDSLoTCM-ISDN)
profile29(29) - G.993.1 F.1.2.3 (PSD reduction)

This object maps to the aPayloadRateProfileDownstream aBandplanPSDMaskProfile attribute
in Clause 30."
REFERENCE
"[802.3ah] Annex 62A.3.6, 30.5.1.1.21"
::= { efmCuPme10PProfileEntry 7 }

efmCuPme10PProfileRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object controls creation/deletion of the associated
entry in efmCuPme10PProfileTable per the semantics of
RowStatus.
If an active entry is referenced via efmCuAdminProfile or
efmCuPmeAdminProfile, the entry MUST remain 'active' until
all references are removed." 62A, 30.5.1.1.22"
::= { efmCuPme10PProfileEntry 8 }

efmCuPme10PStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme10PStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table reflecting status of EFMCu 10PASS-TS PMEs (modems)."
::= { efmCuPme10P 2 3 }

efmCuPme10PStatusEntry

efmCuPme10PUPBOReferenceProfile OBJECT-TYPE
SYNTAX EfmCuPme10PStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the EFMCu 10PASS-TS PME Status table."
AUGMENTS { efmCuPmeStatusEntry }
::= { efmCuPme10PStatusTable 1 }

EfmCuPme10PStatusEntry ::=
SEQUENCE INTEGER {
efmCuPme10PFECCorrectedBlocks Counter32,
efmCuPme10PFECUncorrectedBlocks Counter32
profile1(1),
profile2(2),
profile3(3),
profile4(4),
profile5(5),
profile6(6),
profile7(7),
profile8(8),
profile9(9)
}
efmCuPme10PFECCorrectedBlocks OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only read-create
STATUS current
DESCRIPTION
"A count of received and corrected FEC codewords
"10PASS-TS PME Upstream Power Back-Off (UPBO) Reference PSD
Profile, as specified in 10PASS-TS
PME. 802.3ah Annex 62A. Possible values
are:
profile1(1) - T1.424/T-U Noise A M1
profile2(2) - T1.424/T-U Noise A M2
profile3(3) - T1.424/T-U Noise F M1
profile4(4) - T1.424/T-U Noise F M2
profile5(5) - ETSI TS 101 270-1 Noise A&B
profile6(6) - ETSI TS 101 270-1 Noise C
profile7(7) - ETSI TS 101 270-1 Noise D
profile8(8) - ETSI TS 101 270-1 Noise E
profile9(9) - ETSI TS 101 270-1 Noise F

This object maps to aPMEFECCorrectedBlocks the aUPBOReferenceProfile attribute
in
clause 30.

If a Clause 45 MDIO Interface to the PMA/PMD is present,
then this object maps to the 10P FEC correctable errors
register" 30."
REFERENCE
"[802.3ah] 45.2.1.22" Annex 62A.3.4, 30.5.1.1.23"
::= { efmCuPme10PStatusEntry efmCuPme10PProfileEntry 4 }

efmCuPme10PBandNotchProfiles OBJECT-TYPE
SYNTAX BITS {
profile0(0),
profile1(1),
profile2(2),
profile3(3),
profile4(4),
profile5(5),
profile6(6),
profile7(7),
profile8(8),
profile9(9),
profile10(10),
profile11(11)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"10PASS-TS PME Egress Control Band Notch Profile bitmap,
as specified in 802.3ah Annex 62A. Possible values are:
--------------+---------+----------+-----------+------+-----
Profile Name G.991.3 T1.424/T-U TS101 270-1 StartF EndF
Table Table Table (MHz) (MHz)
--------------+---------+----------+-----------+------+-----
profile0(0) - no profile
profile1(1) - F-5 #01 - - 1.810 1.825
profile2(2) - 6-2 15-1 17 1.810 2.000
profile3(3) - F-5 #02 - - 1.907 1.912
profile4(4) - F-5 #03 - - 3.500 3.575
profile5(5) - 6-2 - 17 3.500 3.800
profile6(6) - - 15-1 - 3.500 4.000
profile7(7) - F-5 #04 - - 3.747 3.754
profile8(8) - F-5 #05 - - 3.791 3.805
profile9(9) - 6-2 - 17 7.000 7.100
profile10(10) - F-5 #06 15-1 - 7.000 7.300
profile11(11) - 6-2 15-1 1 }

efmCuPme10PFECUncorrectedBlocks OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count 10.100 10.150

Any combination of received FEC codewords in 10PASS-TS PME, which are
uncorrectable. profiles can be specified by ORing
individual profiles, for example value of 0x0622 selects
profiles 2,6,10 and 11.

This object maps to aPMEFECUncorrectableBlocks the aBandNotchProfile attribute
in
clause 30.

If a Clause 45 MDIO Interface to the PMA/PMD is present,
then this object maps to the 10P FEC uncorrectable errors
register" 30."
REFERENCE
"[802.3ah] 45.2.1.23" Annex 62A.3.5, 30.5.1.1.19"
::= { efmCuPme10PStatusEntry 2 efmCuPme10PProfileEntry 5 }

-- ifAvailableStackTable for use in Discovery

ifAvailableStackTable

efmCuPme10PPayloadURateProfile OBJECT-TYPE
SYNTAX SEQUENCE OF IfAvailableStackEntry INTEGER {
profile5(5),
profile10(10),
profile15(15),
profile20(20),
profile25(25),
profile30(30),
profile50(50),
profile70(70),
profile100(100)
}
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
"This table, modeled after ifStackTable from IF-MIB,
contains information on the possible 'on-top-of'
relationships between the multiple sub-layers of network
interfaces (as opposed to actual relationships in
ifStackTable). In particular, it contains information on
which PCS ports (sublayers) can possibly run 'on top of'
which PMEs (sublayers),
"10PASS-TS PME Upstream Payload Rate Profile,
as determined by cross-connect
capability of the EFMCu device, where each sub-layer
corresponds to a conceptual row specified in the ifTable. For example,
when the PCS port with ifIndex value x can be connected
to run on top of the PME with ifIndex value y, then this table
contains:

ifAvailableStackStatus.x.y=capable

Note that there's always at least on PCS 802.3ah Annex 62A. Possible values are:
profile5(5) - 2.5 Mbps
profile10(10) - 5 Mbps
profile15(15) - 7.5 Mbps
profile20(20) - 10 Mbps
profile25(25) - 12.5 Mbps
profile30(30) - 15 Mbps
profile50(50) - 25 Mbps
profile70(70) - 35 Mbps
profile100(100) - 50 Mbps

Each value represents a target for each PME and the PME's Upstream Payload
Bitrate as seen at
least one PME for each PCS in the EFMCu devices, with
efmCuPAFCapacity and efmCuPeerPAFCapacity indicating
maximum number MII. If the payload rate of PMEs which can the
selected profile cannot be aggregated by local achieved based on the loop
environment, bandplan and
remote PCS port respectively. PSD mask, the PME initialization
SHALL fail.

This table is read only as it describes device capability" object maps to the aPayloadRateProfileUpstream
attribute in Clause 30."
REFERENCE
"IF-MIB, ifStackTable"
"[802.3ah] Annex 62A.3.6, 30.5.1.1.20"
::= { efmCuObjects 3 efmCuPme10PProfileEntry 6 }

ifAvailableStackEntry

efmCuPme10PPayloadDRateProfile OBJECT-TYPE
SYNTAX IfAvailableStackEntry INTEGER {
profile5(5),
profile10(10),
profile15(15),
profile20(20),
profile25(25),
profile30(30),
profile50(50),
profile70(70),
profile100(100),
profile140(140),
profile200(200)
}
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
"Information on
"10PASS-TS PME Downstream Payload Rate Profile,
as specified in 802.3ah Annex 62A. Possible values are:
profile5(5) - 2.5 Mbps
profile10(10) - 5 Mbps
profile15(15) - 7.5 Mbps
profile20(20) - 10 Mbps
profile25(25) - 12.5 Mbps
profile30(30) - 15 Mbps
profile50(50) - 25 Mbps
profile70(70) - 35 Mbps
profile100(100) - 50 Mbps
profile140(140) - 70 Mbps
profile200(200) - 100 Mbps

Each value represents a particular relationship between two
sub-layers, specifying that one sub-layer (PCS) runs on 'top' target for the PME's Downstream
Payload Bitrate as seen at the MII. If the payload rate of
the other sub-layer (PME). Each sub-layer corresponds to a
conceptual row in selected profile cannot be achieved based on the ifTable (interface index for PCS loop
environment, bandplan and PSD mask, the PME respectively)."
INDEX {
ifAvailableStackHigherLayer,
ifAvailableStackLowerLayer
}
::= { ifAvailableStackTable 1 }

IfAvailableStackEntry initialization
SHALL fail.

This object maps to the aPayloadRateProfileDownstream
attribute in Clause 30."
REFERENCE
"[802.3ah] Annex 62A.3.6, 30.5.1.1.21"
::=
SEQUENCE {
ifAvailableStackHigherLayer InterfaceIndex,
ifAvailableStackLowerLayer InterfaceIndex,
ifAvailableStackStatus INTEGER efmCuPme10PProfileEntry 7 }

ifAvailableStackHigherLayer

efmCuPme10PProfileRowStatus OBJECT-TYPE
SYNTAX InterfaceIndex RowStatus
MAX-ACCESS not-accessible read-create
STATUS current
DESCRIPTION
"The value of ifIndex corresponding to the higher sub-layer
"This object controls creation/deletion of the 'cross-connect capability' relationship, i.e., associated
entry in efmCuPme10PProfileTable per the
PCS sub-layer which MAY run on 'top' semantics of
RowStatus.
If an active entry is referenced via efmCuAdminProfile or
efmCuPmeAdminProfile, the PME sub-layer
identified by the corresponding instance of
ifAvailableStackLowerLayer." entry MUST remain 'active' until
all references are removed."
::= { ifAvailableStackEntry 1 efmCuPme10PProfileEntry 8 }

ifAvailableStackLowerLayer
efmCuPme10PStatusTable OBJECT-TYPE
SYNTAX InterfaceIndex SEQUENCE OF EfmCuPme10PStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The value of ifIndex corresponding to the lower sub-layer
of the 'cross-connect capability' relationship, i.e., the
PME sub-layer which MAY run 'below' the PCS sub-layer
identified by the corresponding instance
"Table reflecting status of
ifAvailableStackHigherLayer." EFMCu 10PASS-TS PMEs (modems)."
::= { ifAvailableStackEntry efmCuPme10P 2 }

ifAvailableStackStatus

efmCuPme10PStatusEntry OBJECT-TYPE
SYNTAX INTEGER EfmCuPme10PStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the EFMCu 10PASS-TS PME Status table."
AUGMENTS { efmCuPmeStatusEntry }
::= { efmCuPme10PStatusTable 1 }

EfmCuPme10PStatusEntry ::=
SEQUENCE {
capable(1),
outOfService(2)
efmCuPme10PFECCorrectedBlocks Counter32,
efmCuPme10PFECUncorrectedBlocks Counter32
}

efmCuPme10PFECCorrectedBlocks OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The status
"A count of the 'cross-connect capability' relationship
between two sub-layers. The following values are defined:
capable(1) - the PME sub-layer interface, identified by
the ifAvailableStackLowerLayer MAY be
connected received and corrected FEC codewords in 10PASS-TS
PME.

This object maps to aPMEFECCorrectedBlocks attribute in
clause 30.

If a Clause 45 MDIO Interface to run 'below' the PCS sub-layer
interface, identified by the
ifAvailableStackLowerLayer.
outOfService(2) - the PME sub-layer interface cannot be
connected due PMA/PMD is present,
then this object maps to unavailability of the
interface.

Note that PME availability per PCS, indicated by 'capable'
value, can be constrained by other parameters,
for example by aggregation capacity 10P FEC correctable errors
register

Discontinuities in the value of a PCS or this counter can occur at
re-initialization of the management system, and at other times
as indicated by the PME value of ifCounterDiscontinuityTime,
defined in
question being already connected to another PCS. So, IF-MIB."
REFERENCE
"[802.3ah] 45.2.1.22, 30.11.2.1.8"
::= { efmCuPme10PStatusEntry 1 }

efmCuPme10PFECUncorrectedBlocks OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of received FEC codewords in
order 10PASS-TS PME, which are
uncorrectable.

This object maps to ensure that aPMEFECUncorrectableBlocks attribute in
clause 30.

If a particular PME can be connected Clause 45 MDIO Interface to the
PCS, all respective parameters (e.g. ifAvailableStackTable,
ifStackTable and efmCuPAFCapacity) SHALL be inspected.

This object PMA/PMD is read only, unlike ifStackStatus, present,
then this object maps to the 10P FEC uncorrectable errors
register

Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as it
describes indicated by the device capability." value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE
"[802.3ah] 45.2.1.23, 30.11.2.1.9"
::= { ifAvailableStackEntry 3 efmCuPme10PStatusEntry 2 }

--
-- Conformance Statements
--

efmCuGroups OBJECT IDENTIFIER ::= { efmCuConformance 1 }

efmCuCompliances OBJECT IDENTIFIER ::= { efmCuConformance 2 }

-- Object Groups

efmCuBasicGroup OBJECT-GROUP
OBJECTS {
efmCuPAFSupported,
efmCuAdminProfile,
efmCuTargetDataRate,
efmCuTargetSnrMgn,
efmCuAdaptiveSpectra,
efmCuPortSide,
efmCuFltStatus
}
STATUS current
DESCRIPTION
"A collection of objects required for all of EFMCu ports."
::= { efmCuGroups 1 }

efmCuPAFGroup OBJECT-GROUP
OBJECTS {
efmCuPeerPAFSupported,
efmCuPAFCapacity,
efmCuPeerPAFCapacity,
efmCuPAFAdminState,
efmCuPAFDiscoveryCode,
efmCuPAFRemoteDiscoveryCode,
efmCuNumPMEs,
ifAvailableStackStatus
efmCuNumPMEs
}
STATUS current
DESCRIPTION
"A collection of objects required for OPTIONAL PME
Aggregation Function (PAF) and PAF discovery in EFMCu ports."
::= { efmCuGroups 2 }

ifStackCapabilityGroup OBJECT-GROUP
OBJECTS {
ifAvailableStackStatus
}
STATUS current
DESCRIPTION
"A collection of objects providing information on
the stacking capability of MIB-II interfaces."
::= { efmCuGroups 3 }

efmCuPAFErrorsGroup OBJECT-GROUP
OBJECTS {
efmCuPAFInErrors,
efmCuPAFInSmallFragments,
efmCuPAFInLargeFragments,
efmCuPAFInBadFragments,
efmCuPAFInLostFragments,
efmCuPAFInLostStarts,
efmCuPAFInLostEnds,
efmCuPAFInOverflows
}
STATUS current
DESCRIPTION
"A collection of objects supporting OPTIONAL error counters
of PAF on EFMCu ports."
::= { efmCuGroups 4 3 }

efmCuPmeGroup OBJECT-GROUP
OBJECTS {
efmCuPmeAdminProfile,
efmCuPmeOperStatus,
efmCuPmeFltStatus,
efmCuPmeSubTypesSupported,
efmCuPmeAdminSubType,
efmCuPmeOperSubType,
efmCuPAFRemoteDiscoveryCode,
efmCuPmeOperProfile,
efmCuPmeSnrMgn,
efmCuPmePeerSnrMgn,
efmCuPmeLineAtn,
efmCuPmePeerLineAtn,
efmCuPmeEquivalentLength,
efmCuPmeTCCodingErrors,
efmCuPmeTCCrcErrors,
efmCuPmeThreshLineAtn,
efmCuPmeThreshSnrMgn
}
STATUS current
DESCRIPTION
"A collection of objects providing information about
a 2BASE-TL/10PASS-TS PME."
::= { efmCuGroups 5 4 }

efmCuAlarmConfGroup OBJECT-GROUP
OBJECTS {
efmCuThreshLowRate,
efmCuLowRateCrossingEnable,
efmCuPmeThreshLineAtn,
efmCuPmeLineAtnCrossingEnable,
efmCuPmeThreshSnrMgn,
efmCuPmeSnrMgnCrossingEnable,
efmCuPmeDeviceFaultEnable,
efmCuPmeConfigInitFailEnable,
efmCuPmeProtocolInitFailEnable
}
STATUS current
DESCRIPTION
"A collection of objects required for configuration of alarm
thresholds and notifications in EFMCu ports."
::= { efmCuGroups 6 5 }

efmCuNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
efmCuLowRateCrossing,
efmCuPmeLineAtnCrossing,
efmCuPmeSnrMgnCrossing,
efmCuPmeDeviceFault,
efmCuPmeConfigInitFailure,
efmCuPmeProtocolInitFailure
-- efmCuPmeDeviceFault,
-- efmCuPmeLocalPowerLoss
}
STATUS current
DESCRIPTION
"This group supports notifications of significant conditions
associated with EFMCu ports."
::= { efmCuGroups 7 6 }

efmCuPme2BProfileGroup OBJECT-GROUP
OBJECTS {
efmCuPme2BProfileDescr,
efmCuPme2BRegion,
efmCuPme2BsMode,
efmCuPme2BMinDataRate,
efmCuPme2BMaxDataRate,
efmCuPme2BPower,
efmCuPme2BConstellation,
efmCuPme2BProfileRowStatus
efmCuPme2BProfileRowStatus,
efmCuPme2BsModeDescr,
efmCuPme2BsModeRowStatus,
efmCuPme2BEquivalentLength,
efmCuPme2BMaxDataRatePam16,
efmCuPme2BMaxDataRatePam32,
efmCuPme2BReachRateRowStatus
}
STATUS current
DESCRIPTION
"A collection of objects that constitute a configuration
profile for configuration of 2BASE-TL ports."
::= { efmCuGroups 8 } 7}

efmCuPme10PProfileGroup OBJECT-GROUP
OBJECTS {
efmCuPme10PProfileDescr,
efmCuPme10PBandplanPSDMskProfile,
efmCuPme10PUPBOReferenceProfile,
efmCuPme10PBandNotchProfiles,
efmCuPme10PPayloadURateProfile,
efmCuPme10PPayloadDRateProfile,
efmCuPme10PProfileRowStatus
}
STATUS current
DESCRIPTION
"A collection of objects that constitute a configuration
profile for configuration of 10PASS-TS ports."
::= { efmCuGroups 9 8 }

efmCuPme10PStatusGroup OBJECT-GROUP
OBJECTS {
efmCuPme10PFECCorrectedBlocks,
efmCuPme10PFECUncorrectedBlocks
}
STATUS current
DESCRIPTION
"A collection of objects providing status information
specific to 10PASS-TS PMEs."
::= { efmCuGroups 10 9 }

-- Compliance Statements
efmCuCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for 2BASE-TL/10PASS-TS interfaces.
Compliance with the following external compliance statements
is REQUIRED:

MIB Module Compliance Statement
---------- --------------------
IF-MIB ifCompliance3
IF-INVERTED-STACK-MIB ifInvCompliance
EtherLike-MIB dot3Compliance2
MAU-MIB mauModIfCompl3" mauModIfCompl3

Compliance with the following external compliance statements
is OPTIONAL for implementations supporting PME Aggregation
Function (PAF) with flexible cross-connect between the PCS
and PME ports:

MIB Module Compliance Statement
---------- --------------------
IF-INVERTED-STACK-MIB ifInvCompliance
IF-CAP-STACK-MIB ifCapStackCompliance"

MODULE -- this module
MANDATORY-GROUPS {
efmCuBasicGroup,
efmCuPmeGroup,
efmCuAlarmConfGroup,
efmCuNotificationGroup
}

GROUP efmCuPme2BProfileGroup
DESCRIPTION
"Support for this group is only required for implementations
supporting 2BASE-TL Phy."

GROUP efmCuPme10PProfileGroup
DESCRIPTION
"Support for this group is only required for implementations
supporting 10PASS-TS Phy."

GROUP efmCuPAFGroup
DESCRIPTION
"Support for this group is only required for
implementations supporting PME Aggregation Function (PAF)."

GROUP ifStackCapabilityGroup
DESCRIPTION
"Support for this group is OPTIONAL for implementations
supporting layered interfaces architecture with
flexible cross-connect between the layers."

GROUP efmCuPAFErrorsGroup
DESCRIPTION
"Support for this group is OPTIONAL for implementations
supporting PME Aggregation Function (PAF)."

GROUP efmCuPme10PStatusGroup
DESCRIPTION
"Support for this group is OPTIONAL for implementations
supporting 10PASS-TS Phy."

OBJECT efmCuPmeSubTypesSupported
SYNTAX BITS {
ieee2BaseTLO(0),
ieee2BaseTLR(1),
ieee10PassTSO(2),
ieee10PassTSR(3)
}
DESCRIPTION
"Support for all subtypes is not required. However at least
one value SHALL be supported"

OBJECT efmCuPmeAdminSubType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required (needed only for PMEs
supporting more than a single subtype, e.g.
ieee2BaseTLO and ieee2BaseTSR or ieee2BaseTLR and
ieee10PassTSR)"

OBJECT efmCuTargetSnrMgn
MIN-ACCESS read-only
DESCRIPTION
"Write access is OPTIONAL. For PHYs without write access
the target SNR margin SHALL be fixed at 5dB for 2BASE-TL
and 6dB for 10PASS-TS."

OBJECT efmCuAdaptiveSpectra
MIN-ACCESS read-only
DESCRIPTION
"Write access is OPTIONAL. For PHYs without write access
the default value SHOULD be false."

::= { efmCuCompliances 1 }
END

7. Security Considerations

There is a number of managed objects defined in this MIB the EFM-CU-MIB module
that have a MAX-ACCESS clause of read-write or read-create. Most
objects are writeable only when the link is Down. Writing to these
objects can have potentially disruptive effects on network operation,
for example:

o Changing of efmCuPmeAdminSubType MAY lead to a potential locking
of the link, as peer PMEs of the same sub-type cannot exchange
handshake messages.

o Changing of efmCuPAFAdminState to enabled MAY lead to a potential
locking of the link, if the peer Phy does not support PAF.

o Changing of efmCuPAFDiscoveryCode, before the discovery operation,
MAY lead to a wrongful discovery, for example when two -O ports
are connected to the same multi-PME -R port and both -O ports have
the same Discovery register value.

o Changing PCS or PME configuration parameters (e.g. profile of a
PCS or PME via efmCuAdminProfile or efmCuPmeAdminProfile) MAY lead
to anything from link quality and rate degradation to a complete
link initialization failure, as ability of an EFMCu port to
support a particular configuration depends on the copper
environment.

o Activation of a PME can cause a severe degradation of service for
another EFMCu Phy, whose PME(s) MAY be affected by the cross-talk
from the newly activated PME.

o Removal of a PME from an operationally 'up' EFMCu port,
aggregating several PMEs, MAY cause port's rate degradation

The user of this MIB the EFM-CU-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.

The readable objects in this MIB the EFM-CU-MIB module (i.e., those with MAX-ACCESS 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 particular since EFMCu can be carried over
Unshielded Twisted Pair (UTP) voice grade copper in a bundle with
other pairs belonging to another operator/customer, it is
theoretically possible to evasdrop to an EFMCu transmission simply by
"listening" to a cross-talk from an EFMCu pair, especially if the
parameters of the EFMCu link in question are known. 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 these MIB module. modules.

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 these MIB module modules 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.

8. IANA Considerations

The two new values of dot3MauType (dot3MauType2BaseTL and
dot3MauType10PassTS) and corresponding IANAifMauTypeListBits bit
definitions (b2BaseTL and b10PassTS), as well as the new values for
IANAifMauMediaAvailable (availableReduced and ready) SHALL be defined
by the IANA in the IANA-MAU-MIB module (see [I-D.ietf-hubmib-
rfc3636bis]) before this document is published as an RFC.

9. Acknowledgments

This document was produced by the IETF Ethernet Interfaces and Hub
MIB Working Group, whose efforts were greatly advanced by the
contributions of the following people (in alphabetical order):

Dan Romascanu

Marina Popilov

Mathias Riess

Matt Squire
Mike Heard

Udi Ashkenazi

10. References

9.1.

10.1. Normative References

[802.3] IEEE, "IEEE Standard for 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", IEEE Std 802.3-2005, December 2005.

[802.3ah] IEEE, "IEEE Standard for 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 - Amendment: Media Access Control
Parameters, Physical Layers and Management Parameters for
Subscriber Access Networks", IEEE Std 802.3ah-2004,
September 2004.

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.

[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58,
RFC 2578, April 1999.

[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M., and S. Waldbusser, "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.

[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.

9.2.

10.2. Informative References

[ANFP] Network Interoperability Consultative Committee (NICC),
"Specification of the Access Network Frequency Plan (ANFP)
applicable to transmission systems used on the BT Access
Network", NICC Document ND1602:2005/08, August 2005.

[G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber Line
(SHDSL) transceivers", ITU-T Recommendation G.991.2,
December 2003.

[G.993.1] ITU-T, "Very High speed Digital Subscriber Line
transceivers", ITU-T Recommendation G.993.1, June 2004.

[I-D.ietf-hubmib-efm-epon-mib]
Khermosh, L., "Managed Objects of EPON",
draft-ietf-hubmib-efm-epon-mib-04
draft-ietf-hubmib-efm-epon-mib-05 (work in progress),
February
July 2006.

[I-D.ietf-hubmib-efm-mib]
Squire, M., "Definitions and Managed Objects for OAM
Functions on Ethernet Like Interfaces",
draft-ietf-hubmib-efm-mib-04 (work in progress),
March 2006.

[I-D.ietf-hubmib-rfc3636bis]
Beili, E., "Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs)",
draft-ietf-hubmib-rfc3636bis-03
draft-ietf-hubmib-rfc3636bis-05 (work in progress),
June
July 2006.

[IANAifType-MIB]
Internet Assigned Numbers Authority (IANA), "IANAifType
Textual Convention definition",
http://www.iana.org/assignments/ianaiftype-mib.

[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.

[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.

[RFC4319] Sikes, C., Ray, B., and R. Abbi, "Definitions of Managed
Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and
Single-Pair High-Speed Digital Subscriber Line (SHDSL)
Lines", RFC 4319, December 2005.

Author's Address

Edward Beili
Actelis Networks
Bazel 25
Petach-Tikva
Israel

Phone: +972-3-924-3491
Email: edward.beili@actelis.com

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 (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.