draft-ietf-hubmib-efm-cu-mib-07.txt   draft-ietf-hubmib-efm-cu-mib-08.txt 
Network Working Group E. Beili Network Working Group E. Beili
Internet-Draft Actelis Networks Internet-Draft Actelis Networks
Intended status: Standards Track February 21, 2007 Intended status: Standards Track July 29, 2007
Expires: August 25, 2007 Expires: January 30, 2008
Ethernet in the First Mile Copper (EFMCu) Interfaces MIB Ethernet in the First Mile Copper (EFMCu) Interfaces MIB
draft-ietf-hubmib-efm-cu-mib-07.txt draft-ietf-hubmib-efm-cu-mib-08.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 34 skipping to change at page 1, line 34
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 25, 2007. This Internet-Draft will expire on January 30, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document defines Management Information Base (MIB) modules for This document defines Management Information Base (MIB) modules for
use with network management protocols in TCP/IP based internets. use with network management protocols in TCP/IP based internets.
This document describes extensions to the Ethernet-like Interfaces This document describes extensions to the Ethernet-like Interfaces
MIB and MAU MIB modules with a set of objects for managing Ethernet MIB and MAU MIB modules with a set of objects for managing Ethernet
in the First Mile Copper (EFMCu) interfaces 10PASS-TS and 2BASE-TL, 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 in IEEE Std 802.3ah-2004 (note: IEEE Std 802.3ah-2004 has
defined, describing cross-connect capability of a managed device with been integrated into IEEE Std 802.3-2005). In addition a set of
multi-layer (stacked) interfaces, extending the stack management objects is defined, describing cross-connect capability of a managed
objects in the Interfaces Group MIB and the Inverted Stack Table MIB device with multi-layer (stacked) interfaces, extending the stack
modules. management objects in the Interfaces Group MIB and the Inverted Stack
Table MIB modules.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Relation to other MIB modules . . . . . . . . . . . . . . . . 4 3. Relation to other MIB modules . . . . . . . . . . . . . . . . 4
3.1. Relation to Interfaces Group MIB module . . . . . . . . . 4 3.1. Relation to Interfaces Group MIB module . . . . . . . . . 4
3.1.1. Layering Model . . . . . . . . . . . . . . . . . . . . 4 3.1.1. Layering Model . . . . . . . . . . . . . . . . . . . . 4
3.1.2. PME Aggregation Function (PAF) . . . . . . . . . . . . 7 3.1.2. PME Aggregation Function (PAF) . . . . . . . . . . . . 7
3.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 7 3.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 7
skipping to change at page 2, line 31 skipping to change at page 2, line 32
4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 13 4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1. EFM Copper MIB Overview . . . . . . . . . . . . . . . . . 13 4.1. EFM Copper MIB Overview . . . . . . . . . . . . . . . . . 13
4.2. Interface stack capability MIB Overview . . . . . . . . . 13 4.2. Interface stack capability MIB Overview . . . . . . . . . 13
4.3. PME Profiles . . . . . . . . . . . . . . . . . . . . . . . 13 4.3. PME Profiles . . . . . . . . . . . . . . . . . . . . . . . 13
4.4. Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 14 4.4. Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 14
5. Interface Stack Capability MIB Definitions . . . . . . . . . . 16 5. Interface Stack Capability MIB Definitions . . . . . . . . . . 16
6. EFM Copper MIB Definitions . . . . . . . . . . . . . . . . . . 22 6. EFM Copper MIB Definitions . . . . . . . . . . . . . . . . . . 22
7. Security Considerations . . . . . . . . . . . . . . . . . . . 84 7. Security Considerations . . . . . . . . . . . . . . . . . . . 84
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 86 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 86
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 86 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 86
10. Notes to RFC Editor . . . . . . . . . . . . . . . . . . . . . 86 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 87
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 87 10.1. Normative References . . . . . . . . . . . . . . . . . . . 87
11.1. Normative References . . . . . . . . . . . . . . . . . . . 87 10.2. Informative References . . . . . . . . . . . . . . . . . . 88
11.2. Informative References . . . . . . . . . . . . . . . . . . 88
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 89 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 89
Intellectual Property and Copyright Statements . . . . . . . . . . 90 Intellectual Property and Copyright Statements . . . . . . . . . . 90
1. Introduction 1. Introduction
New Ethernet-like interfaces have been defined in the Institute of New Ethernet-like interfaces have been defined in the Institute of
Electrical and Electronics Engineers (IEEE) Standard 802.3ah-2004 Electrical and Electronics Engineers (IEEE) Standard 802.3ah-2004
[802.3ah], a.k.a. Ethernet in the First Mile (EFM), which is now a [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 part of the base IEEE Standard 802.3-2005 [802.3]. In particular
2BASE-TL and 10PASS-TS physical interfaces (PHYs), defined over 2BASE-TL and 10PASS-TS physical interfaces (PHYs), defined over
voice-grade copper pairs, have been specified for the long and short voice-grade copper pairs, have been specified for the long and short
reach respectively. These interfaces, collectively called EFM Copper reach respectively. These interfaces, collectively called EFM Copper
(EFMCu), are based on Single-pair High-speed Digital Subscriber Line (EFMCu), are based on Single-pair High-speed Digital Subscriber Line
(SHDSL) [G.991.2] and Very High speed Digital Subscriber Line (VDSL) (SHDSL) [G.991.2] and Very High speed Digital Subscriber Line (VDSL)
[G.993.1] technology, supporting optional Physical Medium Entity [G.993.1] technology, supporting optional Physical Medium Entity
(PME) aggregation (a.k.a. multi-pair bonding) with variable rates. (PME) aggregation (a.k.a. multi-pair bonding) with variable rates.
2BASE-TL PHY is capable of providing at least 2Mbps over 2700 m long 2BASE-TL PHY is capable of providing at least 2Mbps over a 2700 m
single copper pair with a mean Bit Error Rate (BER) of 10^-7 (using long single copper pair with a mean Bit Error Rate (BER) of 10^-7
5dB target noise margin). (using 5dB target noise margin).
10PASS-TS PHY is capable of providing at least 10Mbps over 750 m long 10PASS-TS PHY is capable of providing at least 10Mbps over a 750 m
single copper pair with a mean BER of 10^-7 (using 6dB target noise long single copper pair with a mean BER of 10^-7 (using 6dB target
margin). noise margin).
This memo defines a Management Information Base (MIB) module for use This memo defines a Management Information Base (MIB) module for use
with network management protocols in the Internet community to manage with network management protocols in the Internet community to manage
EFMCu interfaces. In addition a MIB module is defined describing EFMCu interfaces. In addition a MIB module is defined describing the
cross-connect capability of a stacked interface. cross-connect capability of a stacked interface.
Note that managed objects for Operation, Administration and Note that managed objects for Operation, Administration and
Management (OAM) and Ethernet over Passive Optical Networks (EPON) Management (OAM) and Ethernet over Passive Optical Networks (EPON)
clauses of IEEE 802.3ah are defined in EFM-COMMON-MIB clauses of IEEE 802.3ah are defined in EFM-COMMON-MIB [RFC4878] and
[I-D.ietf-hubmib-efm-mib] and EFM-EPON-MIB EFM-EPON-MIB [RFC4837] respectively.
[I-D.ietf-hubmib-efm-epon-mib] respectively.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 4, line 13 skipping to change at page 4, line 13
2580 [RFC2580]. 2580 [RFC2580].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. Relation to other MIB modules 3. Relation to other MIB modules
This section outlines the relationship of the MIB modules defined in This section outlines the relationship of the MIB modules defined in
this document with other MIB modules described in the relevant RFCs. this document with other MIB modules described in the relevant RFCs.
Specifically, Interfaces Group MIB (IF-MIB), Ethernet-Like Specifically, the Interfaces Group MIB (IF-MIB), Ethernet-Like
(EtherLike-MIB), MAU (MAU-MIB), SHDSL (HDSL2-SHDSL-LINE-MIB) and VDSL (EtherLike-MIB), MAU (MAU-MIB), SHDSL (HDSL2-SHDSL-LINE-MIB) and VDSL
(VDSL-LINE-EXT-MCM-MIB) are discussed. (VDSL-LINE-EXT-MCM-MIB) modules are discussed.
3.1. Relation to Interfaces Group MIB module 3.1. Relation to Interfaces Group MIB module
2BASE-TL and 10PASS-TS PHY's specified in the EFM-CU-MIB module are 2BASE-TL and 10PASS-TS PHY's specified in the EFM-CU-MIB module are
stacked (a.k.a. aggregated or bonded) Ethernet interfaces and as such stacked (a.k.a. aggregated or bonded) Ethernet interfaces and as such
are managed using generic interface management objects defined in the are managed using generic interface management objects defined in the
IF-MIB [RFC2863]. IF-MIB [RFC2863].
The stack management, i.e. actual connection of the sub-layers to the The stack management, i.e. actual connection of the sub-layers to the
top layer interface, is done via the ifStackTable, as defined in the top layer interface, is done via the ifStackTable, as defined in the
skipping to change at page 4, line 42 skipping to change at page 4, line 42
connect capability, when a flexible cross-connect matrix is present connect capability, when a flexible cross-connect matrix is present
between the interface layers. between the interface layers.
3.1.1. Layering Model 3.1.1. Layering Model
An EFMCu interface can aggregate up to 32 Physical Medium Entity An EFMCu interface can aggregate up to 32 Physical Medium Entity
(PME) sub-layer devices (modems), using so called PME Aggregation (PME) sub-layer devices (modems), using so called PME Aggregation
Function (PAF). Function (PAF).
A generic EFMCu device can have a number of Physical Coding Sublayer A generic EFMCu device can have a number of Physical Coding Sublayer
(PCS) ports, each connected to a MAC via Medium Independent Interface (PCS) ports, each connected to a MAC via a Medium Independent
(MII) at the upper layer, and cross-connected to a number of Interface (MII) at the upper layer, and cross-connected to a number
underlying PMEs, with a single PCS per PME relationship, see clause of underlying PMEs, with a single PCS per PME relationship, see
61.1 of [802.3ah] for more details. clause 61.1 of [802.3ah] for more details.
Each PME in the aggregated EFMCu port is represented in the Interface Each PME in the aggregated EFMCu port is represented in the Interface
table (ifTable) as a separate interface with ifType of shdsl(169) for table (ifTable) as a separate interface with ifType of shdsl(169) for
2BASE-TL or vdsl(97) for 10PASS-TS. The ifType values are defined in 2BASE-TL or vdsl(97) for 10PASS-TS. The ifType values are defined in
[IANAifType-MIB]. [IANAifType-MIB].
ifSpeed for each PME SHALL return the actual data bitrate of the ifSpeed for each PME SHALL return the actual data bitrate of the
active PME (e.g. for 2BaseTL PMEs it is a multiple of 64Kbps). Zero active PME (e.g. for 2BaseTL PMEs it is a multiple of 64Kbps). A
value SHALL be returned when PME is initializing or down. zero value SHALL be returned when the PME is initializing or down.
The ifSpeed of the PCS is the sum of the current operating data rates The ifSpeed of the PCS is the sum of the current operating data rates
of all PMEs in the aggregation group, without the 64/65B of all PMEs in the aggregation group, without the 64/65B
encapsulation overhead and PAF overhead, but accounting for the encapsulation overhead and PAF overhead, but accounting for the
Inter-Frame Gaps (IFG). Inter-Frame Gaps (IFG).
When using the stated definition of ifSpeed for the PCS, there would When using the stated definition of ifSpeed for the PCS, there would
be no frame loss in the following configuration (the test-sets are be no frame loss in the following configuration (the test-sets are
configured to generate 100% of back to back traffic, i.e. minimal configured to generate 100% of back to back traffic, i.e. minimal
IFG, at 10 or 100Mbps, with min and max frame sizes; the EFM IFG, at 10 or 100Mbps, with min and max frame sizes; the EFM
skipping to change at page 6, line 44 skipping to change at page 6, line 44
application). The ifInvStackTable, being an inverted version of the application). The ifInvStackTable, being an inverted version of the
ifStackTable, provides an efficient means for a Network Management ifStackTable, provides an efficient means for a Network Management
application to read a subset of the ifStackTable and thereby application to read a subset of the ifStackTable and thereby
determine which PCS runs on top of a particular PME. determine which PCS runs on top of a particular PME.
A new table ifCapStackTable defined in the IF-CAP-STACK-MIB module, A new table ifCapStackTable defined in the IF-CAP-STACK-MIB module,
specifies for each higher-layer interface (e.g. PCS port) a list of specifies for each higher-layer interface (e.g. PCS port) a list of
lower-layer interfaces (e.g. PMEs), which can possibly be cross- lower-layer interfaces (e.g. PMEs), which can possibly be cross-
connected to that higher-layer interface, determined by the cross- connected to that higher-layer interface, determined by the cross-
connect capability of the device. This table, modeled after connect capability of the device. This table, modeled after
ifStackTable, is read only, reflecting current cross-connect ifStackTable, is read-only, reflecting current cross-connect
capability of a stacked interface, which can be dynamic in some capability of a stacked interface, which can be dynamic in some
implementations (e.g. if PMEs are located on a pluggable module and implementations (e.g. if PMEs are located on a pluggable module and
the module is pulled out). Note that PME availability per PCS, the module is pulled out). Note that PME availability per PCS,
described by ifCapStackTable, can be constrained by other parameters, described by ifCapStackTable, can be constrained by other parameters,
for example by aggregation capacity of a PCS or by the PME in for example by aggregation capacity of a PCS or by the PME in
question being already connected to another PCS. So, in order to question being already connected to another PCS. So, in order to
ensure that a particular PME can be connected to the PCS, all ensure that a particular PME can be connected to the PCS, all
respective parameters (e.g. ifCapStackTable, ifStackTable and respective parameters (e.g. ifCapStackTable, ifStackTable and
efmCuPAFCapacity) SHALL be inspected. efmCuPAFCapacity) SHALL be inspected.
The ifInvCapStackTable, also defined in the IF-CAP-STACK-MIB module, The ifInvCapStackTable, also defined in the IF-CAP-STACK-MIB module,
describes which higher-layer interfaces (e.g. PCS ports) can describes which higher-layer interfaces (e.g. PCS ports) can
possibly be connected to a particular lower-layer interface (e.g. possibly be connected to a particular lower-layer interface (e.g.
PME), providing inverted mapping of ifCapStackTable. While it PME), providing an inverted mapping of the ifCapStackTable. While it
contains no additional information beyond that already contained in contains no additional information beyond that already contained in
the ifCapStackTable, the ifInvCapStackTable has the ifIndex values in the ifCapStackTable, the ifInvCapStackTable has the ifIndex values in
its INDEX clause in the reverse order, i.e., the lower-layer its INDEX clause in the reverse order, i.e., the lower-layer
interface first, and the higher-layer interface second, providing an interface first, and the higher-layer interface second, providing an
efficient means for a Network Management application to read a subset efficient means for a Network Management application to read a subset
of the ifCapStackTable and thereby determine which interfaces can be of the ifCapStackTable and thereby determine which interfaces can be
connected to run on top of a particular interface. connected to run on top of a particular interface.
3.1.2. PME Aggregation Function (PAF) 3.1.2. PME Aggregation Function (PAF)
The PME Aggregation Function (PAF) allows a number of PMEs to be The PME Aggregation Function (PAF) allows a number of PMEs to be
aggregated onto a PCS port, by fragmenting the Ethernet frames, aggregated onto a PCS port, by fragmenting the Ethernet frames,
transmitting the fragments over multiple PMEs and assembling the transmitting the fragments over multiple PMEs and assembling the
original frames at the remote port. PAF is OPTIONAL, meaning that a original frames at the remote port. PAF is OPTIONAL, meaning that a
device with a single PME MAY perform fragmentation and re-assembly if device with a single PME MAY perform fragmentation and re-assembly if
this function is supported by the device. Note however that the this function is supported by the device. Note however that the
agent is REQUIRED to report on the PAF capability for all EFMCu ports agent is REQUIRED to report on the PAF capability for all EFMCu ports
(2BASE-TL and 10PASS-TS). (2BASE-TL and 10PASS-TS).
The EFM-CU-MIB module allows a Network Management application to The EFM-CU-MIB module allows a Network Management application to
query PAF capability and enable/disable it if supported. Note that query the PAF capability and enable/disable it if supported. Note
enabling PAF effectively turns on fragmentation and re-assembly, even that enabling PAF effectively turns on fragmentation and re-assembly,
on a single-PME port. even on a single-PME port.
3.1.3. Discovery Operation 3.1.3. Discovery Operation
The EFMCu ports may optionally support discovery operation, whereby The EFMCu ports may optionally support discovery operation, whereby
PMEs, during initialization, exchange information about their PMEs, during initialization, exchange information about their
respective aggregation groups (PCS). This information can then be respective aggregation groups (PCS). This information can then be
used to detect copper misconnections or for an automatic assignment used to detect copper misconnections or for an automatic assignment
of the local PMEs into aggregation groups instead of a fixed pre- of the local PMEs into aggregation groups instead of a fixed pre-
configuration. configuration.
The MIB modules defined in this document allow a Network Management The MIB modules defined in this document allow a Network Management
application to control EFM Discovery mechanism and query its results. application to control the EFM Discovery mechanism and query its
Note that the Discovery mechanism can work only if PAF is supported results. Note that the Discovery mechanism can work only if PAF is
and enabled. supported and enabled.
Two tables are used by the EFM Discovery mechanism: ifStackTable and Two tables are used by the EFM Discovery mechanism: ifStackTable and
ifCapStackTable. The following pseudo-code gives an example of the ifCapStackTable. The following pseudo-code gives an example of the
Discovery and automatic PME assignment for a generic PAF enabled Discovery and automatic PME assignment for a generic PAF enabled
multi-PCS EFMCu device, located at Central Office (CO), using objects multi-PCS EFMCu device, located at Central Office (CO), using objects
defined in these MIB modules and in IF-MIB [Note that automatic PME defined in these MIB modules and in the IF-MIB [Note that automatic
assignment is only shown here for the purposes of the example. Fixed PME assignment is only shown here for the purposes of the example.
PME pre-assignment, manual assignment or auto-assignment using an Fixed PME pre-assignment, manual assignment or auto-assignment using
alternative internal algorithm may be chosen by a particular an alternative internal algorithm may be chosen by a particular
implementation]: implementation]:
// Go over all PCS ports in the CO device // Go over all PCS ports in the CO device
FOREACH pcs[i] IN CO_device FOREACH pcs[i] IN CO_device
{ // Perform discovery and auto-assignment only on PAF enabled ports { // Perform discovery and auto-assignment only on PAF enabled ports
// with room for more PMEs // with room for more PMEs
IF ( pcs[i].PAFSupported AND pcs[i].NumPMEs < pcs[i].PAFCapacity ) IF ( pcs[i].PAFSupported AND pcs[i].NumPMEs < pcs[i].PAFCapacity )
{ dc = pcs[i].DiscoveryCode = MAC[i]; // unique 6-octets per PCS { // Assign a unique 6-octets local discovery code to the PCS
// e.g. MAC address
dc = pcs[i].DiscoveryCode = MAC[i];
// Go over all disconnected PMEs, which can // Go over all disconnected PMEs, which can
// potentially be connected to the PCS // potentially be connected to the PCS
FOREACH pme[j] IN ifCapStackTable[pcs[i]] AND FOREACH pme[j] IN ifCapStackTable[pcs[i]] AND
NOT ifInvStackTable[pme[j]] // not connected NOT IN ifStackTable[pcs[i]] // not connected
{ // Try to grab the remote RT_device, by writing the value { // Try to grab the remote RT_device, by writing the value
// of the local 6-octet discovery code to the remote // of the local 6-octet discovery code to the remote
// discovery code register (via handshake mechanism). // discovery code register (via handshake mechanism).
// This operation is atomic Set-if-Clear action, i.e. it // This operation is atomic Set-if-Clear action, i.e. it
// would succeed only if the remote discovery register was // would succeed only if the remote discovery register was
// zero. Read the remote discovery code register via Get // zero. Read the remote discovery code register via Get
// operation to see if the RT_device, attached via the PME // operation to see if the RT_device, attached via the PME
// is indeed marked as being the CO_device peer. // is indeed marked as being the CO_device peer.
pme[j].RemoteDiscoveryCode = dc; // Set-if-Clear pme[j].RemoteDiscoveryCode = dc; // Set-if-Clear
r = pme[j].RemoteDiscoveryCode; // Get r = pme[j].RemoteDiscoveryCode; // Get
IF ( r == dc AND pcs[i].NumPMEs < pcs[i].PAFCapacity) IF ( r == dc AND pcs[i].NumPMEs < pcs[i].PAFCapacity)
{ // Remote RT_device connected via PME[j] is/was a peer { // Remote RT_device connected via PME[j] is/was a peer
// for PCS[i] and there is room for another PME in the // for PCS[i] and there is room for another PME in the
// PCS[i] aggregation group (max. PAF capacity is not // PCS[i] aggregation group (max. PAF capacity is not
// reached yet). // reached yet).
// Connect this PME to the PCS (via ifStackTable, // Connect this PME to the PCS (via ifStackTable,
// ifInvStackTable being inverse of ifStackTable is // ifInvStackTable being inverse of ifStackTable is
// updated automatically) // updated automatically, i.e. pcs[i] is auto-added
// to ifInvStackTable[pme[j]])
ADD pme[j] TO ifStackTable[pcs[i]]; ADD pme[j] TO ifStackTable[pcs[i]];
// pcs[i] is auto-added to ifInvStackTable[pme[j]]
pcs[i].NumPMEs = pcs[i].NumPMEs + 1; pcs[i].NumPMEs = pcs[i].NumPMEs + 1;
// Discover all other disconnected PMEs, // Discover all other disconnected PMEs,
// attached to the same RT_device and connect them to // attached to the same RT_device and connect them to
// the PCS provided there is enough room for more PMEs. // the PCS provided there is enough room for more PMEs.
FOREACH pme[k] IN ifCapStackTable[pcs[i]] and FOREACH pme[k] IN ifCapStackTable[pcs[i]] AND
NOT ifInvStackTable[pme[k]] NOT IN ifStackTable[pcs[i]]
{ r = pme[k].RemoteDiscoveryCode; // Get { // Get Remote Discovery Code from the PME to see if
IF ( r == dc AND // it belongs to a connected RT_device "grabbed" by
pcs[i].NumPMEs < pcs[i].PAFCapacity) // the CO_device.
{ ADD pme[k] TO ifStackTable[pcs[i]];
// pcs[i] is added TO ifInvStackTable[pme[k]] r = pme[k].RemoteDiscoveryCode;
IF ( r == dc AND pcs[i].NumPMEs < pcs[i].PAFCapacity)
{ // Physically connect the PME to the PCS
// (pcs[i] is auto-added TO ifInvStackTable[pme[k]])
ADD pme[k] TO ifStackTable[pcs[i]];
pcs[i].NumPMEs = pcs[i].NumPMEs + 1; pcs[i].NumPMEs = pcs[i].NumPMEs + 1;
} }
} }
} }
// At this point we have discovered all local PMEs which // At this point we have discovered all local PMEs which
// are physically connected to the same remote RT_device // are physically connected to the same remote RT_device
// and connected them to PCS[i]. Go to the next PCS. // and connected them to PCS[i]. Go to the next PCS.
BREAK; BREAK;
} }
} }
} }
An SNMP Agent for a EFMCu device builds ifCapStackTable and its An SNMP Agent for an EFMCu device builds the ifCapStackTable and its
inverse ifInvCapStackTable according to the information contained in inverse ifInvCapStackTable according to the information contained in
the Clause 45 PME_Available_register (see [802.3ah] 61.1.5.3 and the Clause 45 PME_Available_register (see [802.3ah] 61.1.5.3 and
45.2.3.20). 45.2.3.20).
Adding a PME to the ifStackTable row for a specific PCS, involves 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 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 modifying Clause 45 PME_Aggregate_register (see [802.3ah] 61.1.5.3
and 45.2.3.21). and 45.2.3.21).
Note that PCS port does not have to be operationally 'down' for the Note that the PCS port does not have to be operationally 'down' for
connection to succeed. In fact, a dynamic PME addition (and removal) the connection to succeed. In fact, a dynamic PME addition (and
MAY be implemented with an available PME being initialized first (by removal) MAY be implemented with an available PME being initialized
setting its ifAdminStatus to 'up') and then added to an operationally first (by setting its ifAdminStatus to 'up') and then added to an
'up' PCS port, by modifying a respective ifStackTable (and respective operationally 'up' PCS port, by modifying a respective ifStackTable
ifInvStackTable) entry. (and respective ifInvStackTable) entry.
It is RECOMMENDED that a removal of the last operationally 'up' PME It is RECOMMENDED that a removal of the last operationally 'up' PME
from an operationally 'up' PCS would be rejected by the from an operationally 'up' PCS would be rejected by the
implementation, as this action would completely drop the link. implementation, as this action would completely drop the link.
3.1.4. EFMCu ports initialization 3.1.4. EFMCu ports initialization
EFMCu ports being built on top of xDSL technology, require a lengthy EFMCu ports being built on top of xDSL technology, require a lengthy
initialization or 'training' process, before any data can pass. initialization or 'training' process, before any data can pass.
During this initialization both ends of a link (peers) work During this initialization both ends of a link (peers) work
cooperatively to achieve required data rate on a particular copper cooperatively to achieve the required data rate on a particular
pair. Sometimes, when the copper line is too long or the noise on copper pair. Sometimes, when the copper line is too long or the
the line is too high, that 'training' process may fail to achieve a noise on the line is too high, that 'training' process may fail to
specific target rate with required characteristics. achieve a specific target rate with required characteristics.
The ifAdminStatus object from the IF-MIB, controls the desired state The ifAdminStatus object from the IF-MIB controls the desired state
of a PCS with all the PMEs connected to it or of an individual PME 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 port. Setting this object to 'up' instructs a particular PCS or PME
to start initialization process, which may take tens of seconds for to start the initialization process, which may take tens of seconds
EFMCu ports, especially if PAF is involved. The ifOperStatus object for EFMCu ports, especially if PAF is involved. The ifOperStatus
shows the operational state of an interface (extended by object shows the operational state of an interface (extended by the
ifMauMediaAvailable object from MAU-MIB for PCS and ifMauMediaAvailable object from MAU-MIB for PCS and
efmCuPmeOperStatus defined in the EFM-CU-MIB module for PME efmCuPmeOperStatus defined in the EFM-CU-MIB module for PME
interfaces). interfaces).
A disconnected PME may be initialized by changing the ifAdminState A disconnected PME may be initialized by changing the ifAdminState
from 'down' to 'up'. Changing the ifAdminState to 'up' on the PCS from 'down' to 'up'. Changing the ifAdminState to 'up' on the PCS
initializes all PMEs connected to that particular PCS. Note that in initializes all PMEs connected to that particular PCS. Note that in
case of PAF some interfaces may fail to initialize while others case of PAF some interfaces may fail to initialize while others
succeed. The PCS is considered operationally 'up' if at least one succeed. The PCS is considered operationally 'up' if at least one
PME aggregated by its PAF is operationally 'up'. When all PMEs PME aggregated by its PAF is operationally 'up'. When all PMEs
skipping to change at page 10, line 47 skipping to change at page 11, line 4
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
| IF-MIB object | EFMCu interpretation | | IF-MIB object | EFMCu interpretation |
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
| ifIndex | Interface index. Note that each PME and each PCS | | ifIndex | Interface index. Note that each PME and each PCS |
| | in the EFMCu PHY MUST have a unique index, as | | | in the EFMCu PHY MUST have a unique index, as |
| | there are some PCS and PME specific attributes | | | there are some PCS and PME specific attributes |
| | accessible only on the PCS or PME level. | | | accessible only on the PCS or PME level. |
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
| ifType | ethernetCsmacd(6) for PCS, shdsl(169) for | | ifType | ethernetCsmacd(6) for PCS, shdsl(169) for |
| | 2BASE-TL PME, vdsl(97) for 10PASS-TS PME | | | 2BASE-TL PME, vdsl(97) for 10PASS-TS PME |
+---------------+---------------------------------------------------+
+---------------+---------------------------------------------------+
| ifSpeed | Operating data rate for the PME. For the PCS it | | ifSpeed | Operating data rate for the PME. For the PCS it |
| | is the sum of the current operating data rates of | | | is the sum of the current operating data rates of |
| | all PMEs in the aggregation group, without the | | | all PMEs in the aggregation group, without the |
| | 64/65B encapsulation overhead and PAF overhead, | | | 64/65B encapsulation overhead and PAF overhead, |
| | but accounting for the Inter-Frame Gaps (IFG) | | | but accounting for the Inter-Frame Gaps (IFG) |
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
| ifAdminStatus | Setting this object to 'up' instructs a | | ifAdminStatus | Setting this object to 'up' instructs a |
| | particular PCS (with all PMEs connected to it) or | | | particular PCS (with all PMEs connected to it) or |
| | PME to start initialization process | | | PME to start initialization process |
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
| ifOperStatus | efmCuPmeOperStatus supplements the 'down' value | | ifOperStatus | efmCuPmeOperStatus supplements the 'down' value |
| | of ifOperStatus for PMEs. | | | of ifOperStatus for PMEs. |
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
Table 1: EFMCu interpretation of IF-MIB objects Table 1: EFMCu interpretation of IF-MIB objects
3.2. Relation to SHDSL MIB module 3.2. Relation to SHDSL MIB module
G.SHDSL.bis modems, similar to PME(s) comprising a 2BASE-TL port, are G.SHDSL.bis modems, similar to PMEs comprising a 2BASE-TL port, are
described in HDSL2-SHDSL-LINE-MIB [RFC4319]. Note that not all described in the HDSL2-SHDSL-LINE-MIB module [RFC4319]. Note that
attributes of G.SHDSL modems reflected in HDSL2-SHDSL-LINE-MIB have not all attributes of G.SHDSL modems reflected in the HDSL2-SHDSL-
adequate management objects (Clause 30 attributes and Clause 45 LINE-MIB module have adequate management objects (Clause 30
registers) in the EFM standard. attributes and Clause 45 registers) in the EFM standard.
Because of these differences and for the purposes of simplicity, Because of these differences and for the purposes of simplicity,
unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs
and name consistency (e.g. prefixing the 2BASE-TL PME related objects and name consistency (e.g. prefixing the 2BASE-TL PME related objects
with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided not to with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided not to
reference HDSL2-SHDSL-LINE-MIB objects, but define all the relevant reference HDSL2-SHDSL-LINE-MIB objects, but define all the relevant
objects in the EFM-CU-MIB module. objects in the EFM-CU-MIB module.
However, if some functionality, not available in the EFM-CU-MIB However, if some functionality not available in the EFM-CU-MIB module
module, is required and supported by the PME, e.g. performance is required and supported by the PME, e.g. performance monitoring,
monitoring, relevant HDSL2-SHDSL-LINE-MIB groups MAY be included and relevant HDSL2-SHDSL-LINE-MIB groups MAY be included and applied for
applied for PMEs of 2BASE-TL subtype. PMEs of 2BASE-TL subtype.
3.3. Relation to VDSL MIB module 3.3. Relation to VDSL MIB module
VDSL modems, similar to the PME(s) comprising a 10PASS-TS port, are VDSL modems, similar to the PME(s) comprising a 10PASS-TS port, are
described in VDSL-LINE-EXT-MCM-MIB [RFC4070]. Note that not all described in the VDSL-LINE-EXT-MCM-MIB module [RFC4070]. Note that
attributes of VDSL modems reflected in VDSL-LINE-EXT-MCM-MIB have not all attributes of VDSL modems reflected in the VDSL-LINE-EXT-MCM-
adequate management objects (Clause 30 attributes and Clause 45 MIB module have adequate management objects (Clause 30 attributes and
registers) in the EFM standard. Clause 45 registers) in the EFM standard.
Because of these differences and for the purposes of simplicity, Because of these differences and for the purposes of simplicity,
unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs
and name consistency, it was decided not to reference VDSL-LINE-EXT- and name consistency, it was decided not to reference VDSL-LINE-EXT-
MCM-MIB objects, but define all the relevant objects in the EFM-CU- MCM-MIB objects, but define all the relevant objects in the EFM-CU-
MIB module. MIB module.
However, if some functionality, not available in the EFM-CU-MIB However, if some functionality not available in the EFM-CU-MIB module
module, is required and supported by the PME, relevant VDSL-LINE-EXT- is required and supported by the PME, relevant VDSL-LINE-EXT-MCM-MIB
MCM-MIB groups MAY be included and applied for PMEs of 10PASS-TS groups MAY be included and applied for PMEs of 10PASS-TS subtype.
subtype.
3.4. Relation to Ethernet-Like and MAU MIB modules 3.4. Relation to Ethernet-Like and MAU MIB modules
The implementation of EtherLike-MIB [RFC3635] and MAU-MIB The implementation of the EtherLike-MIB [RFC3635] and MAU-MIB
[I-D.ietf-hubmib-rfc3636bis] is REQUIRED for the EFMCu interfaces. [RFC4836] modules is REQUIRED for EFMCu interfaces.
Two new values of ifMauType (OBJECT-IDENTITIES of dot3MauType) and Two new values of ifMauType (OBJECT-IDENTITIES of dot3MauType) and
corresponding bit definitions of ifMauTypeListBits corresponding bit definitions of ifMauTypeListBits
(IANAifMauTypeListBits) have been defined in the IANA-MAU-MIB (IANAifMauTypeListBits) have been defined in the IANA-MAU-MIB module
[I-D.ietf-hubmib-rfc3636bis] for the EFMCu MAUs: [RFC4836] for EFMCu MAUs:
o dot3MauType2BaseTL and b2BaseTL - for 2BASE-TL MAU o dot3MauType2BaseTL and b2BaseTL - for 2BASE-TL MAU
o dot3MauType10PassTS and b10PassTS - for 10PASS-TS MAU o dot3MauType10PassTS and b10PassTS - for 10PASS-TS MAU
Additionally IANA-MAU-MIB defines two new values of Additionally, the IANA-MAU-MIB module defines two new values of
ifMauMediaAvailable, as a textual convention IANAifMauMediaAvailable ifMauMediaAvailable, as a textual convention IANAifMauMediaAvailable
- availableReduced and ready, specifically for the EFMCu ports. Due - availableReduced and ready, specifically for EFMCu ports. Due to
to the PME aggregation, the EFMCu interpretation of some possible the PME aggregation, the EFMCu interpretation of some possible
ifMauMediaAvailable values differs from other MAUs as follows: ifMauMediaAvailable values differs from other MAUs as follows:
o unknown - the EFMCu interface (PCS with connected PMEs) is o unknown - the EFMCu interface (PCS with connected PMEs) is
initializing initializing
o ready - the interface is down, at least one PME in the aggregation o ready - the interface is down, at least one PME in the aggregation
group (all PMEs connected to the PCS) is ready for handshake group (all PMEs connected to the PCS) is ready for handshake
o available - the interface is up, all PMEs in the aggregation group o available - the interface is up, all PMEs in the aggregation group
are up are up
skipping to change at page 13, line 50 skipping to change at page 13, line 48
cross-connect (cross-connect capability). cross-connect (cross-connect capability).
o ifInvCapStackTable - an inverse of the ifCapstackTable. o ifInvCapStackTable - an inverse of the ifCapstackTable.
4.3. PME Profiles 4.3. PME Profiles
Since a managed node can have a large number of EFMCu PHYs, Since a managed node can have a large number of EFMCu PHYs,
provisioning every parameter on every EFMCu PHY may become provisioning every parameter on every EFMCu PHY may become
burdensome. Moreover, most PMEs are provisioned identically with the burdensome. Moreover, most PMEs are provisioned identically with the
same set of parameters. To simplify the provisioning process, the same set of parameters. To simplify the provisioning process, the
EFM-CU-MIB module makes use of configuration profiles, similar to EFM-CU-MIB module makes use of configuration profiles, similar to the
HDSL2-SHDSL-LINE-MIB and VDSL-LINE-EXT-MCM-MIB. A profile is a set HDSL2-SHDSL-LINE-MIB and VDSL-LINE-EXT-MCM-MIB modules. A profile is
of parameters, used either for configuration or representation of a a set of parameters, used either for configuration or representation
PME. The same profile can be shared by multiple PME ports, using the of a PME. The same profile can be shared by multiple PME ports using
same configuration. the same configuration.
The PME profiles are defined in efmCuPme2BProfileTable and The PME profiles are defined in the efmCuPme2BProfileTable and
efmCuPme10PProfileTable for 2BASE-TL and 10PASS-TS PMEs respectively. efmCuPme10PProfileTable for 2BASE-TL and 10PASS-TS PMEs,
There are 12 predefined standard profiles for 2BASE-TL and 22 respectively. There are 12 predefined standard profiles for 2BASE-TL
standard profiles for 10PASS-TS, defined in 802.3ah and dedicated for and 22 standard profiles for 10PASS-TS, defined in 802.3ah and
rapid provisioning of EFMCu PHYs in most scenarios. In addition the dedicated for rapid provisioning of EFMCu PHYs in most scenarios. In
EFM-CU-MIB defines two additional predefined profiles for "best- addition, the EFM-CU-MIB defines two additional predefined profiles
effort" provisioning of 2BASE-TL PMEs. An ability to define new for "best-effort" provisioning of 2BASE-TL PMEs. An ability to
configuration profiles is also provided to allow for EFMCu deployment define new configuration profiles is also provided to allow for EFMCu
tailored to specific copper environment and spectral regulations. deployment tailored to specific copper environments and spectral
regulations.
A specific configuration or administrative profile is assigned to a A specific configuration or administrative profile is assigned to a
specific PME via efmCuPmeAdminProfile object. If specific PME via the efmCuPmeAdminProfile object. If
efmCuPmeAdminProfile is zero, then efmCuAdminProfile object of the efmCuPmeAdminProfile is zero, then the efmCuAdminProfile object of
PCS port, connected to the PME, determines the configuration profile the PCS port connected to the PME determines the configuration
(or a list of possible profiles) for that PME. This mechanism allows profile (or a list of possible profiles) for that PME. This
to specify a common profile(s) for all PMEs connected to the PCS mechanism allows to specify a common profile for all PMEs connected
port, with an ability to change individual PME profiles by setting to the PCS port, with an ability to change individual PME profiles by
efmCuPmeAdminProfile object, which overwrites the profile set by setting efmCuPmeAdminProfile object, which overwrites the profile set
efmCuAdminProfile. by efmCuAdminProfile.
A current operating PME profile is pointed to by efmCuPmeOperProfile A current operating PME profile is pointed to by *the*
object. Note that this profile entry, can be created automatically, efmCuPmeOperProfile object. Note that this profile entry can be
to reflect achieved parameters in adaptive (not fixed) created automatically to reflect achieved parameters in adaptive (not
initialization. fixed) initialization.
4.4. Mapping of IEEE 802.3ah Managed Objects 4.4. Mapping of IEEE 802.3ah Managed Objects
This section contains the mapping between relevant managed objects This section contains the mapping between relevant managed objects
(attributes) defined in [802.3ah] Clause 30, and managed objects (attributes) defined in [802.3ah] Clause 30, and managed objects
defined in this document and in associated MIB modules, i.e., the IF- defined in this document and in associated MIB modules, i.e., the IF-
MIB [RFC2863]. MIB [RFC2863].
Note that majority of the objects defined in the EFM-CU-MIB module do Note that the majority of the objects defined in the EFM-CU-MIB
not have direct counterparts in Clause 30 and instead refer to Clause module do not have direct counterparts in Clause 30 and instead refer
45 registers. to Clause 45 registers.
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| IEEE 802.3 Managed Object | Corresponding SNMP Object | | IEEE 802.3 Managed Object | Corresponding SNMP Object |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| oMAU - Basic Package | | | oMAU - Basic Package | |
| (Mandatory) | | | (Mandatory) | |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aMAUType | ifMauType (MAU-MIB) | | aMAUType | ifMauType (MAU-MIB) |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| aMAUTypeList | ifMauTypeListBits (MAU-MIB) | | aMAUTypeList | ifMauTypeListBits (MAU-MIB) |
skipping to change at page 16, line 40 skipping to change at page 16, line 40
FROM SNMPv2-TC -- RFC 2579 FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- RFC 2580
ifStackGroup2, ifStackHigherLayer, ifStackLowerLayer ifStackGroup2, ifStackHigherLayer, ifStackLowerLayer
FROM IF-MIB -- RFC 2863 FROM IF-MIB -- RFC 2863
ifInvStackGroup ifInvStackGroup
FROM IF-INVERTED-STACK-MIB -- RFC 2864 FROM IF-INVERTED-STACK-MIB -- RFC 2864
; ;
ifCapStackMIB MODULE-IDENTITY ifCapStackMIB MODULE-IDENTITY
LAST-UPDATED "200702210000Z" -- February 21, 2007 LAST-UPDATED "200707290000Z" -- July 29, 2007
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://www.ietf.org/html.charters/hubmib-charter.html http://www.ietf.org/html.charters/hubmib-charter.html
Mailing Lists: Mailing Lists:
General Discussion: hubmib@ietf.org General Discussion: hubmib@ietf.org
To Subscribe: hubmib-request@ietf.org To Subscribe: hubmib-request@ietf.org
In Body: subscribe your_email_address In Body: subscribe your_email_address
Chair: Bert Wijnen Chair: Bert Wijnen
skipping to change at page 17, line 30 skipping to change at page 17, line 30
DESCRIPTION DESCRIPTION
"The objects in this MIB module are used to describe "The objects in this MIB module are used to describe
cross-connect capabilities of stacked (layered) interfaces, cross-connect capabilities of stacked (layered) interfaces,
complementing ifStackTable and ifInvStackTable defined in complementing ifStackTable and ifInvStackTable defined in
IF-MIB and IF-INVERTED-STACK-MIB respectively. IF-MIB and IF-INVERTED-STACK-MIB respectively.
Copyright (C) The IETF Trust (2007). This version Copyright (C) The IETF Trust (2007). This version
of this MIB module is part of RFC XXXX; see the RFC of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices." itself for full legal notices."
REVISION "200702210000Z" -- February 21, 2007 REVISION "200707290000Z" -- July 29, 2007
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- EdNote: Replace XXXX with the actual RFC number & -- EdNote: Replace XXXX with the actual RFC number &
-- remove this note -- remove this note
::= { mib-2 ZZZ } ::= { mib-2 ZZZ }
-- EdNote: Replace ZZZ with a real OID once it is -- EdNote: Replace ZZZ with a real OID once it is
-- allocated & remove this note. -- allocated & remove this note.
skipping to change at page 18, line 26 skipping to change at page 18, line 26
ifStackTable). In particular, it contains information on ifStackTable). In particular, it contains information on
which sub-layers MAY possibly run 'on top of' which other which sub-layers MAY possibly run 'on top of' which other
sub-layers, as determined by cross-connect capability of the sub-layers, as determined by cross-connect capability of the
device, where each sub-layer corresponds to a conceptual row device, where each sub-layer corresponds to a conceptual row
in the ifTable. For example, when the sub-layer with ifIndex in the ifTable. For example, when the sub-layer with ifIndex
value x can be connected to run on top of the sub-layer with value x can be connected to run on top of the sub-layer with
ifIndex value y, then this table contains: ifIndex value y, then this table contains:
ifCapStackStatus.x.y=true ifCapStackStatus.x.y=true
ifCapStackStatus.x.y row does not exist if it is impossible The ifCapStackStatus.x.y row does not exist if it is
to connect between the sub-layers x and y. impossible to connect between the sub-layers x and y.
Note that for most stacked interfaces (e.g. 2BASE-TL) Note that for most stacked interfaces (e.g. 2BASE-TL)
there's always at least one higher-level interface (e.g. PCS there's always at least one higher-level interface (e.g. PCS
port) for each lower-level interface (e.g. PME) and at port) for each lower-level interface (e.g. PME) and at
least one lower-level interface for each higher-level least one lower-level interface for each higher-level
interface, that is, there is at least a single row with a interface, that is, there is at least a single row with a
'true' status for any existing value of x or y. 'true' status for any such existing value of x or y.
This table is read only as it describes device capability" This table is read-only as it describes device capabilities."
REFERENCE REFERENCE
"IF-MIB, ifStackTable" "IF-MIB, ifStackTable"
::= { ifCapStackObjects 1 } ::= { ifCapStackObjects 1 }
ifCapStackEntry OBJECT-TYPE ifCapStackEntry OBJECT-TYPE
SYNTAX IfCapStackEntry SYNTAX IfCapStackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information on a particular relationship between two "Information on a particular relationship between two
skipping to change at page 19, line 41 skipping to change at page 19, line 41
Note that lower-layer interface availability per higher-layer, Note that lower-layer interface availability per higher-layer,
indicated by the value of 'true', can be constrained by indicated by the value of 'true', can be constrained by
other parameters, for example by the aggregation capacity of other parameters, for example by the aggregation capacity of
a higher-layer interface or by the lower-layer interface in a higher-layer interface or by the lower-layer interface in
question being already connected to another higher-layer question being already connected to another higher-layer
interface. In order to ensure that a particular sub-layer can interface. In order to ensure that a particular sub-layer can
be connected to another sub-layer, all respective objects be connected to another sub-layer, all respective objects
(e.g. ifCapStackTable, ifStackTable and efmCuPAFCapacity for (e.g. ifCapStackTable, ifStackTable and efmCuPAFCapacity for
for EFMCu interfaces) SHALL be inspected. for EFMCu interfaces) SHALL be inspected.
This object is read only, unlike ifStackStatus, as it This object is read-only, unlike ifStackStatus, as it
describes a cross-connect capability." describes a cross-connect capability."
::= { ifCapStackEntry 1 } ::= { ifCapStackEntry 1 }
ifInvCapStackTable OBJECT-TYPE ifInvCapStackTable OBJECT-TYPE
SYNTAX SEQUENCE OF IfInvCapStackEntry SYNTAX SEQUENCE OF IfInvCapStackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing information on the possible relationships "A table containing information on the possible relationships
between the multiple sub-layers of network interfaces. This between the multiple sub-layers of network interfaces. This
skipping to change at page 20, line 19 skipping to change at page 20, line 19
each sub-layer corresponds to a conceptual row in the ifTable. each sub-layer corresponds to a conceptual row in the ifTable.
For example, when the sub-layer with ifIndex value x MAY be For example, when the sub-layer with ifIndex value x MAY be
connected to run underneath the sub-layer with ifIndex value connected to run underneath the sub-layer with ifIndex value
y, then this table contains: y, then this table contains:
ifInvCapStackStatus.x.y=true ifInvCapStackStatus.x.y=true
This table contains exactly the same number of rows as the This table contains exactly the same number of rows as the
ifCapStackTable, but the rows appear in a different order. ifCapStackTable, but the rows appear in a different order.
This table is read only as it describes a cross-connect This table is read-only as it describes a cross-connect
capability." capability."
REFERENCE REFERENCE
"IF-INVERTED-STACK-MIB, ifInvStackTable" "IF-INVERTED-STACK-MIB, ifInvStackTable"
::= { ifCapStackObjects 2 } ::= { ifCapStackObjects 2 }
ifInvCapStackEntry OBJECT-TYPE ifInvCapStackEntry OBJECT-TYPE
SYNTAX IfInvCapStackEntry SYNTAX IfInvCapStackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 22, line 50 skipping to change at page 22, line 50
FROM SNMPv2-TC -- RFC 2579 FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- RFC 2580
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC 3411 FROM SNMP-FRAMEWORK-MIB -- RFC 3411
ifIndex, ifSpeed ifIndex, ifSpeed
FROM IF-MIB -- RFC 2863 FROM IF-MIB -- RFC 2863
; ;
efmCuMIB MODULE-IDENTITY efmCuMIB MODULE-IDENTITY
LAST-UPDATED "200702210000Z" -- February 21, 2007 LAST-UPDATED "200707290000Z" -- July 29, 2007
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://www.ietf.org/html.charters/hubmib-charter.html http://www.ietf.org/html.charters/hubmib-charter.html
Mailing Lists: Mailing Lists:
General Discussion: hubmib@ietf.org General Discussion: hubmib@ietf.org
To Subscribe: hubmib-request@ietf.org To Subscribe: hubmib-request@ietf.org
In Body: subscribe your_email_address In Body: subscribe your_email_address
Chair: Bert Wijnen Chair: Bert Wijnen
Postal: Alcatel-Lucent Postal: Alcatel-Lucent
Schagen 33 Schagen 33
3461 GL Linschoten 3461 GL Linschoten
Netherlands Netherlands
Tel: +31-348-407-775 Phone: +31-348-407-775
E-mail: bwijnen@alcatel-lucent.com Email: bwijnen@alcatel-lucent.com
Editor: Edward Beili Editor: Edward Beili
Postal: Actelis Networks Inc. Postal: Actelis Networks Inc.
25 Bazel St., P.O.B. 10173 25 Bazel St., P.O.B. 10173
Petach-Tikva 10173 Petach-Tikva 10173
Israel Israel
Tel: +972-3-924-3491 Phone: +972-3-924-3491
E-mail: edward.beili@actelis.com" Email: edward.beili@actelis.com"
DESCRIPTION DESCRIPTION
"The objects in this MIB module are used to manage "The objects in this MIB module are used to manage
the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces
2BASE-TL and 10PASS-TS, defined in IEEE Std. 802.3ah-2004, 2BASE-TL and 10PASS-TS, defined in IEEE Std. 802.3ah-2004,
which is now a part of IEEE Std. 802.3-2005. which is now a part of IEEE Std. 802.3-2005.
The following references are used throughout this MIB module: The following references are used throughout this MIB module:
[802.3ah] refers to: [802.3ah] refers to:
skipping to change at page 24, line 18 skipping to change at page 24, line 18
[G.991.2] refers to: [G.991.2] refers to:
ITU-T Recommendation G.991.2: 'Single-pair High-speed Digital ITU-T Recommendation G.991.2: 'Single-pair High-speed Digital
Subscriber Line (SHDSL) transceivers', December 2003. Subscriber Line (SHDSL) transceivers', December 2003.
[ANFP] refers to: [ANFP] refers to:
NICC Document ND1602:2005/08: 'Specification of the Access NICC Document ND1602:2005/08: 'Specification of the Access
Network Frequency Plan (ANFP) applicable to transmission Network Frequency Plan (ANFP) applicable to transmission
systems used on the BT Access Network,' August 2005. systems used on the BT Access Network,' August 2005.
The following normative documents are quoted by the DESCRIPTION
clauses in this MIB module:
[G.993.1] refers to:
ITU-T Recommendation G.993.1: 'Very High speed Digital
Subscriber Line transceivers', June 2004.
[T1.424] refers to:
ANSI T1.424-2004: 'Interface Between Networks and Customer
Installation Very-high-bit-rate Digital Subscriber Lines
(VDSL) Metallic Interface (DMT Based)', June 2004.
[TS 101 270-1] refers to:
ETSI TS 101 270-1: 'Transmission and Multiplexing (TM);
Access transmission systems on metallic access cables;
Very high speed Digital Subscriber Line (VDSL); Part 1:
Functional requirements', October 2005.
Naming Conventions: Naming Conventions:
Atn - Attenuation Atn - Attenuation
CO - Central Office CO - Central Office
CPE - Customer Premises Equipment CPE - Customer Premises Equipment
EFM - Ethernet in the First Mile EFM - Ethernet in the First Mile
EFMCu - EFM Copper EFMCu - EFM Copper
MDIO - Management Data Input/Output MDIO - Management Data Input/Output
Mgn - Margin Mgn - Margin
PAF - PME Aggregation Function PAF - PME Aggregation Function
PBO - Power Back-Off PBO - Power Back-Off
skipping to change at page 24, line 34 skipping to change at page 25, line 4
MDIO - Management Data Input/Output MDIO - Management Data Input/Output
Mgn - Margin Mgn - Margin
PAF - PME Aggregation Function PAF - PME Aggregation Function
PBO - Power Back-Off PBO - Power Back-Off
PCS - Physical Coding Sublayer PCS - Physical Coding Sublayer
PMD - Physical Medium Dependent PMD - Physical Medium Dependent
PME - Physical Medium Entity PME - Physical Medium Entity
PSD - Power Spectral Density PSD - Power Spectral Density
SNR - Signal to Noise Ratio SNR - Signal to Noise Ratio
TCPAM - Trellis Coded Pulse Amplitude Modulation TCPAM - Trellis Coded Pulse Amplitude Modulation
Copyright (C) The IETF Trust (2007). This version Copyright (C) The IETF Trust (2007). This version
of this MIB module is part of RFC XXXX; see the RFC of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices." itself for full legal notices."
REVISION "200702210000Z" -- February 21, 2007 REVISION "200707290000Z" -- July 29, 2007
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- EdNote: Replace XXXX with the actual RFC number & -- EdNote: Replace XXXX with the actual RFC number &
-- remove this note -- remove this note
::= { mib-2 YYY } ::= { mib-2 YYY }
-- EdNote: Replace YYY with a real OID once it is -- EdNote: Replace YYY with a real OID once it is
-- allocated & remove this note. -- allocated & remove this note.
skipping to change at page 25, line 47 skipping to change at page 26, line 16
of the description of any object which uses this syntax. of the description of any object which uses this syntax.
Examples of the usage of zero value might include situations Examples of the usage of zero value might include situations
where current operational profile is unknown." where current operational profile is unknown."
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
EfmProfileIndexList ::= TEXTUAL-CONVENTION EfmProfileIndexList ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d:" DISPLAY-HINT "1d:"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention represents a list of up to 6 "This textual convention represents a list of up to 6
EfmProfileIndex's, any of which can be chosen for EfmProfileIndex values, any of which can be chosen for
configuration of an PME in a managed EFMCu port. configuration of an PME in a managed EFMCu port.
The EfmProfileIndex textual convention defines a greater than The EfmProfileIndex textual convention defines a greater than
zero value used to identify a PME profile. zero value used to identify a PME profile.
The value of this object is a concatenation of one or The value of this object is a concatenation of zero or
more (up to 6) octets, where each octet contains an 8-bit more (up to 6) octets, where each octet contains an 8-bit
EfmProfileIndex value. EfmProfileIndex value.
A zero length octet string is object-specific and MUST A zero-length octet string is object-specific and MUST
therefore be defined as part of the description of any object therefore be defined as part of the description of any object
which uses this syntax. Examples of the usage of zero length which uses this syntax. Examples of the usage of a zero-length
value might include situations where an object using this value might include situations where an object using this
textual convention is irrelevant for a specific EFMCu port textual convention is irrelevant for a specific EFMCu port
type." type."
SYNTAX OCTET STRING (SIZE(0..6)) SYNTAX OCTET STRING (SIZE(0..6))
EfmTruthValueOrUnknown ::= TEXTUAL-CONVENTION EfmTruthValueOrUnknown ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention is an extension of the TruthValue "This textual convention is an extension of the TruthValue
convention. The latter defines a boolean value with convention. The latter defines a boolean value with possible
possible values of true(1) and false(2). This values of true(1) and false(2). This extension permits the
extension permits the additional value of unknown(0), which additional value of unknown(0), that can be returned as the
can be returned as a result of GET operation, when an exact result of a GET operation, when an exact true or false value
true or false value of the object cannot be determined." of the object cannot be determined."
SYNTAX INTEGER { unknown(0), true(1), false(2) } SYNTAX INTEGER { unknown(0), true(1), false(2) }
-- Port Notifications Group -- Port Notifications Group
efmCuPortNotifications OBJECT IDENTIFIER ::= { efmCuPort 0 } efmCuPortNotifications OBJECT IDENTIFIER ::= { efmCuPort 0 }
efmCuLowRateCrossing NOTIFICATION-TYPE efmCuLowRateCrossing NOTIFICATION-TYPE
OBJECTS { OBJECTS {
-- ifIndex is not needed here since we are under specific PCS
ifSpeed, ifSpeed,
efmCuThreshLowRate efmCuThreshLowRate
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that the EFMCu port' data rate "This notification indicates that the EFMCu port's data rate
has reached/dropped below or exceeded the low rate threshold, has reached/dropped below or exceeded the low rate threshold,
specified by efmCuThreshLowRate. specified by efmCuThreshLowRate.
This notification MAY be send for the -O subtype ports This notification MAY be sent for the -O subtype ports
(2BaseTL-O/10PassTS-O) while the port is up, on the crossing (2BaseTL-O/10PassTS-O) while the port is up, on the crossing
event in both directions: from normal (rate is above the event in both directions: from normal (rate is above the
threshold) to low (rate equals the threshold or below it) and threshold) to low (rate equals the threshold or below it) and
from low to normal. This notification is not applicable to from low to normal. This notification is not applicable to
the -R subtypes. the -R subtypes.
It is RECOMMENDED that a small debouncing period of 2.5 sec, It is RECOMMENDED that a small debouncing period of 2.5 sec,
between the detection of the condition and notification, between the detection of the condition and the notification,
is implemented to prevent simultaneous LinkUp/LinkDown and is implemented to prevent simultaneous LinkUp/LinkDown and
efmCuLowRateCrossing notifications to be sent. efmCuLowRateCrossing notifications to be sent.
The adaptive nature of the EFMCu technology allows the port to The adaptive nature of the EFMCu technology allows the port to
adapt itself to the changes in the copper environment, e.g. adapt itself to the changes in the copper environment, e.g.
an impulse noise, alien crosstalk or a micro-interruption may an impulse noise, alien crosstalk or a micro-interruption may
temporarily drop one or more PMEs in the aggregation group, temporarily drop one or more PMEs in the aggregation group,
causing a rate degradation of the aggregated EFMCu link. causing a rate degradation of the aggregated EFMCu link.
The dropped PMEs would then try to re-initialize, possibly at The dropped PMEs would then try to re-initialize, possibly at
a lower rate than before, adjusting the rate to provide a lower rate than before, adjusting the rate to provide
skipping to change at page 28, line 23 skipping to change at page 28, line 42
(PCS). (PCS).
When 'disabled', PME Aggregation will not be performed by the When 'disabled', PME Aggregation will not be performed by the
PCS. No more than a single PME can be assigned to this PCS in PCS. No more than a single PME can be assigned to this PCS in
this case. this case.
When 'enabled', PAF will be performed by the PCS when the link When 'enabled', PAF will be performed by the PCS when the link
is Up, even on a single attached PME, if PAF is supported. is Up, even on a single attached PME, if PAF is supported.
PCS ports incapable of supporting PAF SHALL return a value of PCS ports incapable of supporting PAF SHALL return a value of
'disabled'. Attempts to 'enable' such ports SHALL be rejected. 'disabled'. Attempts to 'enable' such ports SHALL be rejected.
PAF 'enabled' port with multiple PMEs assigned cannot be A PAF 'enabled' port with multiple PMEs assigned cannot be
'disabled'. Attempts to 'disable' such port SHALL be rejected, 'disabled'. Attempts to 'disable' such port SHALL be rejected,
until at most one PME is left assigned. until at most one PME is left assigned.
Changing PAFAdminState is a traffic disruptive operation and Changing PAFAdminState is a traffic disruptive operation and
as such SHALL be done when the link is Down. Attempts to as such SHALL be done when the link is Down. Attempts to
change this object SHALL be rejected if the link is Up or change this object SHALL be rejected if the link is Up or
Initializing. Initializing.
This object maps to the Clause 30 attribute aPAFAdminState. This object maps to the Clause 30 attribute aPAFAdminState.
skipping to change at page 28, line 51 skipping to change at page 29, line 22
::= { efmCuPortConfEntry 1 } ::= { efmCuPortConfEntry 1 }
efmCuPAFDiscoveryCode OBJECT-TYPE efmCuPAFDiscoveryCode OBJECT-TYPE
SYNTAX PhysAddress (SIZE(0|6)) SYNTAX PhysAddress (SIZE(0|6))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"PAF Discovery Code of the EFMCu port (PCS). "PAF Discovery Code of the EFMCu port (PCS).
A unique 6 octet long code used by the Discovery function, A unique 6 octet long code used by the Discovery function,
when PAF is supported. when PAF is supported.
PCS ports incapable of supporting PAF SHALL return a zero PCS ports incapable of supporting PAF SHALL return a
length octet string on an attempt to read this object. An zero-length octet string on an attempt to read this object.
attempt to write to this object SHALL be rejected for such An attempt to write to this object SHALL be rejected for such
ports. ports.
This object MUST be instantiated for the -O subtype PCS before This object MUST be instantiated for the -O subtype PCS before
writing operations on the efmCuPAFRemoteDiscoveryCode writing operations on the efmCuPAFRemoteDiscoveryCode
(Set_if_Clear and Clear_if_Same) are performed by PMEs (Set_if_Clear and Clear_if_Same) are performed by PMEs
associated with the PCS. associated with the PCS.
The initial value of this object for -R subtype ports after The initial value of this object for -R subtype ports after
reset is all zeroes. For -R subtype ports, the value of this reset is all zeroes. For -R subtype ports, the value of this
object cannot be changed directly. This value may be changed object cannot be changed directly. This value may be changed
as a result of writing operation on the as a result of writing operation on the
efmCuPAFRemoteDiscoveryCode object of remote PME of -O efmCuPAFRemoteDiscoveryCode object of remote PME of -O
skipping to change at page 29, line 37 skipping to change at page 30, line 7
REFERENCE REFERENCE
"[802.3ah] 61.2.2.8.3, 61.2.2.8.4, 45.2.6.6.1, 45.2.6.8, "[802.3ah] 61.2.2.8.3, 61.2.2.8.4, 45.2.6.6.1, 45.2.6.8,
61A.2" 61A.2"
::= { efmCuPortConfEntry 2 } ::= { efmCuPortConfEntry 2 }
efmCuAdminProfile OBJECT-TYPE efmCuAdminProfile OBJECT-TYPE
SYNTAX EfmProfileIndexList SYNTAX EfmProfileIndexList
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Desired configuration Profile(s), common for all PMEs in the "Desired configuration profile(s), common for all PMEs in the
EFMCu port. This object is a list of pointers to entries in EFMCu port. This object is a list of pointers to entries in
either efmCuPme2BProfileTable or either efmCuPme2BProfileTable or
efmCuPme10PProfileTable, depending on the current efmCuPme10PProfileTable, depending on the current
operating SubType of the EFMCu port as indicated by operating SubType of the EFMCu port as indicated by
efmCuPortSide. efmCuPortSide.
The value of this object is a list of up to 6 indices of The value of this object is a list of up to 6 indices of
Profiles. If this list consists of a single Profile index, profiles. If this list consists of a single profile index,
then all PMEs assigned to this EFMCu port SHALL be configured then all PMEs assigned to this EFMCu port SHALL be configured
according to the Profile referenced by that index, unless it according to the profile referenced by that index, unless it
is overwritten by corresponding non-zero efmCuPmeAdminProfile, is overwritten by a corresponding non-zero
which takes precedence over efmCuAdminProfile. efmCuPmeAdminProfile instance, which takes precedence over
The list, consisting of more than one index, allows each PME efmCuAdminProfile.
in the port to be configured according to any Profile A list consisting of more than one index allows each PME
in the port to be configured according to any profile
specified in the list. specified in the list.
By default this object has a value of 0x01, referencing the
By default this object has a value of 0x01, referencing 1st 1st entry in efmCuPme2BProfileTable or
entry in efmCuPme2BProfileTable or efmCuPme10PProfileTable. efmCuPme10PProfileTable.
This object is writable and readable for the -O subtype This object is writable and readable for the -O subtype
(2BaseTL-O or 10PassTS-O) EFMCu ports. It is irrelevant for (2BaseTL-O or 10PassTS-O) EFMCu ports. It is irrelevant for
the -R subtype (2BaseTL-R or 10PassTS-R) ports - a zero the -R subtype (2BaseTL-R or 10PassTS-R) ports - a
length octet string SHALL be returned on an attempt to read zero-length octet string SHALL be returned on an attempt to
this object and an attempt to change this object MUST be read this object and an attempt to change this object MUST be
rejected in this case. rejected in this case.
Note that current operational Profile value is available via Note that the current operational profile value is available
efmCuPmeOperProfile object. via the efmCuPmeOperProfile object.
Modification of this object MUST be performed when the link is Any modification of this object MUST be performed when the
Down. Attempts to change this object MUST be rejected, if the link is Down. Attempts to change this object MUST be rejected,
link is Up or Initializing. if the link is Up or Initializing.
Attempts to set this object to a list with a member Attempts to set this object to a list with a member value that
value, that is not the value of the index for an active entry is not the value of the index for an active entry in the
in the corresponding profile table, MUST be rejected. corresponding profile table MUST be rejected.
This object maps to the Clause 30 attribute aProfileSelect.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"[802.3ah] 30.11.2.1.6" "[802.3ah] 30.11.2.1.6"
DEFVAL { '01'H } DEFVAL { '01'H }
::= { efmCuPortConfEntry 3 } ::= { efmCuPortConfEntry 3 }
efmCuTargetDataRate OBJECT-TYPE efmCuTargetDataRate OBJECT-TYPE
SYNTAX Unsigned32(1..100000|999999) SYNTAX Unsigned32(1..100000|999999)
UNITS "Kbps" UNITS "Kbps"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Desired EFMCu port 'net' (as seen across MII) Data Rate in "Desired EFMCu port 'net' (as seen across MII) Data Rate in
Kbps, to be achieved during initialization, under spectral Kbps, to be achieved during initialization, under spectral
restrictions placed on each PME via efmCuAdminProfile or restrictions placed on each PME via efmCuAdminProfile or
efmCuPmeAdminProfile, with the desired SNR Margin specified by efmCuPmeAdminProfile, with the desired SNR Margin specified by
skipping to change at page 30, line 45 skipping to change at page 31, line 18
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Desired EFMCu port 'net' (as seen across MII) Data Rate in "Desired EFMCu port 'net' (as seen across MII) Data Rate in
Kbps, to be achieved during initialization, under spectral Kbps, to be achieved during initialization, under spectral
restrictions placed on each PME via efmCuAdminProfile or restrictions placed on each PME via efmCuAdminProfile or
efmCuPmeAdminProfile, with the desired SNR Margin specified by efmCuPmeAdminProfile, with the desired SNR Margin specified by
efmCuTargetSnrMgn. efmCuTargetSnrMgn.
In case of PAF, this object represents a sum of individual PME In case of PAF, this object represents a sum of individual PME
data rates, modified to compensate for fragmentation and data rates, modified to compensate for fragmentation and
64/65B framing overhead (e.g. target data rate of 10Mbps 64/65B framing overhead (e.g. target data rate of 10Mbps
SHALL allow lossless transmission of full-duplex 10Mbps SHALL allow lossless transmission of a full-duplex 10Mbps
Ethernet frame stream with minimal inter-frame gap). Ethernet frame stream with minimal inter-frame gap).
The value is limited above by 100Mbps as this is the max The value is limited above by 100Mbps as this is the max
burst rate across MII for EFMCu ports. burst rate across MII for EFMCu ports.
The value between 1 and 100000 indicates that the total data The value between 1 and 100000 indicates that the total data
rate (ifSpeed) of the EFMCu port after initialization SHALL rate (ifSpeed) of the EFMCu port after initialization SHALL be
be equal to the target data rate or less, if the target data equal to the target data rate or less, if the target data rate
rate cannot be achieved under spectral restrictions specified cannot be achieved under spectral restrictions specified by
by efmCuAdminProfile/efmCuPmeAdminProfile and with desired SNR efmCuAdminProfile/efmCuPmeAdminProfile and with the desired
margin. In case the copper environment allows to achieve SNR margin. In case the copper environment allows to achieve
higher total data rate than that specified by the target, the a higher total data rate than that specified by the target,
excess capability SHALL be either converted to additional SNR the excess capability SHALL be either converted to additional
margin or reclaimed by minimizing transmit power as controlled SNR margin or reclaimed by minimizing transmit power as
by efmCuAdaptiveSpectra. controlled by efmCuAdaptiveSpectra.
The value of 999999 means that the target data rate is not The value of 999999 means that the target data rate is not
fixed and SHALL be set to the maximum attainable rate during fixed and SHALL be set to the maximum attainable rate during
initialization (Best Effort), under specified spectral initialization (Best Effort), under specified spectral
restrictions and with desired SNR Margin. restrictions and with the desired SNR Margin.
This object is read-write for the -O subtype EFMCu ports This object is read-write for the -O subtype EFMCu ports
(2BaseTL-O/10PassTS-O) and not available for the -R subtypes. (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
Changing of the Target Data Rate MUST be performed when the Changing of the Target Data Rate MUST be performed when the
link is Down. Attempts to change this object MUST be rejected link is Down. Attempts to change this object MUST be rejected
(in case of SNMP with the error inconsistentValue), if the (in case of SNMP with the error inconsistentValue), if the
link is Up or Initializing. link is Up or Initializing.
Note that current Data Rate of the EFMCu port is represented Note that the current Data Rate of the EFMCu port is
by ifSpeed object of IF-MIB. represented by the ifSpeed object of IF-MIB.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
::= { efmCuPortConfEntry 4 } ::= { efmCuPortConfEntry 4 }
efmCuTargetSnrMgn OBJECT-TYPE efmCuTargetSnrMgn OBJECT-TYPE
SYNTAX Unsigned32(0..21) SYNTAX Unsigned32(0..21)
UNITS "dB" UNITS "dB"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Desired EFMCu port SNR Margin to be achieved on all PMEs "Desired EFMCu port SNR Margin to be achieved on all PMEs
assigned to the port, during initializiation. (The SNR margin assigned to the port, during initialization. (The SNR margin
is the difference between the desired SNR and the actual SNR). is the difference between the desired SNR and the actual SNR).
Note that 802.3ah recommends using default Target SNR Margin Note that 802.3ah recommends using a default Target SNR Margin
of 5dB for 2BASE-TL ports and 6dB for 10PASS-TS ports in order 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 PMA to achieve a mean Bit Error Rate (BER) of 10^-7 at the PMA
service interface. service interface.
This object is read-write for the -O subtype EFMCu ports This object is read-write for the -O subtype EFMCu ports
(2BaseTL-O/10PassTS-O) and not available for the -R subtypes. (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
Changing of the Target SNR Margin MUST be performed when the Changing of the Target SNR Margin MUST be performed when the
link is Down. Attempts to change this object MUST be rejected link is Down. Attempts to change this object MUST be rejected
(in case of SNMP with the error inconsistentValue), if the (in case of SNMP with the error inconsistentValue), if the
link is Up or Initializing. link is Up or Initializing.
Note that current SNR Margin of the PMEs comprising the EFMCu Note that the current SNR Margin of the PMEs comprising the
port is represented by efmCuPmeSnrMgn. EFMCu port is represented by efmCuPmeSnrMgn.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"[802.3ah] 61.1.2" "[802.3ah] 61.1.2"
::= { efmCuPortConfEntry 5 } ::= { efmCuPortConfEntry 5 }
efmCuAdaptiveSpectra OBJECT-TYPE efmCuAdaptiveSpectra OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates how to utilize excess capacity when the copper "Indicates how to utilize excess capacity when the copper
environment allows to achieve higher total data rate than that environment allows to achieve a higher total data rate than
specified by the efmCuTargetDataRate. that specified by the efmCuTargetDataRate.
Value of true(1) indicates that the excess capability SHALL be A value of true(1) indicates that the excess capability SHALL
reclaimed by minimizing transmit power, e.g. using higher be reclaimed by minimizing transmit power, e.g. using higher
constellations and Power Back-Off, in order to reduce constellations and Power Back-Off, in order to reduce
interference to other copper pairs in the binder and the interference to other copper pairs in the binder and the
adverse impact to link/system performance. adverse impact to link/system performance.
Value of false(2) indicates that the excess capability SHALL A value of false(2) indicates that the excess capability SHALL
be converted to additional SNR margin and spread evenly across be converted to additional SNR margin and spread evenly across
all active PMEs assigned to the (PCS) port, to increase link all active PMEs assigned to the (PCS) port, to increase link
robustness. robustness.
This object is read-write for the -O subtype EFMCu ports This object is read-write for the -O subtype EFMCu ports
(2BaseTL-O/10PassTS-O) and not available for the -R subtypes. (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
Changing of this object MUST be performed when the link is Changing of this object MUST be performed when the link is
Down. Attempts to change this object MUST be rejected (in case Down. Attempts to change this object MUST be rejected (in case
of SNMP with the error inconsistentValue), if the link is Up of SNMP with the error inconsistentValue), if the link is Up
skipping to change at page 33, line 24 skipping to change at page 33, line 47
::= { efmCuPortConfEntry 7 } ::= { efmCuPortConfEntry 7 }
efmCuLowRateCrossingEnable OBJECT-TYPE efmCuLowRateCrossingEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether efmCuLowRateCrossing notifications should "Indicates whether efmCuLowRateCrossing notifications should
be generated for this interface. be generated for this interface.
Value of true(1) indicates that efmCuLowRateCrossing A value of true(1) indicates that efmCuLowRateCrossing
notification is enabled. Value of false(2) indicates that notification is enabled. A value of false(2) indicates that
the notification is disabled. the notification is disabled.
This object is read-write for the -O subtype EFMCu ports This object is read-write for the -O subtype EFMCu ports
(2BaseTL-O/10PassTS-O) and not available for the -R subtypes. (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
::= { efmCuPortConfEntry 8 } ::= { efmCuPortConfEntry 8 }
efmCuPortCapabilityTable OBJECT-TYPE efmCuPortCapabilityTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPortCapabilityEntry SYNTAX SEQUENCE OF EfmCuPortCapabilityEntry
skipping to change at page 34, line 47 skipping to change at page 35, line 19
efmCuPeerPAFSupported OBJECT-TYPE efmCuPeerPAFSupported OBJECT-TYPE
SYNTAX EfmTruthValueOrUnknown SYNTAX EfmTruthValueOrUnknown
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"PME Aggregation Function (PAF) Capability of the EFMCu port "PME Aggregation Function (PAF) Capability of the EFMCu port
(PCS) link partner. (PCS) link partner.
This object has a value of true(1) when the remote PCS can This object has a value of true(1) when the remote PCS can
perform PME aggregation on its available PMEs. perform PME aggregation on its available PMEs.
Ports whose peers are incapable of PAF, SHALL return a value Ports whose peers are incapable of PAF SHALL return a value
of false(2). of false(2).
Ports whose peers cannot be reached because of the link Ports whose peers cannot be reached because of the link
state, SHALL return a value if unknown(0). state SHALL return a value of unknown(0).
This object maps to the Clause 30 attribute This object maps to the Clause 30 attribute
aRemotePAFSupported. aRemotePAFSupported.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the Remote PAF supported bit in the this object maps to the Remote PAF supported bit in the
10P/2B capability register." 10P/2B capability register."
REFERENCE REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.9, 45.2.3.17.2" "[802.3ah] 61.2.2, 30.11.1.1.9, 45.2.3.17.2"
::= { efmCuPortCapabilityEntry 2 } ::= { efmCuPortCapabilityEntry 2 }
skipping to change at page 36, line 7 skipping to change at page 36, line 27
efmCuPortStatusTable OBJECT-TYPE efmCuPortStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPortStatusEntry SYNTAX SEQUENCE OF EfmCuPortStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides overall status information of EFMCu "This table provides overall status information of EFMCu
2BASE-TL/10PASS-TS ports, complementing the generic status 2BASE-TL/10PASS-TS ports, complementing the generic status
information from the ifTable of IF-MIB and ifMauTable of information from the ifTable of IF-MIB and ifMauTable of
MAU-MIB. Additional status information about connected PMEs MAU-MIB. Additional status information about connected PMEs
is available from efmCuPmeStatusTable. is available from the efmCuPmeStatusTable.
This table contains live data from the equipment. As such, This table contains live data from the equipment. As such,
it is NOT persistent." it is NOT persistent."
::= { efmCuPort 3 } ::= { efmCuPort 3 }
efmCuPortStatusEntry OBJECT-TYPE efmCuPortStatusEntry OBJECT-TYPE
SYNTAX EfmCuPortStatusEntry SYNTAX EfmCuPortStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 37, line 4 skipping to change at page 37, line 25
noPeer(0), noPeer(0),
peerPowerLoss(1), peerPowerLoss(1),
pmeSubTypeMismatch(2), pmeSubTypeMismatch(2),
lowRate(3) lowRate(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"EFMCu (PCS) port Fault Status. This is a bitmap of possible "EFMCu (PCS) port Fault Status. This is a bitmap of possible
conditions. The various bit positions are: conditions. The various bit positions are:
noPeer - the peer PHY cannot be reached (e.g.
noPeer - peer PHY cannot be reached (e.g.
no PMEs attached, all PMEs are Down no PMEs attached, all PMEs are Down
etc.) More info is available in etc.) More info is available in
efmCuPmeFltStatus. efmCuPmeFltStatus.
peerPowerLoss - peer PHY has indicated impending unit peerPowerLoss - the peer PHY has indicated impending
failure due to loss of local power unit failure due to loss of local
('Dying Gasp'). power ('Dying Gasp').
pmeSubTypeMismatch - local PMEs in the aggregation group pmeSubTypeMismatch - local PMEs in the aggregation group
are not of the same sub-type, e.g. are not of the same sub-type, e.g.
some PMEs in the local device are -O some PMEs in the local device are -O
while others are -R subtype. while others are -R subtype.
lowRate - ifSpeed of the port reached or dropped lowRate - ifSpeed of the port reached or dropped
below efmCuThreshLowRate below efmCuThreshLowRate
This object is intended to supplement ifOperStatus object This object is intended to supplement the ifOperStatus object
in IF-MIB and ifMauMediaAvailable in MAU-MIB. in IF-MIB and ifMauMediaAvailable in MAU-MIB.
Additional information is available via efmCuPmeFltStatus Additional information is available via the efmCuPmeFltStatus
object for each PME in the aggregation group (single PME if object for each PME in the aggregation group (single PME if
PAF is disabled)." PAF is disabled)."
REFERENCE REFERENCE
"IF-MIB, ifOperStatus; MAU-MIB, ifMauMediaAvailable; "IF-MIB, ifOperStatus; MAU-MIB, ifMauMediaAvailable;
efmCuPmeFltStatus" efmCuPmeFltStatus"
::= { efmCuPortStatusEntry 1 } ::= { efmCuPortStatusEntry 1 }
efmCuPortSide OBJECT-TYPE efmCuPortSide OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
subscriber(1), subscriber(1),
skipping to change at page 38, line 12 skipping to change at page 38, line 33
aPhyEnd" aPhyEnd"
REFERENCE REFERENCE
"[802.3ah] 61.1, 30.11.1.1.2" "[802.3ah] 61.1, 30.11.1.1.2"
::= { efmCuPortStatusEntry 2 } ::= { efmCuPortStatusEntry 2 }
efmCuNumPMEs OBJECT-TYPE efmCuNumPMEs OBJECT-TYPE
SYNTAX Unsigned32 (0..32) SYNTAX Unsigned32 (0..32)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of PMEs that is currently aggregated by the local PAF "The number of PMEs that is currently aggregated by the local
(assigned to the EFMCu port using ifStackTable). PAF (assigned to the EFMCu port using the ifStackTable).
This number is never greater than efmCuPAFCapacity. This number is never greater than efmCuPAFCapacity.
This object SHALL be automatically incremented or decremented This object SHALL be automatically incremented or decremented
when a PME is added or deleted to/from the EFMCu port using when a PME is added or deleted to/from the EFMCu port using
ifStackTable." the ifStackTable."
REFERENCE REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.6" "[802.3ah] 61.2.2, 30.11.1.1.6"
::= { efmCuPortStatusEntry 3 } ::= { efmCuPortStatusEntry 3 }
efmCuPAFInErrors OBJECT-TYPE efmCuPAFInErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of fragments that have been received across the "The number of fragments that have been received across the
gamma interface with RxErr asserted and discarded. gamma interface with RxErr asserted and discarded.
This read-only counter is inactive (not incremented) when the This read-only counter is inactive (not incremented) when the
PAF is unsupported or disabled. Upon disabling the PAF, the PAF is unsupported or disabled. Upon disabling the PAF, the
counter retains its previous value. counter retains its previous value.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the 10P/2B PAF RX error register. this object maps to the 10P/2B PAF RX error register.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times re-initialization of the management system, and at other times
skipping to change at page 38, line 50 skipping to change at page 39, line 23
defined in IF-MIB." defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.21" "[802.3ah] 45.2.3.21"
::= { efmCuPortStatusEntry 4 } ::= { efmCuPortStatusEntry 4 }
efmCuPAFInSmallFragments OBJECT-TYPE efmCuPAFInSmallFragments OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of fragments smaller than minFragmentSize "The number of fragments smaller than minFragmentSize
(64 Bytes), which have been received across the gamma (64 Bytes), which have been received across the gamma
interface and discarded. interface and discarded.
This read-only counter is inactive when the PAF is This read-only counter is inactive when the PAF is
unsupported or disabled. Upon disabling the PAF, the counter unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value. retains its previous value.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the 10P/2B PAF small fragments this object maps to the 10P/2B PAF small fragments
register. register.
skipping to change at page 39, line 26 skipping to change at page 39, line 47
defined in IF-MIB." defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.22" "[802.3ah] 45.2.3.22"
::= { efmCuPortStatusEntry 5 } ::= { efmCuPortStatusEntry 5 }
efmCuPAFInLargeFragments OBJECT-TYPE efmCuPAFInLargeFragments OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of fragments larger than maxFragmentSize "The number of fragments larger than maxFragmentSize
(512 Bytes), which have been received across the gamma (512 Bytes), which have been received across the gamma
interface and discarded. interface and discarded.
This read-only counter is inactive when the PAF is This read-only counter is inactive when the PAF is
unsupported or disabled. Upon disabling the PAF, the counter unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value. retains its previous value.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the 10P/2B PAF large fragments this object maps to the 10P/2B PAF large fragments
register. register.
skipping to change at page 39, line 50 skipping to change at page 40, line 23
defined in IF-MIB." defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.23" "[802.3ah] 45.2.3.23"
::= { efmCuPortStatusEntry 6 } ::= { efmCuPortStatusEntry 6 }
efmCuPAFInBadFragments OBJECT-TYPE efmCuPAFInBadFragments OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of fragments which do not fit into the sequence "The number of fragments which do not fit into the sequence
expected by the frame assembly function, that have been expected by the frame assembly function, that have been
received across the gamma interface and discarded (the received across the gamma interface and discarded (the
frame buffer is flushed to the next valid frame start). frame buffer is flushed to the next valid frame start).
This read-only counter is inactive when the PAF is This read-only counter is inactive when the PAF is
unsupported or disabled. Upon disabling the PAF, the counter unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value. retains its previous value.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the 10P/2B PAF bad fragments this object maps to the 10P/2B PAF bad fragments
register. register.
skipping to change at page 40, line 27 skipping to change at page 40, line 48
defined in IF-MIB." defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.25" "[802.3ah] 45.2.3.25"
::= { efmCuPortStatusEntry 7 } ::= { efmCuPortStatusEntry 7 }
efmCuPAFInLostFragments OBJECT-TYPE efmCuPAFInLostFragments OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of gaps in the sequence of fragments, which have "The number of gaps in the sequence of fragments, which have
been received across the gamma interface (the frame buffer is been received across the gamma interface (the frame buffer is
flushed to the next valid frame start, when fragment/fragments flushed to the next valid frame start, when fragment/fragments
expected by the frame assembly function is/are not received). expected by the frame assembly function is/are not received).
This read-only counter is inactive when the PAF is This read-only counter is inactive when the PAF is
unsupported or disabled. Upon disabling the PAF, the counter unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value. retains its previous value.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the 10P/2B PAF lost fragment this object maps to the 10P/2B PAF lost fragment
register. register.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times re-initialization of the management system, and at other times
skipping to change at page 41, line 4 skipping to change at page 41, line 26
defined in IF-MIB." defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.26" "[802.3ah] 45.2.3.26"
::= { efmCuPortStatusEntry 8 } ::= { efmCuPortStatusEntry 8 }
efmCuPAFInLostStarts OBJECT-TYPE efmCuPAFInLostStarts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of missing StartOfPacket indicators expected by the "The number of missing StartOfPacket indicators expected by
frame assembly function. the frame assembly function.
This read-only counter is inactive when the PAF is This read-only counter is inactive when the PAF is
unsupported or disabled. Upon disabling the PAF, the counter unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value. retains its previous value.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the 10P/2B PAF lost start of fragment this object maps to the 10P/2B PAF lost start of fragment
register. register.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times re-initialization of the management system, and at other times
skipping to change at page 41, line 27 skipping to change at page 41, line 49
defined in IF-MIB." defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.27" "[802.3ah] 45.2.3.27"
::= { efmCuPortStatusEntry 9 } ::= { efmCuPortStatusEntry 9 }
efmCuPAFInLostEnds OBJECT-TYPE efmCuPAFInLostEnds OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of missing EndOfPacket indicators expected by the "The number of missing EndOfPacket indicators expected by the
frame assembly function. frame assembly function.
This read-only counter is inactive when the PAF is This read-only counter is inactive when the PAF is
unsupported or disabled. Upon disabling the PAF, the counter unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value. retains its previous value.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the 10P/2B PAF lost start of fragment this object maps to the 10P/2B PAF lost start of fragment
register. register.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
skipping to change at page 41, line 50 skipping to change at page 42, line 23
defined in IF-MIB." defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.28" "[802.3ah] 45.2.3.28"
::= { efmCuPortStatusEntry 10 } ::= { efmCuPortStatusEntry 10 }
efmCuPAFInOverflows OBJECT-TYPE efmCuPAFInOverflows OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of fragments, received across the gamma interface "The number of fragments, received across the gamma interface
and discarded, which would have caused the frame assembly and discarded, which would have caused the frame assembly
buffer to overflow. buffer to overflow.
This read-only counter is inactive when the PAF is This read-only counter is inactive when the PAF is
unsupported or disabled. Upon disabling the PAF, the counter unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value. retains its previous value.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the 10P/2B PAF overflow register. this object maps to the 10P/2B PAF overflow register.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
skipping to change at page 42, line 34 skipping to change at page 43, line 7
efmCuPmeLineAtnCrossing NOTIFICATION-TYPE efmCuPmeLineAtnCrossing NOTIFICATION-TYPE
OBJECTS { OBJECTS {
efmCuPmeLineAtn, efmCuPmeLineAtn,
efmCuPmeThreshLineAtn efmCuPmeThreshLineAtn
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that the loop attenuation "This notification indicates that the loop attenuation
threshold (as per the efmCuPmeThreshLineAtn threshold (as per the efmCuPmeThreshLineAtn
value) has been reached/exceeded for the 2BASE-TL/10PASS-TS value) has been reached/exceeded for the 2BASE-TL/10PASS-TS
PME. This notification MAY be send on the crossing event in PME. This notification MAY be sent on the crossing event in
both directions: from normal to exceeded and from exceeded both directions: from normal to exceeded and from exceeded
to normal. to normal.
It is RECOMMENDED that a small debouncing period of 2.5 sec, It is RECOMMENDED that a small debouncing period of 2.5 sec,
between the detection of the condition and notification, between the detection of the condition and the notification,
is implemented to prevent intermittent notifications to be is implemented to prevent intermittent notifications to be
sent. sent.
Generation of this notification is controlled by the Generation of this notification is controlled by the
efmCuPmeLineAtnCrossingEnable object." efmCuPmeLineAtnCrossingEnable object."
::= { efmCuPmeNotifications 1 } ::= { efmCuPmeNotifications 1 }
efmCuPmeSnrMgnCrossing NOTIFICATION-TYPE efmCuPmeSnrMgnCrossing NOTIFICATION-TYPE
OBJECTS { OBJECTS {
efmCuPmeSnrMgn, efmCuPmeSnrMgn,
efmCuPmeThreshSnrMgn efmCuPmeThreshSnrMgn
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that the SNR margin threshold "This notification indicates that the SNR margin threshold
(as per the efmCuPmeThreshSnrMgn value) has been (as per the efmCuPmeThreshSnrMgn value) has been
reached/exceeded for the 2BASE-TL/10PASS-TS PME. reached/exceeded for the 2BASE-TL/10PASS-TS PME.
This notification MAY be send on the crossing event in This notification MAY be sent on the crossing event in
both directions: from normal to exceeded and from exceeded both directions: from normal to exceeded and from exceeded
to normal. to normal.
It is RECOMMENDED that a small debouncing period of 2.5 sec, It is RECOMMENDED that a small debouncing period of 2.5 sec,
between the detection of the condition and notification, between the detection of the condition and the notification,
is implemented to prevent intermittent notifications to be is implemented to prevent intermittent notifications to be
sent. sent.
Generation of this notification is controlled by the Generation of this notification is controlled by the
efmCuPmeSnrMgnCrossingEnable object." efmCuPmeSnrMgnCrossingEnable object."
::= { efmCuPmeNotifications 2 } ::= { efmCuPmeNotifications 2 }
efmCuPmeDeviceFault NOTIFICATION-TYPE efmCuPmeDeviceFault NOTIFICATION-TYPE
OBJECTS { OBJECTS {
efmCuPmeFltStatus efmCuPmeFltStatus
skipping to change at page 43, line 44 skipping to change at page 44, line 18
efmCuPmeConfigInitFailure NOTIFICATION-TYPE efmCuPmeConfigInitFailure NOTIFICATION-TYPE
OBJECTS { OBJECTS {
efmCuPmeFltStatus, efmCuPmeFltStatus,
efmCuAdminProfile, efmCuAdminProfile,
efmCuPmeAdminProfile efmCuPmeAdminProfile
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that PME initialization has "This notification indicates that PME initialization has
failed, due to inability of the PME link to achieve requested failed, due to inability of the PME link to achieve the
configuration profile. requested configuration profile.
Generation of this notification is controlled by the Generation of this notification is controlled by the
efmCuPmeConfigInitFailEnable object." efmCuPmeConfigInitFailEnable object."
::= { efmCuPmeNotifications 4 } ::= { efmCuPmeNotifications 4 }
efmCuPmeProtocolInitFailure NOTIFICATION-TYPE efmCuPmeProtocolInitFailure NOTIFICATION-TYPE
OBJECTS { OBJECTS {
efmCuPmeFltStatus, efmCuPmeFltStatus,
efmCuPmeOperSubType efmCuPmeOperSubType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that peer PME was using "This notification indicates that the peer PME was using
incompatible protocol during initialization. an incompatible protocol during initialization.
Generation of this notification is controlled by the Generation of this notification is controlled by the
efmCuPmeProtocolInitFailEnable object." efmCuPmeProtocolInitFailEnable object."
::= { efmCuPmeNotifications 5 } ::= { efmCuPmeNotifications 5 }
-- The PME group -- The PME group
efmCuPmeConfTable OBJECT-TYPE efmCuPmeConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPmeConfEntry SYNTAX SEQUENCE OF EfmCuPmeConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 45, line 33 skipping to change at page 46, line 6
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Administrative (desired) sub-type of the PME. "Administrative (desired) sub-type of the PME.
Possible values are: Possible values are:
ieee2BaseTLO - PME SHALL operate as 2BaseTL-O ieee2BaseTLO - PME SHALL operate as 2BaseTL-O
ieee2BaseTLR - PME SHALL operate as 2BaseTL-R ieee2BaseTLR - PME SHALL operate as 2BaseTL-R
ieee10PassTSO - PME SHALL operate as 10PassTS-O ieee10PassTSO - PME SHALL operate as 10PassTS-O
ieee10PassTSR - PME SHALL operate as 10PassTS-R ieee10PassTSR - PME SHALL operate as 10PassTS-R
ieee2BaseTLor10PassTSR - PME SHALL operate as 2BaseTL-R or ieee2BaseTLor10PassTSR - PME SHALL operate as 2BaseTL-R or
10PassTS-R. Actual value will be 10PassTS-R. The actual value will
set by -O link partner during be set by the -O link partner
initialization (handshake). during initialization (handshake).
ieee2BaseTLor10PassTSO - PME SHALL operate as 2BaseTL-O ieee2BaseTLor10PassTSO - PME SHALL operate as 2BaseTL-O
(preferred) or 10PassTS-O. Actual (preferred) or 10PassTS-O. The
value will be set during actual value will be set during
initialization depending on -R initialization depending on the -R
link partner capability (i.e. if link partner capability (i.e. if
-R is incapable of the preferred -R is incapable of the preferred
2BaseTL mode, 10PassTS will be 2BaseTL mode, 10PassTS will be
used). used).
ieee10PassTSor2BaseTLO - PME SHALL operate as 10PassTS-O ieee10PassTSor2BaseTLO - PME SHALL operate as 10PassTS-O
(preferred) or 2BaseTL-O. Actual (preferred) or 2BaseTL-O. The
value will be set during actual value will be set during
initialization depending on -R initialization depending on the -R
link partner capability (i.e. if link partner capability (i.e. if
-R is incapable of the preferred -R is incapable of the preferred
10PassTS mode, 2BaseTL will be 10PassTS mode, 2BaseTL will be
used). used).
Changing efmCuPmeAdminSubType is a traffic disruptive Changing efmCuPmeAdminSubType is a traffic disruptive
operation and as such SHALL be done when the link is Down. operation and as such SHALL be done when the link is Down.
Attempts to change this object SHALL be rejected if the link Attempts to change this object SHALL be rejected if the link
is Up or Initializing. is Up or Initializing.
Attempts to change this object to an unsupported subtype Attempts to change this object to an unsupported subtype
(see efmCuPmeSubTypesSupported) SHALL be rejected. (see efmCuPmeSubTypesSupported) SHALL be rejected.
The current operational sub type is indicated by The current operational sub type is indicated by the
efmCuPmeOperSubType variable. efmCuPmeOperSubType variable.
If a Clause 45 MDIO Interface to the PMA/PMD is present, then If a Clause 45 MDIO Interface to the PMA/PMD is present, then
this object combines values of the Port sub-type select bits this object combines values of the Port sub-type select bits
and the PMA/PMD type selection bits in the 10P/2B PMA/PMD and the PMA/PMD type selection bits in the 10P/2B PMA/PMD
control register" control register"
REFERENCE REFERENCE
"[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7" "[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7"
::= { efmCuPmeConfEntry 1 } ::= { efmCuPmeConfEntry 1 }
efmCuPmeAdminProfile OBJECT-TYPE efmCuPmeAdminProfile OBJECT-TYPE
SYNTAX EfmProfileIndexOrZero SYNTAX EfmProfileIndexOrZero
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Desired PME configuration Profile. This object is a pointer "Desired PME configuration profile. This object is a pointer
to an entry in either efmCuPme2BProfileTable or to an entry in either the efmCuPme2BProfileTable or the
efmCuPme10PProfileTable, depending on the current operating efmCuPme10PProfileTable, depending on the current operating
SubType of the PME. The value of this object is the index of SubType of the PME. The value of this object is the index of
the referenced profile. the referenced profile.
The value of zero (default) indicates that the PME is The value of zero (default) indicates that the PME is
configured via efmCuAdminProfile object for the PCS port, configured via the efmCuAdminProfile object for the PCS port
to which this PME is assigned. That is, the profile referenced to which this PME is assigned. That is, the profile referenced
by efmCuPmeAdminProfile takes precedence over the profile(s) by efmCuPmeAdminProfile takes precedence over the profile(s)
referenced by efmCuAdminProfile. referenced by efmCuAdminProfile.
This object is writable and readable for the CO subtype PMEs This object is writable and readable for the CO subtype PMEs
(2BaseTL-O or 10PassTS-O). It is irrelevant for the CPE (2BaseTL-O or 10PassTS-O). It is irrelevant for the CPE
subtype (2BaseTL-R or 10PassTS-R) - a zero value SHALL be subtype (2BaseTL-R or 10PassTS-R) - a zero value SHALL be
returned on an attempt to read this object and any attempt returned on an attempt to read this object and any attempt
to change this object MUST be rejected in this case. to change this object MUST be rejected in this case.
Note that current operational Profile value is available via Note that the current operational profile value is available
efmCuPmeOperProfile object. via efmCuPmeOperProfile object.
Modification of this object MUST be performed when the link is Any modification of this object MUST be performed when the
Down. Attempts to change this object MUST be rejected, if the link is Down. Attempts to change this object MUST be rejected,
link is Up or Initializing. if the link is Up or Initializing.
Attempts to set this object to a value that is not the value Attempts to set this object to a value that is not the value
of the index for an active entry in the corresponding profile of the index for an active entry in the corresponding profile
table, MUST be rejected." table MUST be rejected.
This object maps to the Clause 30 attribute aProfileSelect.
This object MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"[802.3ah] 30.11.2.1.6" "[802.3ah] 30.11.2.1.6"
DEFVAL { 0 } DEFVAL { 0 }
::= { efmCuPmeConfEntry 2 } ::= { efmCuPmeConfEntry 2 }
efmCuPAFRemoteDiscoveryCode OBJECT-TYPE efmCuPAFRemoteDiscoveryCode OBJECT-TYPE
SYNTAX PhysAddress (SIZE(0|6)) SYNTAX PhysAddress (SIZE(0|6))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"PAF Remote Discovery Code of the PME port at CO. "PAF Remote Discovery Code of the PME port at the CO.
A 6 octet long Discovery Code of the peer PCS connected via The 6 octet long Discovery Code of the peer PCS connected via
the PME. the PME.
Reading this object results in a Discovery Get operation. Reading this object results in a Discovery Get operation.
Setting this object to all zeroes results in a Discovery Setting this object to all zeroes results in a Discovery
Clear_if_Same operation (the value of efmCuPAFDiscoveryCode Clear_if_Same operation (the value of efmCuPAFDiscoveryCode
at the peer PCS SHALL be the same as efmCuPAFDiscoveryCode of at the peer PCS SHALL be the same as efmCuPAFDiscoveryCode of
the local PCS associated with the PME for the operation to the local PCS associated with the PME for the operation to
succeed). succeed).
Writing a non-zero value to this object results in a Writing a non-zero value to this object results in a
Discovery Set_if_Clear operation. Discovery Set_if_Clear operation.
A zero-length octet string SHALL be returned on an attempt to A zero-length octet string SHALL be returned on an attempt to
read this object when PAF aggregation is not enabled. read this object when PAF aggregation is not enabled.
This object is irrelevant in CPE port (-R) subtypes: in this This object is irrelevant in CPE port (-R) subtypes: in this
case a zero length octet string SHALL be returned on an case a zero-length octet string SHALL be returned on an
attempt to read this object, writing to this object SHALL attempt to read this object, writing to this object SHALL
be rejected. be rejected.
Discovery MUST be performed when the link is Down. Discovery MUST be performed when the link is Down.
Attempts to change this object MUST be rejected (in case of Attempts to change this object MUST be rejected (in case of
SNMP with the error inconsistentValue), if the link is Up or SNMP with the error inconsistentValue), if the link is Up or
Initializing. Initializing.
If a Clause 45 MDIO Interface to the PMA/PMD is present, then If a Clause 45 MDIO Interface to the PMA/PMD is present, then
this object is a function of 10P/2B aggregation discovery this object is a function of 10P/2B aggregation discovery
skipping to change at page 48, line 41 skipping to change at page 49, line 19
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Desired SNR Margin Threshold for the 2B/10P PME. "Desired SNR Margin Threshold for the 2B/10P PME.
This object configures the SNR margin alarm threshold. This object configures the SNR margin alarm threshold.
When the current value of SNR Margin reaches or exceeds this When the current value of SNR Margin reaches or exceeds this
threshold, a efmCuPmeSnrMgnCrossing notification MAY be threshold, a efmCuPmeSnrMgnCrossing notification MAY be
generated, if enabled by efmCuPmeSnrMgnCrossingEnable. generated, if enabled by efmCuPmeSnrMgnCrossingEnable.
This object is writable for the CO subtype PMEs This object is writable for the CO subtype PMEs
(2BaseTL-O/10PassTS-R). It is read-only for the CPE subtype (2BaseTL-O/10PassTS-O). It is read-only for the CPE subtype
(2BaseTL-R/10PassTS-R). (2BaseTL-R/10PassTS-R).
Changing of the SNR Margin Threshold MUST be performed when Changing of the SNR Margin Threshold MUST be performed when
the link is Down. Attempts to change this object MUST be the link is Down. Attempts to change this object MUST be
rejected (in case of SNMP with the error inconsistentValue), rejected (in case of SNMP with the error inconsistentValue),
if the link is Up or Initializing. if the link is Up or Initializing.
If a Clause 45 MDIO Interface to the PME is present, then this If a Clause 45 MDIO Interface to the PME is present, then this
object maps to the SNR margin threshold bits in the 2B PMD object maps to the SNR margin threshold bits in the 2B PMD
line quality thresholds register" line quality thresholds register"
skipping to change at page 49, line 16 skipping to change at page 49, line 42
::= { efmCuPmeConfEntry 5 } ::= { efmCuPmeConfEntry 5 }
efmCuPmeLineAtnCrossingEnable OBJECT-TYPE efmCuPmeLineAtnCrossingEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether efmCuPmeLineAtnCrossing notifications "Indicates whether efmCuPmeLineAtnCrossing notifications
should be generated for this interface. should be generated for this interface.
Value of true(1) indicates that efmCuPmeLineAtnCrossing A value of true(1) indicates that efmCuPmeLineAtnCrossing
notification is enabled. Value of false(2) indicates that notification is enabled. Value of false(2) indicates that
the notification is disabled." the notification is disabled."
::= { efmCuPmeConfEntry 6 } ::= { efmCuPmeConfEntry 6 }
efmCuPmeSnrMgnCrossingEnable OBJECT-TYPE efmCuPmeSnrMgnCrossingEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether efmCuPmeSnrMgnCrossing notifications "Indicates whether efmCuPmeSnrMgnCrossing notifications
should be generated for this interface. should be generated for this interface.
Value of true(1) indicates that efmCuPmeSnrMgnCrossing A value of true(1) indicates that efmCuPmeSnrMgnCrossing
notification is enabled. Value of false(2) indicates that notification is enabled. Value of false(2) indicates that
the notification is disabled." the notification is disabled."
::= { efmCuPmeConfEntry 7 } ::= { efmCuPmeConfEntry 7 }
efmCuPmeDeviceFaultEnable OBJECT-TYPE efmCuPmeDeviceFaultEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether efmCuPmeDeviceFault notifications "Indicates whether efmCuPmeDeviceFault notifications
should be generated for this interface. should be generated for this interface.
Value of true(1) indicates that efmCuPmeDeviceFault A value of true(1) indicates that efmCuPmeDeviceFault
notification is enabled. Value of false(2) indicates that notification is enabled. Value of false(2) indicates that
the notification is disabled." the notification is disabled."
::= { efmCuPmeConfEntry 8 } ::= { efmCuPmeConfEntry 8 }
efmCuPmeConfigInitFailEnable OBJECT-TYPE efmCuPmeConfigInitFailEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether efmCuPmeConfigInitFailure notifications "Indicates whether efmCuPmeConfigInitFailure notifications
should be generated for this interface. should be generated for this interface.
Value of true(1) indicates that efmCuPmeConfigInitFailure A value of true(1) indicates that efmCuPmeConfigInitFailure
notification is enabled. Value of false(2) indicates that notification is enabled. A value of false(2) indicates that
the notification is disabled." the notification is disabled."
::= { efmCuPmeConfEntry 9 } ::= { efmCuPmeConfEntry 9 }
efmCuPmeProtocolInitFailEnable OBJECT-TYPE efmCuPmeProtocolInitFailEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether efmCuPmeProtocolInitFailure notifications "Indicates whether efmCuPmeProtocolInitFailure notifications
should be generated for this interface. should be generated for this interface.
Value of true(1) indicates that efmCuPmeProtocolInitFailure A value of true(1) indicates that efmCuPmeProtocolInitFailure
notification is enabled. Value of false(2) indicates that notification is enabled. A value of false(2) indicates that
the notification is disabled." the notification is disabled."
::= { efmCuPmeConfEntry 10 } ::= { efmCuPmeConfEntry 10 }
efmCuPmeCapabilityTable OBJECT-TYPE efmCuPmeCapabilityTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPmeCapabilityEntry SYNTAX SEQUENCE OF EfmCuPmeCapabilityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table for Configuration of common aspects for EFMCu "Table for the configuration of common aspects for EFMCu
2BASE-TL/10PASS-TS PME ports (modems). Configuration of 2BASE-TL/10PASS-TS PME ports (modems). The configuration of
aspects specific to 2BASE-TL or 10PASS-TS PME types is aspects specific to 2BASE-TL or 10PASS-TS PME types is
represented in efmCuPme2BConfTable and efmCuPme10PConfTable represented in the efmCuPme2BConfTable and the
respectively. efmCuPme10PConfTable, respectively.
Entries in this table MUST be maintained in a persistent Entries in this table MUST be maintained in a persistent
manner." manner."
::= { efmCuPme 2 } ::= { efmCuPme 2 }
efmCuPmeCapabilityEntry OBJECT-TYPE efmCuPmeCapabilityEntry OBJECT-TYPE
SYNTAX EfmCuPmeCapabilityEntry SYNTAX EfmCuPmeCapabilityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 51, line 28 skipping to change at page 52, line 6
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"PME supported sub-types. This is a bitmap of possible "PME supported sub-types. This is a bitmap of possible
sub-types. The various bit positions are: sub-types. The various bit positions are:
ieee2BaseTLO - PME is capable of operating as 2BaseTL-O ieee2BaseTLO - PME is capable of operating as 2BaseTL-O
ieee2BaseTLR - PME is capable of operating as 2BaseTL-R ieee2BaseTLR - PME is capable of operating as 2BaseTL-R
ieee10PassTSO - PME is capable of operating as 10PassTS-O ieee10PassTSO - PME is capable of operating as 10PassTS-O
ieee10PassTSR - PME is capable of operating as 10PassTS-R ieee10PassTSR - PME is capable of operating as 10PassTS-R
An desired mode of operation is determined by The desired mode of operation is determined by
efmCuPmeAdminSubType, while efmCuPmeOperSubType reflects the efmCuPmeAdminSubType, while efmCuPmeOperSubType reflects the
current operating mode. current operating mode.
If a Clause 45 MDIO Interface to the PCS is present, then this If a Clause 45 MDIO Interface to the PCS is present, then this
object combines the 10PASS-TS capable and 2BASE-TL capable object combines the 10PASS-TS capable and 2BASE-TL capable
bits in the 10P/2B PMA/PMD speed ability register and the bits in the 10P/2B PMA/PMD speed ability register and the
CO supported and CPE supported bits in the 10P/2B PMA/PMD CO supported and CPE supported bits in the 10P/2B PMA/PMD
status register" status register"
REFERENCE REFERENCE
"[802.3ah] 61.1, 45.2.1.4.1, 45.2.1.4.2, 45.2.1.12.2, "[802.3ah] 61.1, 45.2.1.4.1, 45.2.1.4.2, 45.2.1.12.2,
skipping to change at page 52, line 48 skipping to change at page 53, line 25
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), up(1),
downNotReady(2), downNotReady(2),
downReady(3), downReady(3),
init(4) init(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Current PME link Operational Status. Possible values are: "Current PME link Operational Status. Possible values are:
up(1) - link is Up and ready to pass 64/65B up(1) - The link is Up and ready to pass 64/65B
encoded frames or fragments. encoded frames or fragments.
downNotReady(2) - link is Down and the PME does not detect downNotReady(2) - The link is Down and the PME does not
Handshake tones from its peer. This value detect Handshake tones from its peer. This
may indicate a possible problem with value may indicate a possible problem with
the peer PME. the peer PME.
downReady(3) - link is Down and the PME detects Handshake downReady(3) - The link is Down and the PME detects
tones from its peer. Handshake tones from its peer.
init(4) - link is initializing, as a result of init(4) - The link is initializing, as a result of
ifAdminStatus being set to 'up' for a ifAdminStatus being set to 'up' for a
particular PME or a PCS the PME is particular PME or a PCS the PME is
connected to. connected to.
This object is intended to supplement Down state of This object is intended to supplement the Down(2) state of
ifOperStatus. ifOperStatus.
This object partially maps to the Clause 30 attribute This object partially maps to the Clause 30 attribute
aPMEStatus. aPMEStatus.
If a Clause 45 MDIO Interface to the PME is present, then this If a Clause 45 MDIO Interface to the PME is present, then this
object partially maps to PMA/PMD link status bits in 10P/2B object partially maps to PMA/PMD link status bits in 10P/2B
PMA/PMD status register." PMA/PMD status register."
REFERENCE REFERENCE
"[802.3ah] 30.11.2.1.3, 45.2.1.12.4" "[802.3ah] 30.11.2.1.3, 45.2.1.12.4"
skipping to change at page 53, line 50 skipping to change at page 54, line 28
lossOfFraming - Loss of Framing for 10P or lossOfFraming - Loss of Framing for 10P or
Loss of Sync word for 2B PMD or Loss of Sync word for 2B PMD or
Loss of 64/65B Framing Loss of 64/65B Framing
snrMgnDefect - SNR Margin dropped below the Threshold snrMgnDefect - SNR Margin dropped below the Threshold
lineAtnDefect - Line Attenuation exceeds the Threshold lineAtnDefect - Line Attenuation exceeds the Threshold
deviceFault - Indicates a vendor-dependent deviceFault - Indicates a vendor-dependent
diagnostic or self-test fault diagnostic or self-test fault
has been detected. has been detected.
configInitFailure - Configuration initialization failure, configInitFailure - Configuration initialization failure,
due to inability of the PME link to due to inability of the PME link to
support configuration profile, support the configuration profile,
requested during initialization. requested during initialization.
protocolInitFailure - Protocol initialization failure, due
protocolInitFailure - Protocol initialization failure, to an incompatible protocol used by
due to incompatible protocol used by
the Peer PME during init (that could the Peer PME during init (that could
happen if a peer PMD is a regular happen if a peer PMD is a regular
G.SDHSL/VDSL modem instead of a G.SDHSL/VDSL modem instead of a
2BASE-TL/10PASS-TS PME). 2BASE-TL/10PASS-TS PME).
This object is intended to supplement ifOperStatus in IF-MIB. This object is intended to supplement ifOperStatus in IF-MIB.
This object holds information about the last fault. This object holds information about the last fault.
efmCuPmeFltStatus is cleared by the device restart. efmCuPmeFltStatus is cleared by the device restart.
In addition lossOfFraming, configInitFailure and In addition, lossOfFraming, configInitFailure, and
protocolInitFailure are cleared by PME init. protocolInitFailure are cleared by PME init;
deviceFault is cleared by successful diagnostics/test. deviceFault is cleared by successful diagnostics/test;
snrMgnDefect and lineAtnDefect are cleared by SNR Margin snrMgnDefect and lineAtnDefect are cleared by SNR Margin
and line Attenuation respectively returning to norm and by and line Attenuation respectively returning to norm and by
PME init. PME init.
This object partially maps to the Clause 30 attribute This object partially maps to the Clause 30 attribute
aPMEStatus. aPMEStatus.
If a Clause 45 MDIO Interface to the PME is present, then this If a Clause 45 MDIO Interface to the PME is present, then this
object consolidates information from various PMA/PMD object consolidates information from various PMA/PMD
registers, namely: Fault bit in PMA/PMD status 1 register, registers, namely: Fault bit in PMA/PMD status 1 register,
skipping to change at page 55, line 6 skipping to change at page 55, line 32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Current operational sub-type of the PME. "Current operational sub-type of the PME.
Possible values are: Possible values are:
ieee2BaseTLO - PME operates as 2BaseTL-O ieee2BaseTLO - PME operates as 2BaseTL-O
ieee2BaseTLR - PME operates as 2BaseTL-R ieee2BaseTLR - PME operates as 2BaseTL-R
ieee10PassTSO - PME operates as 10PassTS-O ieee10PassTSO - PME operates as 10PassTS-O
ieee10PassTSR - PME operates as 10PassTS-R ieee10PassTSR - PME operates as 10PassTS-R
The operational sub type of the PME can be configured via The desired operational sub type of the PME can be configured
efmCuPmeAdminSubType variable. via the efmCuPmeAdminSubType variable.
If a Clause 45 MDIO Interface to the PMA/PMD is present, then If a Clause 45 MDIO Interface to the PMA/PMD is present, then
this object combines values of the Port sub-type select this object combines values of the Port sub-type select
bits, the PMA/PMD type selection bits in the 10P/2B bits, the PMA/PMD type selection bits in the 10P/2B
PMA/PMD control register and the PMA/PMD link status bits in PMA/PMD control register and the PMA/PMD link status bits in
the 10P/2B PMA/PMD status register." the 10P/2B PMA/PMD status register."
REFERENCE REFERENCE
"[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7, 45.2.1.12.4" "[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7, 45.2.1.12.4"
::= { efmCuPmeStatusEntry 3 } ::= { efmCuPmeStatusEntry 3 }
efmCuPmeOperProfile OBJECT-TYPE efmCuPmeOperProfile OBJECT-TYPE
SYNTAX EfmProfileIndexOrZero SYNTAX EfmProfileIndexOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"PME current operating Profile. This object is a pointer to "PME current operating profile. This object is a pointer to
an entry in either efmCuPme2BProfileTable or an entry in either the efmCuPme2BProfileTable or the
efmCuPme10PProfileTable, depending on the current efmCuPme10PProfileTable, depending on the current operating
operating SubType of the PME as indicated by SubType of the PME as indicated by efmCuPmeOperSubType.
efmCuPmeOperSubType. Note that a profile entry to which efmCuPmeOperProfile is
Note that a profile entry, to which efmCuPmeOperProfile is pointing to can be created automatically to reflect achieved
pointing to, can be created automatically, to reflect achieved
parameters in adaptive (not fixed) initialization, parameters in adaptive (not fixed) initialization,
i.e. values of efmCuPmeOperProfile and efmCuAdminProfile or i.e. values of efmCuPmeOperProfile and efmCuAdminProfile or
efmCuPmeAdminProfile may differ. efmCuPmeAdminProfile may differ.
The value of zero indicates that PME is down or initializing. The value of zero indicates that the PME is down or
initializing.
This object partially maps to the aOperatingProfile This object partially maps to the aOperatingProfile attribute
attribute in Clause 30." in Clause 30."
REFERENCE REFERENCE
"[802.3ah] 30.11.2.1.7" "[802.3ah] 30.11.2.1.7"
::= { efmCuPmeStatusEntry 4 } ::= { efmCuPmeStatusEntry 4 }
efmCuPmeSnrMgn OBJECT-TYPE efmCuPmeSnrMgn OBJECT-TYPE
SYNTAX Integer32(-127..128|65535) SYNTAX Integer32(-127..128|65535)
UNITS "dB" UNITS "dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current Signal-to-Noise Ratio (SNR) margin with respect "The current Signal-to-Noise Ratio (SNR) margin with respect
to the received signal as perceived by the local PME. to the received signal as perceived by the local PME.
The value of 65535 is returned when PME is down or The value of 65535 is returned when the PME is down or
initializing. initializing.
This object maps to the aPMESNRMgn attribute in Clause 30. This object maps to the aPMESNRMgn attribute in Clause 30.
If a Clause 45 MDIO Interface is present, then this If a Clause 45 MDIO Interface is present, then this
object maps to the 10P/2B RX SNR margin register." object maps to the 10P/2B RX SNR margin register."
REFERENCE REFERENCE
"[802.3ah] 30.11.2.1.4, 45.2.1.16" "[802.3ah] 30.11.2.1.4, 45.2.1.16"
::= { efmCuPmeStatusEntry 5 } ::= { efmCuPmeStatusEntry 5 }
efmCuPmePeerSnrMgn OBJECT-TYPE efmCuPmePeerSnrMgn OBJECT-TYPE
SYNTAX Integer32(-127..128|65535) SYNTAX Integer32(-127..128|65535)
UNITS "dB" UNITS "dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current SNR margin in dB with respect to the received "The current SNR margin in dB with respect to the received
signal, as perceived by the remote (link partner) PME. signal, as perceived by the remote (link partner) PME.
The value of 65535 is returned when PME is down or The value of 65535 is returned when the PME is down or
initializing. initializing.
This object is irrelevant for the -R PME subtypes. The value This object is irrelevant for the -R PME subtypes. The value
of 65535 SHALL be returned in this case. of 65535 SHALL be returned in this case.
If a Clause 45 MDIO Interface is present, then this If a Clause 45 MDIO Interface is present, then this
object maps to the 10P/2B link partner RX SNR margin object maps to the 10P/2B link partner RX SNR margin
register." register."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.17" "[802.3ah] 45.2.1.17"
::= { efmCuPmeStatusEntry 6} ::= { efmCuPmeStatusEntry 6}
efmCuPmeLineAtn OBJECT-TYPE efmCuPmeLineAtn OBJECT-TYPE
SYNTAX Integer32(-127..128|65535) SYNTAX Integer32(-127..128|65535)
UNITS "dB" UNITS "dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current Line Attenuation in dB as perceived by the local "The current Line Attenuation in dB as perceived by the local
PME. PME.
The value of 65535 is returned when PME is down or The value of 65535 is returned when the PME is down or
initializing. initializing.
If a Clause 45 MDIO Interface is present, then this If a Clause 45 MDIO Interface is present, then this
object maps to the Line Attenuation register" object maps to the Line Attenuation register"
REFERENCE REFERENCE
"[802.3ah] 45.2.1.18" "[802.3ah] 45.2.1.18"
::= { efmCuPmeStatusEntry 7 } ::= { efmCuPmeStatusEntry 7 }
efmCuPmePeerLineAtn OBJECT-TYPE efmCuPmePeerLineAtn OBJECT-TYPE
SYNTAX Integer32(-127..128|65535) SYNTAX Integer32(-127..128|65535)
UNITS "dB" UNITS "dB"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current Line Attenuation in dB as perceived by the remote "The current Line Attenuation in dB as perceived by the remote
(link partner) PME. (link partner) PME.
The value of 65535 is returned when PME is down or The value of 65535 is returned when the PME is down or
initializing. initializing.
This object is irrelevant for the -R PME subtypes. The value This object is irrelevant for the -R PME subtypes. The value
of 65535 SHALL be returned in this case. of 65535 SHALL be returned in this case.
If a Clause 45 MDIO Interface is present, then this If a Clause 45 MDIO Interface is present, then this
object maps to the 20P/2B link partner Line Attenuation object maps to the 20P/2B link partner Line Attenuation
register." register."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.19" "[802.3ah] 45.2.1.19"
::= { efmCuPmeStatusEntry 8 } ::= { efmCuPmeStatusEntry 8 }
efmCuPmeEquivalentLength OBJECT-TYPE efmCuPmeEquivalentLength OBJECT-TYPE
SYNTAX Unsigned32(0..8192|65535) SYNTAX Unsigned32(0..8192|65535)
UNITS "m" UNITS "m"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An estimate of the equivalent loop's Physical Length in "An estimate of the equivalent loop's physical length in
meters, as perceived by the PME after the link is established. meters, as perceived by the PME after the link is established.
An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a
perfect square root attenuation characteristic, without any perfect square root attenuation characteristic, without any
bridged taps. bridged taps.
The value of 65535 is returned if the link is Down or The value of 65535 is returned if the link is Down or
Initializing or the PME is unable to estimate the Equivalent Initializing or the PME is unable to estimate the equivalent
Length. length.
For 10BASE-TL PME, if a Clause 45 MDIO Interface to the PME is For a 10BASE-TL PME, if a Clause 45 MDIO Interface to the PME
present, then this object maps to the 10P Electrical Length is present, then this object maps to the 10P Electrical Length
register" register"
REFERENCE REFERENCE
"[802.3ah] 45.2.1.21" "[802.3ah] 45.2.1.21"
::= { efmCuPmeStatusEntry 9 } ::= { efmCuPmeStatusEntry 9 }
efmCuPmeTCCodingErrors OBJECT-TYPE efmCuPmeTCCodingErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of 64/65-octet encapsulation errors. This counter is "The number of 64/65-octet encapsulation errors. This counter
incremented for each 64/65-octet encapsulation error detected is incremented for each 64/65-octet encapsulation error
by the 64/65-octet receive function. detected by the 64/65-octet receive function.
This object maps to aTCCodingViolations attribute in This object maps to aTCCodingViolations attribute in
clause 30. Clause 30.
If a Clause 45 MDIO Interface to the PME TC is present, then If a Clause 45 MDIO Interface to the PME TC is present, then
this object maps to the TC coding violations register this object maps to the TC coding violations register
(see 45.2.6.12). (see 45.2.6.12).
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime, as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB." defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 61.3.3.1, 30.11.2.1.5, 45.2.6.12" "[802.3ah] 61.3.3.1, 30.11.2.1.5, 45.2.6.12"
::= { efmCuPmeStatusEntry 10 } ::= { efmCuPmeStatusEntry 10 }
efmCuPmeTCCrcErrors OBJECT-TYPE efmCuPmeTCCrcErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of TC-CRC errors. This counter is incremented for "The number of TC-CRC errors. This counter is incremented for
each TC-CRC error detected by the 64/65-octet receive function each TC-CRC error detected by the 64/65-octet receive function
(see 61.3.3.3 and Figure 61-19). (see 61.3.3.3 and Figure 61-19).
This object maps to aTCCRCErrors attribute in This object maps to aTCCRCErrors attribute in
clause 30. Clause 30.
If a Clause 45 MDIO Interface to the PCME TC is present, then If a Clause 45 MDIO Interface to the PME TC is present, then
this object maps to the TC CRC error register this object maps to the TC CRC error register
(see 45.2.6.11). (see 45.2.6.11).
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime, as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB." defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 61.3.3.3, 30.11.2.1.10, 45.2.6.11" "[802.3ah] 61.3.3.3, 30.11.2.1.10, 45.2.6.11"
::= { efmCuPmeStatusEntry 11 } ::= { efmCuPmeStatusEntry 11 }
skipping to change at page 59, line 7 skipping to change at page 59, line 33
-- 2BASE-TL specific PME group -- 2BASE-TL specific PME group
efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 } efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 }
efmCuPme2BProfileTable OBJECT-TYPE efmCuPme2BProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme2BProfileEntry SYNTAX SEQUENCE OF EfmCuPme2BProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table supports definitions of administrative and "This table supports definitions of administrative and
operating Profiles for 2BASE-TL PMEs. operating profiles for 2BASE-TL PMEs.
First 14 entries in this table SHALL always be defined as The first 14 entries in this table SHALL always be defined as
follows (see 802.3ah Annex 63A): follows (see 802.3ah Annex 63A):
-------+-------+-------+-----+------+------------------ -------+-------+-------+-----+------+-------------+-----------
Profile MinRate MaxRate Power Region Constellation Profile MinRate MaxRate Power Region Constellation Comment
index (Kbps) (Kbps) (dBm) index (Kbps) (Kbps) (dBm)
-------+-------+-------+-----+------+------------------ -------+-------+-------+-----+------+-------------+-----------
1 5696 5696 13.5 1 32-TCPAM (default) 1 5696 5696 13.5 1 32-TCPAM default
2 3072 3072 13.5 1 32-TCPAM 2 3072 3072 13.5 1 32-TCPAM
3 2048 2048 13.5 1 16-TCPAM 3 2048 2048 13.5 1 16-TCPAM
4 1024 1024 13.5 1 16-TCPAM 4 1024 1024 13.5 1 16-TCPAM
5 704 704 13.5 1 16-TCPAM 5 704 704 13.5 1 16-TCPAM
6 512 512 13.5 1 16-TCPAM 6 512 512 13.5 1 16-TCPAM
7 5696 5696 14.5 2 32-TCPAM 7 5696 5696 14.5 2 32-TCPAM
8 3072 3072 14.5 2 32-TCPAM 8 3072 3072 14.5 2 32-TCPAM
9 2048 2048 14.5 2 16-TCPAM 9 2048 2048 14.5 2 16-TCPAM
10 1024 1024 13.5 2 16-TCPAM 10 1024 1024 13.5 2 16-TCPAM
11 704 704 13.5 2 16-TCPAM 11 704 704 13.5 2 16-TCPAM
12 512 512 13.5 2 16-TCPAM 12 512 512 13.5 2 16-TCPAM
13 192 5696 0 1 0 (best effort) 13 192 5696 0 1 0 best effort
14 192 5696 0 2 0 (best effort) 14 192 5696 0 2 0 best effort
-------+-------+-------+-----+------+-------------+-----------
These default entries SHALL be created during agent These default entries SHALL be created during agent
initialization and MUST NOT be deleted. initialization and MUST NOT be deleted.
Entries following the first 14, can be dynamically created and Entries following the first 14 can be dynamically created and
deleted, to provide custom administrative (configuration) deleted to provide custom administrative (configuration)
profiles and automatic operating profiles. profiles and automatic operating profiles.
This table MUST be maintained in a persistent manner." This table MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"[802.3ah] Annex 63A, 30.11.2.1.6" "[802.3ah] Annex 63A, 30.11.2.1.6"
::= { efmCuPme2B 2 } ::= { efmCuPme2B 2 }
efmCuPme2BProfileEntry OBJECT-TYPE efmCuPme2BProfileEntry OBJECT-TYPE
SYNTAX EfmCuPme2BProfileEntry SYNTAX EfmCuPme2BProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry corresponds to a single 2BASE-TL PME profile. "Each entry corresponds to a single 2BASE-TL PME profile.
Each profile contains a set of parameters, used either for Each profile contains a set of parameters, used either for
configuration or representation of a 2BASE-TL PME. configuration or representation of a 2BASE-TL PME.
In case a particular profile is referenced via In case a particular profile is referenced via the
efmCuPmeAdminProfile object (or efmCuAdminProfile if efmCuPmeAdminProfile object (or efmCuAdminProfile if
efmCuPmeAdminProfile is zero), it represent the desired efmCuPmeAdminProfile is zero), it represents the desired
parameters the 2BaseTL-O PME initialization. parameters for the 2BaseTL-O PME initialization.
If a profile is referenced via efmCuPmeOperProfile object, If a profile is referenced via an efmCuPmeOperProfile object,
it represents current operating parameters of the it represents the current operating parameters of an
operational PME. operational PME.
Profiles may be created/deleted using the row creation/ Profiles may be created/deleted using the row creation/
deletion mechanism via efmCuPme2BProfileRowStatus. If an deletion mechanism via efmCuPme2BProfileRowStatus. If an
active entry is referenced, the entry MUST remain 'active' active entry is referenced, the entry MUST remain 'active'
until all references are removed. until all references are removed.
Default entries MUST NOT be removed." Default entries MUST NOT be removed."
INDEX { efmCuPme2BProfileIndex } INDEX { efmCuPme2BProfileIndex }
::= { efmCuPme2BProfileTable 1 } ::= { efmCuPme2BProfileTable 1 }
skipping to change at page 60, line 35 skipping to change at page 61, line 14
efmCuPme2BPower Unsigned32, efmCuPme2BPower Unsigned32,
efmCuPme2BConstellation INTEGER, efmCuPme2BConstellation INTEGER,
efmCuPme2BProfileRowStatus RowStatus efmCuPme2BProfileRowStatus RowStatus
} }
efmCuPme2BProfileIndex OBJECT-TYPE efmCuPme2BProfileIndex OBJECT-TYPE
SYNTAX EfmProfileIndex SYNTAX EfmProfileIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"2BASE-TL PME Profile index. "2BASE-TL PME profile index.
This object is the unique index associated with this profile. This object is the unique index associated with this profile.
Entries in this table are referenced via efmCuAdminProfile Entries in this table are referenced via efmCuAdminProfile or
or efmCuPmeAdminProfile objects." efmCuPmeAdminProfile objects."
::= { efmCuPme2BProfileEntry 1 } ::= { efmCuPme2BProfileEntry 1 }
efmCuPme2BProfileDescr OBJECT-TYPE efmCuPme2BProfileDescr OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual string containing information about 2BASE-TL PME "A textual string containing information about a 2BASE-TL PME
Profile. The string may include information about data rate profile. The string may include information about the data
and spectral limitations of this particular profile." rate and spectral limitations of this particular profile."
::= { efmCuPme2BProfileEntry 2 } ::= { efmCuPme2BProfileEntry 2 }
efmCuPme2BRegion OBJECT-TYPE efmCuPme2BRegion OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
region1(1), region1(1),
region2(2) region2(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Regional settings for 2BASE-TL PME, as specified in the "Regional settings for a 2BASE-TL PME, as specified in the
relevant Regional Annex of [G.991.2]. relevant Regional Annex of [G.991.2].
Regional settings specify Power Spectral Density (PSD) mask, Regional settings specify the Power Spectral Density (PSD)
Power Back-Off (PBO) values and place limitations on the max mask, Power Back-Off (PBO) values and place limitations on the
allowed data rate, power and constellation. max allowed data rate, power and constellation.
Possible values for this object are: Possible values for this object are:
region1 - Annexes A and F (e.g. North America) region1 - Annexes A and F (e.g. North America)
region2 - Annexes B and G (e.g. Europe) region2 - Annexes B and G (e.g. Europe)
Annex A/B specify regional settings for data rates 192-2304 Annex A/B specify regional settings for data rates 192-2304
Kbps using 16-TCPAM encoding. Kbps using 16-TCPAM encoding.
Annex F/G specify regional settings for rates 2320-3840 Kbps Annex F/G specify regional settings for rates 2320-3840 Kbps
using 16-TCPAM encoding and 768-5696 Kbps using 32-TCPAM using 16-TCPAM encoding and 768-5696 Kbps using 32-TCPAM
encoding. encoding.
skipping to change at page 61, line 39 skipping to change at page 62, line 18
parameter register." parameter register."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.42; [G.991.2] Annexes A, B, F and G" "[802.3ah] 45.2.1.42; [G.991.2] Annexes A, B, F and G"
::= { efmCuPme2BProfileEntry 3 } ::= { efmCuPme2BProfileEntry 3 }
efmCuPme2BsMode OBJECT-TYPE efmCuPme2BsMode OBJECT-TYPE
SYNTAX EfmProfileIndexOrZero SYNTAX EfmProfileIndexOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Desired custom Spectral Mode for 2BASE-TL PME. This object "Desired custom Spectral Mode for a 2BASE-TL PME. This object
is a pointer to an entry in efmCuPme2BsModeTable and a block is a pointer to an entry in efmCuPme2BsModeTable and a block
of entries in efmCuPme2BRateReachTable, which together define of entries in efmCuPme2BRateReachTable, which together define
(country-specific) reach dependent rate limitations in (country-specific) reach dependent rate limitations in
addition to those defined by efmCuPme2BRegion. addition to those defined by efmCuPme2BRegion.
The value of this object is the index of the referenced The value of this object is the index of the referenced
spectral mode. spectral mode.
The value of zero (default) indicates that no specific The value of zero (default) indicates that no specific
spectral mode is applicable. spectral mode is applicable.
Attempts to set this object to a value that is not the value Attempts to set this object to a value that is not the value
of the index for an active entry in the corresponding spectral of the index for an active entry in the corresponding spectral
mode table, MUST be rejected." mode table MUST be rejected."
REFERENCE REFERENCE
"efmCuPme2BsModeTable, efmCuPme2BRateReachTable" "efmCuPme2BsModeTable, efmCuPme2BRateReachTable"
DEFVAL { 0 } DEFVAL { 0 }
::= { efmCuPme2BProfileEntry 4 } ::= { efmCuPme2BProfileEntry 4 }
efmCuPme2BMinDataRate OBJECT-TYPE efmCuPme2BMinDataRate OBJECT-TYPE
SYNTAX Unsigned32(192..5696) SYNTAX Unsigned32(192..5696)
UNITS "Kbps" UNITS "Kbps"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 62, line 29 skipping to change at page 63, line 8
The data rate of the 2BASE-TL PME is considered 'fixed' when The data rate of the 2BASE-TL PME is considered 'fixed' when
the value of this object equals that of efmCuPme2BMaxDataRate. the value of this object equals that of efmCuPme2BMaxDataRate.
If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in
the administrative profile, the data rate is considered the administrative profile, the data rate is considered
'adaptive', and SHALL be set to the maximum attainable rate 'adaptive', and SHALL be set to the maximum attainable rate
not exceeding efmCuPme2BMaxDataRate, under the spectral not exceeding efmCuPme2BMaxDataRate, under the spectral
limitations placed by the efmCuPme2BRegion and limitations placed by the efmCuPme2BRegion and
efmCuPme2BsMode. efmCuPme2BsMode.
Note that current operational data rate of the PME is Note that the current operational data rate of the PME is
represented by ifSpeed object of IF-MIB. represented by the ifSpeed object of IF-MIB.
If a Clause 45 MDIO Interface to the PME is present, then this 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 object maps to the Min Data Rate1 bits in the 2B PMD
parameters register. parameters register.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.43" "[802.3ah] 45.2.1.43"
::= { efmCuPme2BProfileEntry 5 } ::= { efmCuPme2BProfileEntry 5 }
skipping to change at page 63, line 12 skipping to change at page 63, line 39
The data rate of the 2BASE-TL PME is considered 'fixed' when The data rate of the 2BASE-TL PME is considered 'fixed' when
the value of this object equals that of efmCuPme2BMinDataRate. the value of this object equals that of efmCuPme2BMinDataRate.
If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in
the administrative profile, the data rate is considered the administrative profile, the data rate is considered
'adaptive', and SHALL be set to the maximum attainable rate 'adaptive', and SHALL be set to the maximum attainable rate
not exceeding efmCuPme2BMaxDataRate, under the spectral not exceeding efmCuPme2BMaxDataRate, under the spectral
limitations placed by the efmCuPme2BRegion and limitations placed by the efmCuPme2BRegion and
efmCuPme2BsMode. efmCuPme2BsMode.
Note that current operational data rate of the PME is Note that the current operational data rate of the PME is
represented by ifSpeed object of IF-MIB. represented by the ifSpeed object of IF-MIB.
If a Clause 45 MDIO Interface to the PME is present, then this 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 object maps to the Max Data Rate1 bits in the 2B PMD
parameters register. parameters register.
This object MUST be maintained in a persistent manner." This object MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.43" "[802.3ah] 45.2.1.43"
::= { efmCuPme2BProfileEntry 6 } ::= { efmCuPme2BProfileEntry 6 }
skipping to change at page 64, line 27 skipping to change at page 65, line 6
parameter register." parameter register."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.43" "[802.3ah] 45.2.1.43"
::= { efmCuPme2BProfileEntry 8 } ::= { efmCuPme2BProfileEntry 8 }
efmCuPme2BProfileRowStatus OBJECT-TYPE efmCuPme2BProfileRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object controls creation, modification or deletion of "This object controls the creation, modification or deletion
the associated entry in efmCuPme2BProfileTable per the of the associated entry in the efmCuPme2BProfileTable per the
semantics of RowStatus. semantics of RowStatus.
If an 'active' entry is referenced via efmCuAdminProfile or If an 'active' entry is referenced via efmCuAdminProfile or
efmCuPmeAdminProfile, the entry MUST remain 'active' until all efmCuPmeAdminProfile instance(s), the entry MUST remain
references are removed. 'active'.
An 'active' entry SHALL NOT be modified. In order to modify an An 'active' entry SHALL NOT be modified. In order to modify an
existing entry it MUST be taken out of service (by setting existing entry it MUST be taken out of service (by setting
this object to 'notInService'), modified and set 'active' this object to 'notInService'), modified and set 'active'
again." again."
::= { efmCuPme2BProfileEntry 9 } ::= { efmCuPme2BProfileEntry 9 }
efmCuPme2BsModeTable OBJECT-TYPE efmCuPme2BsModeTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme2BsModeEntry SYNTAX SEQUENCE OF EfmCuPme2BsModeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table, together with efmCu2BReachRateTable, supports "This table, together with efmCu2BReachRateTable, supports
definition of administrative custom spectral modes for definition of administrative custom spectral modes for
2BASE-TL PMEs, describing spectral limitations in addition to 2BASE-TL PMEs, describing spectral limitations in addition to
those specified by efmCuPme2BRegion. those specified by efmCuPme2BRegion.
Some countries spectral regulations (e.g. UK ANFP) limit the In some countries, spectral regulations (e.g. UK ANFP) limit
length of the loops for certain data rates. This table allows the length of the loops for certain data rates. This table
these country-specific limitations to be specified. allows these country-specific limitations to be specified.
Entries in this table referenced by the efmCuPme2BsMode Entries in this table referenced by the efmCuPme2BsMode
MUST NOT be deleted until all the active references are MUST NOT be deleted until all the active references are
removed. removed.
This table MUST be maintained in a persistent manner." This table MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"efmCu2BReachRateTable" "efmCu2BReachRateTable"
::= { efmCuPme2B 3 } ::= { efmCuPme2B 3 }
efmCuPme2BsModeEntry OBJECT-TYPE efmCuPme2BsModeEntry OBJECT-TYPE
SYNTAX EfmCuPme2BsModeEntry SYNTAX EfmCuPme2BsModeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry specifies spectral mode description and its index, "Each entry specifies a spectral mode description and its
which is used to reference corresponding entries in the index, which is used to reference corresponding entries in the
efmCu2BReachRateTable. efmCu2BReachRateTable.
Entries may be created/deleted using the row creation/ Entries may be created/deleted using the row creation/
deletion mechanism via efmCuPme2BsModeRowStatus." deletion mechanism via efmCuPme2BsModeRowStatus."
INDEX { efmCuPme2BsModeIndex } INDEX { efmCuPme2BsModeIndex }
::= { efmCuPme2BsModeTable 1 } ::= { efmCuPme2BsModeTable 1 }
EfmCuPme2BsModeEntry ::= EfmCuPme2BsModeEntry ::=
SEQUENCE { SEQUENCE {
efmCuPme2BsModeIndex EfmProfileIndex, efmCuPme2BsModeIndex EfmProfileIndex,
skipping to change at page 65, line 47 skipping to change at page 66, line 25
} }
efmCuPme2BsModeIndex OBJECT-TYPE efmCuPme2BsModeIndex OBJECT-TYPE
SYNTAX EfmProfileIndex SYNTAX EfmProfileIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"2BASE-TL PME Spectral Mode index. "2BASE-TL PME Spectral Mode index.
This object is the unique index associated with this spectral This object is the unique index associated with this spectral
mode. mode.
Entries in this table are referenced via efmCuPme2BsMode Entries in this table are referenced via the efmCuPme2BsMode
object." object."
::= { efmCuPme2BsModeEntry 1 } ::= { efmCuPme2BsModeEntry 1 }
efmCuPme2BsModeDescr OBJECT-TYPE efmCuPme2BsModeDescr OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual string containing information about 2BASE-TL PME "A textual string containing information about a 2BASE-TL PME
spectral mode. The string may include information about spectral mode. The string may include information about
corresponding (country-specific) spectral regulations corresponding (country-specific) spectral regulations
and rate/reach limitations of this particular spectral mode." and rate/reach limitations of this particular spectral mode."
::= { efmCuPme2BsModeEntry 2 } ::= { efmCuPme2BsModeEntry 2 }
efmCuPme2BsModeRowStatus OBJECT-TYPE efmCuPme2BsModeRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object controls creation, modification or deletion of "This object controls creation, modification or deletion of
the associated entry in efmCuPme2BsModeTable per the semantics the associated entry in efmCuPme2BsModeTable per the semantics
of RowStatus. of RowStatus.
If an 'active' entry is referenced via efmCuPme2BsMode, the If an 'active' entry is referenced via efmCuPme2BsMode
entry MUST remain 'active' until all references are removed. instance(s), the entry MUST remain 'active'.
An 'active' entry SHALL NOT be modified. In order to modify an An 'active' entry SHALL NOT be modified. In order to modify an
existing entry it MUST be taken out of service (by setting existing entry it MUST be taken out of service (by setting
this object to 'notInService'), modified and set 'active' this object to 'notInService'), modified and set 'active'
again." again."
::= { efmCuPme2BsModeEntry 3 } ::= { efmCuPme2BsModeEntry 3 }
efmCuPme2BReachRateTable OBJECT-TYPE efmCuPme2BReachRateTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme2BReachRateEntry SYNTAX SEQUENCE OF EfmCuPme2BReachRateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table supports definition of administrative custom "This table supports the definition of administrative custom
spectral modes for 2BASE-TL PMEs, providing spectral spectral modes for 2BASE-TL PMEs, providing spectral
limitations in addition to those specified by limitations in addition to those specified by
efmCuPme2BRegion. efmCuPme2BRegion.
The spectral regulations in some countries (e.g. UK ANFP) The spectral regulations in some countries (e.g. UK ANFP)
limit the length of the loops for certain data rates. limit the length of the loops for certain data rates.
This table allows these country-specific limitations to be This table allows these country-specific limitations to be
specified. specified.
Below is an example of this table for [ANFP]: Below is an example of this table for [ANFP]:
----------+-------+-------+ ----------+-------+-------
Equivalent MaxRate MaxRate Equivalent MaxRate MaxRate
Length PAM16 PAM32 Length PAM16 PAM32
(m) (Kbps) (Kbps) (m) (Kbps) (Kbps)
----------+-------+-------+ ----------+-------+-------
975 2304 5696 975 2304 5696
1125 2304 5504 1125 2304 5504
1275 2304 5120 1275 2304 5120
1350 2304 4864 1350 2304 4864
1425 2304 4544 1425 2304 4544
1500 2304 4288 1500 2304 4288
1575 2304 3968 1575 2304 3968
1650 2304 3776 1650 2304 3776
1725 2304 3520 1725 2304 3520
1800 2304 3264 1800 2304 3264
1875 2304 3072 1875 2304 3072
1950 2048 2688 1950 2048 2688
2100 1792 2368 2100 1792 2368
2250 1536 0 2250 1536 0
2400 1408 0 2400 1408 0
2550 1280 0 2550 1280 0
2775 1152 0 2775 1152 0
2925 1152 0 2925 1152 0
3150 1088 0 3150 1088 0
3375 1024 0 3375 1024 0
----------+-------+-------+ ----------+-------+-------
Entries in this table referenced by an efmCuPme2BsMode
Entries in this table referenced by the efmCuPme2BsMode instance MUST NOT be deleted.
MUST NOT be deleted until all the active references are
removed.
This table MUST be maintained in a persistent manner." This table MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"[ANFP]" "[ANFP]"
::= { efmCuPme2B 4 } ::= { efmCuPme2B 4 }
efmCuPme2BReachRateEntry OBJECT-TYPE efmCuPme2BReachRateEntry OBJECT-TYPE
SYNTAX EfmCuPme2BReachRateEntry SYNTAX EfmCuPme2BReachRateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry specifies maximum 2BASE-TL PME data rates "Each entry specifies maximum 2BASE-TL PME data rates
allowed for a certain equivalent loop length, when using allowed for a certain equivalent loop length, when using
16-TCPAM or 32-TCPAM encoding. 16-TCPAM or 32-TCPAM encoding.
When 2BASE-TL PME is initialized, its data rate MUST NOT When a 2BASE-TL PME is initialized, its data rate MUST NOT
exceed one of the following limitations: exceed one of the following limitations:
- the value of efmCuPme2BMaxDataRate - the value of efmCuPme2BMaxDataRate
- maximum data rate allowed by efmCuPme2BRegion and - maximum data rate allowed by efmCuPme2BRegion and
efmCuPme2BPower efmCuPme2BPower
- maximum data rate for a given encoding specified in the - maximum data rate for a given encoding specified in the
efmCuPme2BsModeEntry, corresponding to the equivalent loop efmCuPme2BsModeEntry, corresponding to the equivalent loop
length, estimated by the PME. length, estimated by the PME.
It is RECOMMENDED that the efmCuPme2BEquivalentLength values It is RECOMMENDED that the efmCuPme2BEquivalentLength values
are assigned in the increasing order, starting from the are assigned in increasing order, starting from the minimum
minimum value. value.
Entries may be created/deleted using the row creation/ Entries may be created/deleted using the row creation/
deletion mechanism via efmCuPme2ReachRateRowStatus." deletion mechanism via efmCuPme2ReachRateRowStatus."
INDEX { efmCuPme2BsModeIndex, efmCuPme2BReachRateIndex } INDEX { efmCuPme2BsModeIndex, efmCuPme2BReachRateIndex }
::= { efmCuPme2BReachRateTable 1 } ::= { efmCuPme2BReachRateTable 1 }
EfmCuPme2BReachRateEntry ::= EfmCuPme2BReachRateEntry ::=
SEQUENCE { SEQUENCE {
efmCuPme2BReachRateIndex EfmProfileIndex, efmCuPme2BReachRateIndex EfmProfileIndex,
efmCuPme2BEquivalentLength Unsigned32, efmCuPme2BEquivalentLength Unsigned32,
skipping to change at page 68, line 39 skipping to change at page 69, line 15
"2BASE-TL custom spectral mode Reach-Rate table index. "2BASE-TL custom spectral mode Reach-Rate table index.
This object is the unique index associated with each enry." This object is the unique index associated with each enry."
::= { efmCuPme2BReachRateEntry 1 } ::= { efmCuPme2BReachRateEntry 1 }
efmCuPme2BEquivalentLength OBJECT-TYPE efmCuPme2BEquivalentLength OBJECT-TYPE
SYNTAX Unsigned32(0..8192) SYNTAX Unsigned32(0..8192)
UNITS "m" UNITS "m"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Maximum allowed Equivalent loop's Physical Length in meters "Maximum allowed equivalent loop's physical length in meters
for the specified data rates. for the specified data rates.
An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a
perfect square root attenuation characteristic, without any perfect square root attenuation characteristic, without any
bridged taps." bridged taps."
::= { efmCuPme2BReachRateEntry 2 } ::= { efmCuPme2BReachRateEntry 2 }
efmCuPme2BMaxDataRatePam16 OBJECT-TYPE efmCuPme2BMaxDataRatePam16 OBJECT-TYPE
SYNTAX Unsigned32(0|192..5696) SYNTAX Unsigned32(0|192..5696)
UNITS "Kbps" UNITS "Kbps"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Maximum data rate for 2BASE-TL PME at the specified "Maximum data rate for a 2BASE-TL PME at the specified
Equivalent loop's Length using TC-PAM16 encoding. equivalent loop's length using TC-PAM16 encoding.
The value of zero means that TC-PAM16 encoding should not be The value of zero means that TC-PAM16 encoding should not be
used at this distance." used at this distance."
::= { efmCuPme2BReachRateEntry 3 } ::= { efmCuPme2BReachRateEntry 3 }
efmCuPme2BMaxDataRatePam32 OBJECT-TYPE efmCuPme2BMaxDataRatePam32 OBJECT-TYPE
SYNTAX Unsigned32(0|192..5696) SYNTAX Unsigned32(0|192..5696)
UNITS "Kbps" UNITS "Kbps"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Maximum data rate for 2BASE-TL PME at the specified "Maximum data rate for a 2BASE-TL PME at the specified
Equivalent loop's Length using TC-PAM32 encoding. equivalent loop's length using TC-PAM32 encoding.
The value of zero means that TC-PAM32 encoding should not be The value of zero means that TC-PAM32 encoding should not be
used at this distance." used at this distance."
::= { efmCuPme2BReachRateEntry 4 } ::= { efmCuPme2BReachRateEntry 4 }
efmCuPme2BReachRateRowStatus OBJECT-TYPE efmCuPme2BReachRateRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object controls creation, modification or deletion of "This object controls the creation, modification or deletion
the associated entry in efmCuPme2BReachRateTable per the of the associated entry in the efmCuPme2BReachRateTable per
semantics of RowStatus. the semantics of RowStatus.
If an 'active' entry is referenced via efmCuPme2BsMode, the If an 'active' entry is referenced via efmCuPme2BsMode
entry MUST remain 'active' until all references are removed. instance(s), the entry MUST remain 'active'.
An 'active' entry SHALL NOT be modified. In order to modify an An 'active' entry SHALL NOT be modified. In order to modify an
existing entry it MUST be taken out of service (by setting existing entry it MUST be taken out of service (by setting
this object to 'notInService'), modified and set 'active' this object to 'notInService'), modified and set 'active'
again." again."
::= { efmCuPme2BReachRateEntry 5 } ::= { efmCuPme2BReachRateEntry 5 }
-- 10PASS-TS specific PME group -- 10PASS-TS specific PME group
efmCuPme10P OBJECT IDENTIFIER ::= { efmCuPme 6 } efmCuPme10P OBJECT IDENTIFIER ::= { efmCuPme 6 }
efmCuPme10PProfileTable OBJECT-TYPE efmCuPme10PProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme10PProfileEntry SYNTAX SEQUENCE OF EfmCuPme10PProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table supports definitions of configuration profiles for "This table supports definitions of configuration profiles for
10PASS-TS PMEs. 10PASS-TS PMEs.
The first 22 entries in this table SHALL always be defined as
First 22 entries in this table SHALL always be defined as follows (see 802.3ah Annex 62B.3, table 62B-1):
follows (see 802.3ah Annex 62B.3): -------+--------+----+---------+-----+-----+---------------
-------+--------+----+---------+-----+------------ Profile Bandplan UPBO BandNotch DRate URate Comment
Profile Bandplan UPBO BandNotch DRate URate
Index PSDMask# p# p# p# p# Index PSDMask# p# p# p# p#
-------+--------+----+---------+-----+------------ -------+--------+----+---------+-----+-----+---------------
1 1 3 2,6,10,11 20 20(default) 1 1 3 2,6,10,11 20 20 default profile
2 13 5 0 20 20 2 13 5 0 20 20
3 1 1 0 20 20 3 1 1 0 20 20
4 16 0 0 100 100 4 16 0 0 100 100
5 16 0 0 70 50 5 16 0 0 70 50
6 6 0 0 50 10 6 6 0 0 50 10
7 17 0 0 30 30 7 17 0 0 30 30
8 8 0 0 30 5 8 8 0 0 30 5
9 4 0 0 25 25 9 4 0 0 25 25
10 4 0 0 15 15 10 4 0 0 15 15
11 23 0 0 10 10 11 23 0 0 10 10
skipping to change at page 70, line 33 skipping to change at page 71, line 8
13 16 0 2,5,9,11 100 100 13 16 0 2,5,9,11 100 100
14 16 0 2,5,9,11 70 50 14 16 0 2,5,9,11 70 50
15 6 0 2,6,10,11 50 10 15 6 0 2,6,10,11 50 10
16 17 0 2,5,9,11 30 30 16 17 0 2,5,9,11 30 30
17 8 0 2,6,10,11 30 5 17 8 0 2,6,10,11 30 5
18 4 0 2,6,10,11 25 25 18 4 0 2,6,10,11 25 25
19 4 0 2,6,10,11 15 15 19 4 0 2,6,10,11 15 15
20 23 0 2,5,9,11 10 10 20 23 0 2,5,9,11 10 10
21 23 0 2,5,9,11 5 5 21 23 0 2,5,9,11 5 5
22 30 0 0 200 50 22 30 0 0 200 50
-------+--------+----+---------+-----+-----+---------------
These default entries SHALL be created by during agent These default entries SHALL be created during agent
initialization and MUST NOT be deleted. initialization and MUST NOT be deleted.
Entries following the first 22, can be dynamically created and Entries following the first 22 can be dynamically created and
deleted, to provide custom administrative (configuration) deleted to provide custom administrative (configuration)
profiles and automatic operating profiles. profiles and automatic operating profiles.
This table MUST be maintained in a persistent manner." This table MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"[802.3ah] Annex 62B.3, 30.11.2.1.6" "[802.3ah] Annex 62B.3, 30.11.2.1.6"
::= { efmCuPme10P 1 } ::= { efmCuPme10P 1 }
efmCuPme10PProfileEntry OBJECT-TYPE efmCuPme10PProfileEntry OBJECT-TYPE
SYNTAX EfmCuPme10PProfileEntry SYNTAX EfmCuPme10PProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry corresponds to a single 10PASS-TS PME "Each entry corresponds to a single 10PASS-TS PME profile.
profile.
Each profile contains a set of parameters, used either for Each profile contains a set of parameters, used either for
configuration or representation of a 10PASS-TS PME. configuration or representation of a 10PASS-TS PME.
In case a particular profile is referenced via In case a particular profile is referenced via the
efmCuPmeAdminProfile object (or efmCuAdminProfile if efmCuPmeAdminProfile object (or efmCuAdminProfile if
efmCuPmeAdminProfile is zero), it represent the desired efmCuPmeAdminProfile is zero), it represents the desired
parameters the 10PassTS-O PME initialization. parameters for the 10PassTS-O PME initialization.
If a profile is referenced via efmCuPmeOperProfile object, If a profile is referenced via an efmCuPmeOperProfile object,
it represents current operating parameters of the PME. it represents the current operating parameters of the PME.
Profiles may be created/deleted using the row creation/ Profiles may be created/deleted using the row creation/
deletion mechanism via efmCuPme10PProfileRowStatus. If an deletion mechanism via efmCuPme10PProfileRowStatus. If an
'active' entry is referenced, the entry MUST remain 'active' 'active' entry is referenced, the entry MUST remain 'active'
until all references are removed. until all references are removed.
Default entries MUST NOT be removed." Default entries MUST NOT be removed."
INDEX { efmCuPme10PProfileIndex } INDEX { efmCuPme10PProfileIndex }
::= { efmCuPme10PProfileTable 1 } ::= { efmCuPme10PProfileTable 1 }
EfmCuPme10PProfileEntry ::= EfmCuPme10PProfileEntry ::=
SEQUENCE { SEQUENCE {
efmCuPme10PProfileIndex EfmProfileIndex, efmCuPme10PProfileIndex EfmProfileIndex,
efmCuPme10PProfileDescr SnmpAdminString, efmCuPme10PProfileDescr SnmpAdminString,
efmCuPme10PBandplanPSDMskProfile INTEGER, efmCuPme10PBandplanPSDMskProfile INTEGER,
efmCuPme10PUPBOReferenceProfile INTEGER, efmCuPme10PUPBOReferenceProfile INTEGER,
efmCuPme10PBandNotchProfiles BITS, efmCuPme10PBandNotchProfiles BITS,
efmCuPme10PPayloadURateProfile INTEGER,
efmCuPme10PPayloadDRateProfile INTEGER, efmCuPme10PPayloadDRateProfile INTEGER,
efmCuPme10PPayloadURateProfile INTEGER,
efmCuPme10PProfileRowStatus RowStatus efmCuPme10PProfileRowStatus RowStatus
} }
efmCuPme10PProfileIndex OBJECT-TYPE efmCuPme10PProfileIndex OBJECT-TYPE
SYNTAX EfmProfileIndex SYNTAX EfmProfileIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"10PASS-TS PME Profile Index. "10PASS-TS PME profile Index.
This object is the unique index associated with this profile. This object is the unique index associated with this profile.
Entries in this table are referenced via efmCuAdminProfile or Entries in this table are referenced via efmCuAdminProfile or
efmCuPmeAdminProfile." efmCuPmeAdminProfile."
::= { efmCuPme10PProfileEntry 1 } ::= { efmCuPme10PProfileEntry 1 }
efmCuPme10PProfileDescr OBJECT-TYPE efmCuPme10PProfileDescr OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual string containing information about 10PASS-TS PME "A textual string containing information about a 10PASS-TS PME
Profile. The string may include information about data rate profile. The string may include information about data rate
and spectral limitations of this particular profile." and spectral limitations of this particular profile."
::= { efmCuPme10PProfileEntry 2 } ::= { efmCuPme10PProfileEntry 2 }
efmCuPme10PBandplanPSDMskProfile OBJECT-TYPE efmCuPme10PBandplanPSDMskProfile OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
profile1(1), profile1(1),
profile2(2), profile2(2),
profile3(3), profile3(3),
profile4(4), profile4(4),
profile5(5), profile5(5),
skipping to change at page 72, line 36 skipping to change at page 73, line 13
profile19(19), profile19(19),
profile20(20), profile20(20),
profile21(21), profile21(21),
profile22(22), profile22(22),
profile23(23), profile23(23),
profile24(24), profile24(24),
profile25(25), profile25(25),
profile26(26), profile26(26),
profile27(27), profile27(27),
profile28(28), profile28(28),
profile29(29) profile29(29),
profile30(30)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"10PASS-TS PME Bandplan and PSD Mask profile, "The 10PASS-TS PME Bandplan and PSD Mask Profile, as specified
as specified in 802.3ah Annex 62A. Possible values are: in 802.3ah Annex 62A, table 62A-1. Possible values are:
--------------+------------------------+-----------+--------- --------------+------------------------+------------+--------
Profile Name PSD Mask Bands Bandplan Profile Name PSD Mask Bands G.993.1
--------------+------------------------+-----------+--------- 0/1/2/3/4/5 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 profile1(1) T1.424 FTTCab.M1 x/D/U/D/U A
profile3(3) - T1.424/T-U P1 FTTCab.M2 profile2(2) T1.424 FTTEx.M1 x/D/U/D/U A
profile4(4) - T1.424/T-U P1 FTTEx.M2 profile3(3) T1.424 FTTCab.M2 x/D/U/D/U A
profile5(5) - T1.424/T-U P1 FTTCab.M1 D/D/U/D/U profile4(4) T1.424 FTTEx.M2 x/D/U/D/U A
profile6(6) - T1.424/T-U P1 FTTEx.M1 profile5(5) T1.424 FTTCab.M1 D/D/U/D/U A
profile7(7) - T1.424/T-U P1 FTTCab.M2 profile6(6) T1.424 FTTEx.M1 D/D/U/D/U A
profile8(8) - T1.424/T-U P1 FTTEx.M2 profile7(7) T1.424 FTTCab.M2 D/D/U/D/U A
profile9(9) - T1.424/T-U P1 FTTCab.M1 U/D/U/D/x profile8(8) T1.424 FTTEx.M2 D/D/U/D/U A
profile10(10) - T1.424/T-U P1 FTTEx.M1 profile9(9) T1.424 FTTCab.M1 U/D/U/D/x A
profile11(11) - T1.424/T-U P1 FTTCab.M2 profile10(10) T1.424 FTTEx.M1 U/D/U/D/x A
profile12(12) - T1.424/T-U P1 FTTEx.M2 profile11(11) T1.424 FTTCab.M2 U/D/U/D/x A
profile13(13) - TS1 101 270-1 Pcab.M1.A x/D/U/D/U B profile12(12) T1.424 FTTEx.M2 U/D/U/D/x A
profile14(14) - TS1 101 270-1 Pcab.M1.B profile13(13) TS 101 270-1 Pcab.M1.A x/D/U/D/U B
profile15(15) - TS1 101 270-1 Pex.P1.M1 profile14(14) TS 101 270-1 Pcab.M1.B x/D/U/D/U B
profile16(16) - TS1 101 270-1 Pex.P2.M1 profile15(15) TS 101 270-1 Pex.P1.M1 x/D/U/D/U B
profile17(17) - TS1 101 270-1 Pcab.M2 profile16(16) TS 101 270-1 Pex.P2.M1 x/D/U/D/U B
profile18(18) - TS1 101 270-1 Pex.P1.M2 profile17(17) TS 101 270-1 Pcab.M2 x/D/U/D/U B
profile19(19) - TS1 101 270-1 Pex.P2.M2 profile18(18) TS 101 270-1 Pex.P1.M2 x/D/U/D/U B
profile20(20) - TS1 101 270-1 Pcab.M1.A U/D/U/D/x profile19(19) TS 101 270-1 Pex.P2.M2 x/D/U/D/U B
profile21(21) - TS1 101 270-1 Pcab.M1.B profile20(20) TS 101 270-1 Pcab.M1.A U/D/U/D/x B
profile22(22) - TS1 101 270-1 Pex.P1.M1 profile21(21) TS 101 270-1 Pcab.M1.B U/D/U/D/x B
profile23(23) - TS1 101 270-1 Pex.P2.M1 profile22(22) TS 101 270-1 Pex.P1.M1 U/D/U/D/x B
profile24(24) - TS1 101 270-1 Pcab.M2 profile23(23) TS 101 270-1 Pex.P2.M1 U/D/U/D/x B
profile25(25) - TS1 101 270-1 Pex.P1.M2 profile24(24) TS 101 270-1 Pcab.M2 U/D/U/D/x B
profile26(26) - TS1 101 270-1 Pex.P2.M2 profile25(25) TS 101 270-1 Pex.P1.M2 U/D/U/D/x B
profile27(27) - G.993.1 F.1.2.1 (VDSLoPOTS) x/D/U/D/U F profile26(26) TS 101 270-1 Pex.P2.M2 U/D/U/D/x B
profile28(28) - G.993.1 F.1.2.2 (VDSLoTCM-ISDN) profile27(27) G.993.1 F.1.2.1 x/D/U/D/U Annex F
profile29(29) - G.993.1 F.1.2.3 (PSD reduction) profile28(28) G.993.1 F.1.2.2 x/D/U/D/U Annex F
profile29(29) G.993.1 F.1.2.3 x/D/U/D/U Annex F
This object maps to the aBandplanPSDMaskProfile attribute profile30(30) T1.424 FTTCab.M1 (ext.) x/D/U/D/U/D Annex A
in Clause 30." --------------+------------------------+------------+--------
"
REFERENCE REFERENCE
"[802.3ah] Annex 62A, 30.5.1.1.22" "[802.3ah] Annex 62A"
::= { efmCuPme10PProfileEntry 3 } ::= { efmCuPme10PProfileEntry 3 }
efmCuPme10PUPBOReferenceProfile OBJECT-TYPE efmCuPme10PUPBOReferenceProfile OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
profile0(0),
profile1(1), profile1(1),
profile2(2), profile2(2),
profile3(3), profile3(3),
profile4(4), profile4(4),
profile5(5), profile5(5),
profile6(6), profile6(6),
profile7(7), profile7(7),
profile8(8), profile8(8),
profile9(9) profile9(9)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"10PASS-TS PME Upstream Power Back-Off (UPBO) Reference PSD "The 10PASS-TS PME Upstream Power Back-Off (UPBO) Reference
Profile, as specified in 802.3ah Annex 62A. Possible values PSD Profile, as specified in 802.3 Annex 62A, table 62A-3.
are: Possible values are:
------------+-----------------------------
profile1(1) - T1.424/T-U Noise A M1 Profile Name Reference PSD
profile2(2) - T1.424/T-U Noise A M2 ------------+-----------------------------
profile3(3) - T1.424/T-U Noise F M1 profile0(0) no profile
profile4(4) - T1.424/T-U Noise F M2 profile1(1) T1.424 Noise A M1
profile5(5) - ETSI TS 101 270-1 Noise A&B profile2(2) T1.424 Noise A M2
profile6(6) - ETSI TS 101 270-1 Noise C profile3(3) T1.424 Noise F M1
profile7(7) - ETSI TS 101 270-1 Noise D profile4(4) T1.424 Noise F M2
profile8(8) - ETSI TS 101 270-1 Noise E profile5(5) TS 101 270-1 Noise A&B
profile9(9) - ETSI TS 101 270-1 Noise F profile6(6) TS 101 270-1 Noise C
profile7(7) TS 101 270-1 Noise D
This object maps to the aUPBOReferenceProfile attribute profile8(8) TS 101 270-1 Noise E
in Clause 30." profile9(9) TS 101 270-1 Noise F
------------+-----------------------------
"
REFERENCE REFERENCE
"[802.3ah] Annex 62A.3.4, 30.5.1.1.23" "[802.3ah] Annex 62A.3.5"
::= { efmCuPme10PProfileEntry 4 } ::= { efmCuPme10PProfileEntry 4 }
efmCuPme10PBandNotchProfiles OBJECT-TYPE efmCuPme10PBandNotchProfiles OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
profile0(0), profile0(0),
profile1(1), profile1(1),
profile2(2), profile2(2),
profile3(3), profile3(3),
profile4(4), profile4(4),
profile5(5), profile5(5),
profile6(6), profile6(6),
profile7(7), profile7(7),
profile8(8), profile8(8),
profile9(9), profile9(9),
profile10(10), profile10(10),
profile11(11) profile11(11)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"10PASS-TS PME Egress Control Band Notch Profile bitmap, "The 10PASS-TS PME Egress Control Band Notch Profile bitmap,
as specified in 802.3ah Annex 62A. Possible values are: as specified in 802.3 Annex 62A, table 62A-4. Possible values
--------------+---------+----------+-----------+------+----- are:
Profile Name G.991.3 T1.424/T-U TS101 270-1 StartF EndF --------------+--------+------+------------+------+------
Table Table Table (MHz) (MHz) Profile Name G.991.3 T1.424 TS 101 270-1 StartF EndF
--------------+---------+----------+-----------+------+----- table table table (MHz) (MHz)
profile0(0) - no profile --------------+--------+------+------------+------+------
profile1(1) - F-5 #01 - - 1.810 1.825 profile0(0) no profile
profile2(2) - 6-2 15-1 17 1.810 2.000 profile1(1) F-5 #01 - - 1.810 1.825
profile3(3) - F-5 #02 - - 1.907 1.912 profile2(2) 6-2 15-1 17 1.810 2.000
profile4(4) - F-5 #03 - - 3.500 3.575 profile3(3) F-5 #02 - - 1.907 1.912
profile5(5) - 6-2 - 17 3.500 3.800 profile4(4) F-5 #03 - - 3.500 3.575
profile6(6) - - 15-1 - 3.500 4.000 profile5(5) 6-2 - 17 3.500 3.800
profile7(7) - F-5 #04 - - 3.747 3.754 profile6(6) - 15-1 - 3.500 4.000
profile8(8) - F-5 #05 - - 3.791 3.805 profile7(7) F-5 #04 - - 3.747 3.754
profile9(9) - 6-2 - 17 7.000 7.100 profile8(8) F-5 #05 - - 3.791 3.805
profile10(10) - F-5 #06 15-1 - 7.000 7.300 profile9(9) 6-2 - 17 7.000 7.100
profile11(11) - 6-2 15-1 1 10.100 10.150 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 be specified by ORing Any combination of profiles can be specified by ORing
individual profiles, for example value of 0x0622 selects individual profiles, for example value of 0x2230 selects
profiles 2,6,10 and 11. profiles 2,6,10 and 11."
This object maps to the aBandNotchProfile attribute
in Clause 30."
REFERENCE REFERENCE
"[802.3ah] Annex 62A.3.5, 30.5.1.1.19" "[802.3ah] Annex 62A.3.5"
::= { efmCuPme10PProfileEntry 5 } ::= { efmCuPme10PProfileEntry 5 }
efmCuPme10PPayloadURateProfile OBJECT-TYPE efmCuPme10PPayloadDRateProfile OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
profile5(5), profile5(5),
profile10(10), profile10(10),
profile15(15), profile15(15),
profile20(20), profile20(20),
profile25(25), profile25(25),
profile30(30), profile30(30),
profile50(50), profile50(50),
profile70(70), profile70(70),
profile100(100) profile100(100),
profile140(140),
profile200(200)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"10PASS-TS PME Upstream Payload Rate Profile, "The 10PASS-TS PME Downstream Payload Rate Profile, as
as specified in 802.3ah Annex 62A. Possible values are: specified in 802.3 Annex 62A. Possible values are:
profile5(5) - 2.5 Mbps profile5(5) - 2.5 Mbps
profile10(10) - 5 Mbps profile10(10) - 5 Mbps
profile15(15) - 7.5 Mbps profile15(15) - 7.5 Mbps
profile20(20) - 10 Mbps profile20(20) - 10 Mbps
profile25(25) - 12.5 Mbps profile25(25) - 12.5 Mbps
profile30(30) - 15 Mbps profile30(30) - 15 Mbps
profile50(50) - 25 Mbps profile50(50) - 25 Mbps
profile70(70) - 35 Mbps profile70(70) - 35 Mbps
profile100(100) - 50 Mbps profile100(100) - 50 Mbps
profile140(140) - 70 Mbps
profile200(200) - 100 Mbps
Each value represents a target for the PME's Upstream Payload Each value represents a target for the PME's Downstream
Bitrate as seen at the MII. If the payload rate of the Payload Bitrate as seen at the MII. If the payload rate of
selected profile cannot be achieved based on the loop the selected profile cannot be achieved based on the loop
environment, bandplan and PSD mask, the PME initialization environment, bandplan and PSD mask, the PME initialization
SHALL fail. SHALL fail."
This object maps to the aPayloadRateProfileUpstream
attribute in Clause 30."
REFERENCE REFERENCE
"[802.3ah] Annex 62A.3.6, 30.5.1.1.20" "[802.3ah] Annex 62A.3.6"
::= { efmCuPme10PProfileEntry 6 } ::= { efmCuPme10PProfileEntry 6 }
efmCuPme10PPayloadDRateProfile OBJECT-TYPE efmCuPme10PPayloadURateProfile OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
profile5(5), profile5(5),
profile10(10), profile10(10),
profile15(15), profile15(15),
profile20(20), profile20(20),
profile25(25), profile25(25),
profile30(30), profile30(30),
profile50(50), profile50(50),
profile70(70), profile70(70),
profile100(100), profile100(100)
profile140(140),
profile200(200)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"10PASS-TS PME Downstream Payload Rate Profile, "The 10PASS-TS PME Upstream Payload Rate Profile, as specified
as specified in 802.3ah Annex 62A. Possible values are: in 802.3 Annex 62A. Possible values are:
profile5(5) - 2.5 Mbps profile5(5) - 2.5 Mbps
profile10(10) - 5 Mbps profile10(10) - 5 Mbps
profile15(15) - 7.5 Mbps profile15(15) - 7.5 Mbps
profile20(20) - 10 Mbps profile20(20) - 10 Mbps
profile25(25) - 12.5 Mbps profile25(25) - 12.5 Mbps
profile30(30) - 15 Mbps profile30(30) - 15 Mbps
profile50(50) - 25 Mbps profile50(50) - 25 Mbps
profile70(70) - 35 Mbps profile70(70) - 35 Mbps
profile100(100) - 50 Mbps profile100(100) - 50 Mbps
profile140(140) - 70 Mbps
profile200(200) - 100 Mbps
Each value represents a target for the PME's Downstream Each value represents a target for the PME's Upstream Payload
Payload Bitrate as seen at the MII. If the payload rate of Bitrate as seen at the MII. If the payload rate of the
the selected profile cannot be achieved based on the loop selected profile cannot be achieved based on the loop
environment, bandplan and PSD mask, the PME initialization environment, bandplan and PSD mask, the PME initialization
SHALL fail. SHALL fail."
This object maps to the aPayloadRateProfileDownstream
attribute in Clause 30."
REFERENCE REFERENCE
"[802.3ah] Annex 62A.3.6, 30.5.1.1.21" "[802.3ah] Annex 62A.3.6"
::= { efmCuPme10PProfileEntry 7 } ::= { efmCuPme10PProfileEntry 7 }
efmCuPme10PProfileRowStatus OBJECT-TYPE efmCuPme10PProfileRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object controls creation, modification or deletion of "This object controls creation, modification or deletion of
the associated entry in efmCuPme10PProfileTable per the the associated entry in efmCuPme10PProfileTable per the
semantics of RowStatus. semantics of RowStatus.
If an active entry is referenced via efmCuAdminProfile or If an active entry is referenced via efmCuAdminProfile or
skipping to change at page 77, line 41 skipping to change at page 78, line 19
This table contains live data from the equipment. As such, This table contains live data from the equipment. As such,
it is NOT persistent." it is NOT persistent."
::= { efmCuPme10P 2 } ::= { efmCuPme10P 2 }
efmCuPme10PStatusEntry OBJECT-TYPE efmCuPme10PStatusEntry OBJECT-TYPE
SYNTAX EfmCuPme10PStatusEntry SYNTAX EfmCuPme10PStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the EFMCu 10PASS-TS PME Status table." "An entry in the EFMCu 10PASS-TS PME Status table."
AUGMENTS { efmCuPmeStatusEntry } INDEX { ifIndex }
::= { efmCuPme10PStatusTable 1 } ::= { efmCuPme10PStatusTable 1 }
EfmCuPme10PStatusEntry ::= EfmCuPme10PStatusEntry ::=
SEQUENCE { SEQUENCE {
efmCuPme10PFECCorrectedBlocks Counter32, efmCuPme10PFECCorrectedBlocks Counter32,
efmCuPme10PFECUncorrectedBlocks Counter32 efmCuPme10PFECUncorrectedBlocks Counter32
} }
efmCuPme10PFECCorrectedBlocks OBJECT-TYPE efmCuPme10PFECCorrectedBlocks OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of received and corrected FEC codewords in 10PASS-TS "The number of received and corrected FEC codewords in this
PME. 10PASS-TS PME.
This object maps to aPMEFECCorrectedBlocks attribute in This object maps to the aPMEFECCorrectedBlocks attribute in
clause 30. Clause 30.
If a Clause 45 MDIO Interface to the PMA/PMD is present, If a Clause 45 MDIO Interface to the PMA/PMD is present,
then this object maps to the 10P FEC correctable errors then this object maps to the 10P FEC correctable errors
register register.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime, as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB." defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.22, 30.11.2.1.8" "[802.3ah] 45.2.1.22, 30.11.2.1.8"
::= { efmCuPme10PStatusEntry 1 } ::= { efmCuPme10PStatusEntry 1 }
efmCuPme10PFECUncorrectedBlocks OBJECT-TYPE efmCuPme10PFECUncorrectedBlocks OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of received FEC codewords in 10PASS-TS PME, which are "The number of received uncorrectable FEC codewords in this
uncorrectable. 10PASS-TS PME.
This object maps to aPMEFECUncorrectableBlocks attribute in This object maps to the aPMEFECUncorrectableBlocks attribute
clause 30. in Clause 30.
If a Clause 45 MDIO Interface to the PMA/PMD is present, If a Clause 45 MDIO Interface to the PMA/PMD is present,
then this object maps to the 10P FEC uncorrectable errors then this object maps to the 10P FEC uncorrectable errors
register register.
Discontinuities in the value of this counter can occur at Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime, as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB." defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.23, 30.11.2.1.9" "[802.3ah] 45.2.1.23, 30.11.2.1.9"
::= { efmCuPme10PStatusEntry 2 } ::= { efmCuPme10PStatusEntry 2 }
-- --
skipping to change at page 81, line 15 skipping to change at page 81, line 41
::= { efmCuGroups 5 } ::= { efmCuGroups 5 }
efmCuNotificationGroup NOTIFICATION-GROUP efmCuNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
efmCuLowRateCrossing, efmCuLowRateCrossing,
efmCuPmeLineAtnCrossing, efmCuPmeLineAtnCrossing,
efmCuPmeSnrMgnCrossing, efmCuPmeSnrMgnCrossing,
efmCuPmeDeviceFault, efmCuPmeDeviceFault,
efmCuPmeConfigInitFailure, efmCuPmeConfigInitFailure,
efmCuPmeProtocolInitFailure efmCuPmeProtocolInitFailure
-- efmCuPmeDeviceFault,
-- efmCuPmeLocalPowerLoss
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group supports notifications of significant conditions "This group supports notifications of significant conditions
associated with EFMCu ports." associated with EFMCu ports."
::= { efmCuGroups 6 } ::= { efmCuGroups 6 }
efmCuPme2BProfileGroup OBJECT-GROUP efmCuPme2BProfileGroup OBJECT-GROUP
OBJECTS { OBJECTS {
efmCuPme2BProfileDescr, efmCuPme2BProfileDescr,
skipping to change at page 82, line 5 skipping to change at page 82, line 29
"A collection of objects that constitute a configuration "A collection of objects that constitute a configuration
profile for configuration of 2BASE-TL ports." profile for configuration of 2BASE-TL ports."
::= { efmCuGroups 7} ::= { efmCuGroups 7}
efmCuPme10PProfileGroup OBJECT-GROUP efmCuPme10PProfileGroup OBJECT-GROUP
OBJECTS { OBJECTS {
efmCuPme10PProfileDescr, efmCuPme10PProfileDescr,
efmCuPme10PBandplanPSDMskProfile, efmCuPme10PBandplanPSDMskProfile,
efmCuPme10PUPBOReferenceProfile, efmCuPme10PUPBOReferenceProfile,
efmCuPme10PBandNotchProfiles, efmCuPme10PBandNotchProfiles,
efmCuPme10PPayloadURateProfile,
efmCuPme10PPayloadDRateProfile, efmCuPme10PPayloadDRateProfile,
efmCuPme10PPayloadURateProfile,
efmCuPme10PProfileRowStatus efmCuPme10PProfileRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects that constitute a configuration "A collection of objects that constitute a configuration
profile for configuration of 10PASS-TS ports." profile for configuration of 10PASS-TS ports."
::= { efmCuGroups 8 } ::= { efmCuGroups 8 }
efmCuPme10PStatusGroup OBJECT-GROUP efmCuPme10PStatusGroup OBJECT-GROUP
OBJECTS { OBJECTS {
skipping to change at page 85, line 23 skipping to change at page 85, line 45
support for SET operations in a non-secure environment without proper support for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations. protection can have a negative effect on network operations.
The readable objects in the EFM-CU-MIB module (i.e., those with MAX- The readable objects in the EFM-CU-MIB module (i.e., those with MAX-
ACCESS other than not-accessible) may be considered sensitive in some ACCESS other than not-accessible) may be considered sensitive in some
environments since, collectively, they provide information about the environments since, collectively, they provide information about the
performance of network interfaces and can reveal some aspects of performance of network interfaces and can reveal some aspects of
their configuration. In particular, since EFMCu can be carried over their configuration. In particular, since EFMCu can be carried over
Unshielded Twisted Pair (UTP) voice grade copper in a bundle with Unshielded Twisted Pair (UTP) voice grade copper in a bundle with
other pairs belonging to another operator/customer, it is other pairs belonging to another operator/customer, it is
theoretically possible to evasdrop to an EFMCu transmission simply by theoretically possible to eavesdrop to an EFMCu transmission simply
"listening" to a cross-talk from the EFMCu pairs, especially if the by "listening" to a cross-talk from the EFMCu pairs, especially if
parameters of the EFMCu link in question are known. the parameters of the EFMCu link in question are known.
In such environments it is important to control also GET and NOTIFY In such environments it is important to control also GET and NOTIFY
access to these objects and possibly even to encrypt their values access to these objects and possibly even to encrypt their values
when sending them over the network via SNMP. when sending them over the network via SNMP.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPsec), 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 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 allowed to access and GET/SET (read/change/create/delete) the objects
in these MIB modules. in these MIB modules.
skipping to change at page 86, line 7 skipping to change at page 86, line 26
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of these MIB modules is properly configured to give access instance of these MIB modules is properly configured to give access
to the objects only to those principals (users) that have legitimate to the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
8. IANA Considerations 8. IANA Considerations
The two new values of dot3MauType (dot3MauType2BaseTL and Object identifiers for the efmCuMIB MODULE-IDENTITY and ifCapStackMIB
dot3MauType10PassTS) and corresponding IANAifMauTypeListBits bit MODULE-IDENTITY SHALL be allocated by IANA in the MIB-2 sub-tree,
definitions (b2BaseTL and b10PassTS), as well as the new values for before this document is published.
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.
Additionally, object identifiers for efmCuMIB MODULE-IDENTITY and
ifCapStackMIB MODULE-IDENTITY SHALL be allocated by IANA in the MIB-2
sub-tree, before this document is published.
9. Acknowledgments 9. Acknowledgments
This document was produced by the IETF Ethernet Interfaces and Hub This document was produced by the IETF Ethernet Interfaces and Hub
MIB Working Group [1], whose efforts were greatly advanced by the MIB Working Group [1], whose efforts were greatly advanced by the
contributions of the following people (in alphabetical order): contributions of the following people (in alphabetical order):
Bert Wijnen (Alcatel) Udi Ashkenazi (Actelis)
Dan Romascanu (Avaya) Mike Heard
Alfred Hoenes (TR-Sys)
Marina Popilov (Actelis) Marina Popilov (Actelis)
Mathias Riess (Infineon) Mathias Riess (Infineon)
Matt Squire (Hatteras) Dan Romascanu (Avaya)
Mike Heard
Udi Ashkenazi (Actelis)
10. Notes to RFC Editor
This section contains notes to the RFC Editor and should be removed
prior to publication.
Please replace [I-D.ietf-hubmib-efm-mib] and Matt Squire (Hatteras)
[I-D.ietf-hubmib-rfc3636bis] with actual RFC numbers if those are Bert Wijnen (Alcatel)
available at time of publication.
11. References 10. References
11.1. Normative References 10.1. Normative References
[802.3] IEEE, "IEEE Standard for Information technology - [802.3] IEEE, "IEEE Standard for Information technology -
Telecommunications and information exchange between Telecommunications and information exchange between
systems - Local and metropolitan area networks - Specific systems - Local and metropolitan area networks - Specific
requirements - Part 3: Carrier Sense Multiple Access with requirements - Part 3: Carrier Sense Multiple Access with
Collision Detection (CSMA/CD) Access Method and Physical Collision Detection (CSMA/CD) Access Method and Physical
Layer Specifications", IEEE Std 802.3-2005, December 2005. Layer Specifications", IEEE Std 802.3-2005, December 2005.
[802.3ah] IEEE, "IEEE Standard for Information technology - [802.3ah] IEEE, "IEEE Standard for Information technology -
Telecommunications and information exchange between Telecommunications and information exchange between
skipping to change at page 87, line 31 skipping to change at page 87, line 34
Subscriber Access Networks", IEEE Std 802.3ah-2004, Subscriber Access Networks", IEEE Std 802.3ah-2004,
September 2004. September 2004.
[G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber Line [G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber Line
(SHDSL) transceivers", ITU-T Recommendation G.991.2, (SHDSL) transceivers", ITU-T Recommendation G.991.2,
December 2003. December 2003.
[G.993.1] ITU-T, "Very High speed Digital Subscriber Line [G.993.1] ITU-T, "Very High speed Digital Subscriber Line
transceivers", ITU-T Recommendation G.993.1, June 2004. transceivers", ITU-T Recommendation G.993.1, June 2004.
[I-D.ietf-hubmib-rfc3636bis]
Beili, E., "Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs)",
draft-ietf-hubmib-rfc3636bis-05 (work in progress),
July 2006.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Schoenwaelder, Ed., "Structure of Management Information
Management Information Version 2 (SMIv2)", STD 58, Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
McCloghrie, K., Rose, M., and S. Waldbusser, "Textual Schoenwaelder, Ed., "Textual Conventions for SMIv2",
Conventions for SMIv2", STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table [RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table
Extension to the Interfaces Group MIB", RFC 2864, Extension to the Interfaces Group MIB", RFC 2864,
June 2000. June 2000.
[RFC3635] Flick, J., "Definitions of Managed Objects for the [RFC3635] Flick, J., "Definitions of Managed Objects for the
Ethernet-like Interface Types", RFC 3635, September 2003. Ethernet-like Interface Types", RFC 3635, September 2003.
11.2. Informative References [RFC4836] Beili, E., "Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs)", RFC 4836, April 2007.
[T1.424] ANSI, "Interface Between Networks and Customer
Installation Very-high-bit-rate Digital Subscriber Lines
(VDSL) Metallic Interface (DMT Based)", American National
Standard T1.424-2004, June 2004.
[TS 101 270-1]
ETSI, "Transmission and Multiplexing (TM); Access
transmission systems on metallic access cables; Very high
speed Digital Subscriber Line (VDSL); Part 1: Functional
requirements", Technical Specification TS 101 270-1,
October 2005.
10.2. Informative References
[ANFP] Network Interoperability Consultative Committee (NICC), [ANFP] Network Interoperability Consultative Committee (NICC),
"Specification of the Access Network Frequency Plan (ANFP) "Specification of the Access Network Frequency Plan (ANFP)
applicable to transmission systems used on the BT Access applicable to transmission systems used on the BT Access
Network", NICC Document ND1602:2005/08, August 2005. Network", NICC Document ND1602:2005/08, August 2005.
[I-D.ietf-hubmib-efm-epon-mib]
Khermosh, L., "Managed Objects of EPON",
draft-ietf-hubmib-efm-epon-mib-06 (work in progress),
November 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-05 (work in progress),
October 2006.
[IANAifType-MIB] [IANAifType-MIB]
Internet Assigned Numbers Authority (IANA), "IANAifType Internet Assigned Numbers Authority (IANA), "IANAifType
Textual Convention definition", Textual Convention definition",
http://www.iana.org/assignments/ianaiftype-mib. http://www.iana.org/assignments/ianaiftype-mib.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[RFC4070] Dodge, M. and B. Ray, "Definitions of Managed Object [RFC4070] Dodge, M. and B. Ray, "Definitions of Managed Object
Extensions for Very High Speed Digital Subscriber Lines Extensions for Very High Speed Digital Subscriber Lines
(VDSL) Using Multiple Carrier Modulation (MCM) Line (VDSL) Using Multiple Carrier Modulation (MCM) Line
Coding", RFC 4070, May 2005. Coding", RFC 4070, May 2005.
[RFC4319] Sikes, C., Ray, B., and R. Abbi, "Definitions of Managed [RFC4319] Sikes, C., Ray, B., and R. Abbi, "Definitions of Managed
Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and
Single-Pair High-Speed Digital Subscriber Line (SHDSL) Single-Pair High-Speed Digital Subscriber Line (SHDSL)
Lines", RFC 4319, December 2005. Lines", RFC 4319, December 2005.
[RFC4837] Khermosh, L., "Managed Objects of Ethernet Passive Optical
Networks (EPON)", RFC 4837, July 2007.
[RFC4878] Squire, M., "Definitions and Managed Objects for
Operations, Administration, and Maintenance (OAM)
Functions on Ethernet-Like Interfaces", RFC 4878,
June 2007.
URIs URIs
[1] <http://www.ietf.org/html.charters/hubmib-charter.html> [1] <http://www.ietf.org/html.charters/hubmib-charter.html>
Author's Address Author's Address
Edward Beili Edward Beili
Actelis Networks Actelis Networks
Bazel 25 Bazel 25
Petach-Tikva Petach-Tikva
Israel Israel
 End of changes. 250 change blocks. 
576 lines changed or deleted 585 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/