EFM-CU-MIB

All MIBs › EFM-CU-MIB

Organization: IETF Ethernet Interfaces and Hub MIB Working Group

Last Updated: 2007-11-14

Category: DSL and Broadband, Network Interfaces

Description: Defines managed objects for Ethernet in the First Mile Copper (EFMCu) interfaces, managing DSL-based Ethernet links over copper per IEEE 802.3ah.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring EFM-CU-MIB with a free 30-day trial of IPNetwork Monitor.

What Is EFM-CU-MIB?

EFM-CU-MIB is an IETF standards-based MIB, paired with IEEE 802.3ah-2004, defining managed objects for Ethernet in the First Mile Copper (EFMCu) interfaces — the 2BASE-TL and 10PASS-TS DSL-based Ethernet access technologies delivered over copper in the access 'first mile'. It belongs to the DSL/Ethernet-access technology area and exposes interface configuration, PME aggregation function (bonded-pair) status, line coding/rate parameters, and per-pair loop statistics. For hardware/software status monitoring it is used to confirm a DSL/EFM interface's operational state, verify how many of a bonded group's copper pairs are actively aggregated, and review per-pair error statistics that reveal a degraded or failed copper loop. It is layered on top of and depends on the standard IF-MIB for interface indexing, per IEEE 802.3ah conventions. It is typically deployed by telecom/access carriers on DSLAMs, EFM access multiplexers, and copper-based CPE delivering bonded Ethernet access circuits. Engineers implementing or auditing this functionality typically reference the EFM-CU-MIB RFC/standard documentation for the authoritative specification.

IPNetwork Monitor allows you to monitor SNMP objects defined in EFM-CU-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

vendor-neutral, standards-based MIB, not tied to a specific manufacturer
DSLAM / EFM access multiplexer
EFM Copper CPE / Ethernet-over-copper bridge

Monitoring Examples

No sample objects were supplied for this module, so specific table or object names cannot be confirmed; based on the module description an operator would poll the PME aggregation function (PAF) table to check how many bonded copper pairs in a 2BASE-TL/10PASS-TS group are currently active, and review per-pair loop statistics to identify a degraded or dropped copper pair reducing aggregate bandwidth.

What Can Be Monitored

EFM copper interface operational status
PME aggregation (bonded pair) group status
active vs configured bonded copper pairs
per-pair loop error statistics

Imported Objects

From IF-MIB

ifIndex	OBJECT-TYPE
ifSpeed	OBJECT-TYPE

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32
mib-2

From SNMPv2-TC

PhysAddress
RowStatus
TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using efmCuPAFInErrors OID:

Select a DSLAM/EFM access multiplexer or CPE (802.3ah EFM Copper, vendor-neutral IETF standard) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type efmCuPAFInErrors into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of fragments that have been received across the gamma interface with RxErr asserted and discarded. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
T/F efmCuAdaptiveSpectra	1.3.6.1.2.1.167.1.1.1.1.6	TruthValue	read-write	Indicates how to utilize excess capacity when the copper environment allows a higher total data rate to be achieved than that specified by the efmCuTargetDataRate. A value of true(1) indicates that the excess capability SHALL be reclaimed by minimizing transmit power, e.g., using higher constellations and Power Back-Off, in order to reduce interference to other copper pairs in the binder and the adverse impact to link/system performance. A value of false(2) indicates that the excess capability SHALL be converted to additional SNR margin and spread evenly across all active PMEs assigned to the (PCS) port, to increase link robustness. This object is read-write for the -O subtype EFMCu ports (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. Changing of this object MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing. This object MUST be maintained in a persistent manner.
EFM efmCuAdminProfile	1.3.6.1.2.1.167.1.1.1.1.3	EfmProfileIndexList	read-write	Desired configuration profile(s), common for all PMEs in the EFMCu port. This object is a list of pointers to entries in either efmCuPme2BProfileTable or efmCuPme10PProfileTable, depending on the current operating SubType of the EFMCu port as indicated by efmCuPortSide. The value of this object is a list of up to 6 indices of profiles. If this list consists of a single profile index, then all PMEs assigned to this EFMCu port SHALL be configured according to the profile referenced by that index, unless it is overwritten by a corresponding non-zero efmCuPmeAdminProfile instance, which takes precedence over efmCuAdminProfile. 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. By default, this object has a value of 0x01, referencing the 1st entry in efmCuPme2BProfileTable or efmCuPme10PProfileTable. This object is writable and readable for the -O subtype (2BaseTL-O or 10PassTS-O) EFMCu ports. It is irrelevant for the -R subtype (2BaseTL-R or 10PassTS-R) ports -- a zero-length octet string SHALL be returned on an attempt to read this object and an attempt to change this object MUST be rejected in this case. Note that the current operational profile value is available via the efmCuPmeOperProfile object. Any modification of this object MUST be performed when the link is Down. Attempts to change this object MUST be rejected, if the link is Up or Initializing. Attempts to set this object to a list with a member value that is not the value of the index for an active entry in the corresponding profile table MUST be rejected. This object maps to the Clause 30 attribute aProfileSelect. This object MUST be maintained in a persistent manner.
efmCuAlarmConfGroup	1.3.6.1.2.1.167.2.1.5			A collection of objects supporting configuration of alarm thresholds and notifications in EFMCu ports.
efmCuBasicGroup	1.3.6.1.2.1.167.2.1.1			A collection of objects representing management information common for all types of EFMCu ports.
efmCuCompliance	1.3.6.1.2.1.167.2.2.1			The compliance statement for 2BASE-TL/10PASS-TS interfaces. Compliance with the following external compliance statements is REQUIRED: MIB Module Compliance Statement ---------- -------------------- IF-MIB ifCompliance3 EtherLike-MIB dot3Compliance2 MAU-MIB mauModIfCompl3 Compliance with the following external compliance statements is OPTIONAL for implementations supporting PME Aggregation Function (PAF) with flexible cross-connect between the PCS and PME ports: MIB Module Compliance Statement ---------- -------------------- IF-INVERTED-STACK-MIB ifInvCompliance IF-CAP-STACK-MIB ifCapStackCompliance
efmCuCompliances	1.3.6.1.2.1.167.2.2
efmCuConformance	1.3.6.1.2.1.167.2
BIT efmCuFltStatus	1.3.6.1.2.1.167.1.1.3.1.1	Bits	read-only	EFMCu (PCS) port Fault Status. This is a bitmap of possible conditions. The various bit positions are: noPeer - the peer PHY cannot be reached (e.g., no PMEs attached, all PMEs are Down, etc.). More info is available in efmCuPmeFltStatus. peerPowerLoss - the peer PHY has indicated impending unit failure due to loss of local power ('Dying Gasp'). pmeSubTypeMismatch - local PMEs in the aggregation group are not of the same subtype, e.g., some PMEs in the local device are -O while others are -R subtype. lowRate - ifSpeed of the port reached or dropped below efmCuThreshLowRate. This object is intended to supplement the ifOperStatus object in IF-MIB and ifMauMediaAvailable in MAU-MIB. Additional information is available via the efmCuPmeFltStatus object for each PME in the aggregation group (single PME if PAF is disabled).
efmCuGroups	1.3.6.1.2.1.167.2.1
NTF efmCuLowRateCrossing	1.3.6.1.2.1.167.1.1.0.1			This notification indicates that the EFMCu port's data rate has reached/dropped below or exceeded the low rate threshold, specified by efmCuThreshLowRate. This notification MAY be sent for the -O subtype ports (2BaseTL-O/10PassTS-O) while the port is Up, on the crossing event in both directions: from normal (rate is above the threshold) to low (rate equals the threshold or below it) and from low to normal. This notification is not applicable to the -R subtypes. It is RECOMMENDED that a small debouncing period of 2.5 sec, between the detection of the condition and the notification, is implemented to prevent simultaneous LinkUp/LinkDown and efmCuLowRateCrossing notifications to be sent. The adaptive nature of the EFMCu technology allows the port to adapt itself to the changes in the copper environment, e.g., an impulse noise, alien crosstalk, or a micro-interruption may temporarily drop one or more PMEs in the aggregation group, causing a rate degradation of the aggregated EFMCu link. The dropped PMEs would then try to re-initialize, possibly at a lower rate than before, adjusting the rate to provide required target SNR margin. Generation of this notification is controlled by the efmCuLowRateCrossingEnable object.
T/F efmCuLowRateCrossingEnable	1.3.6.1.2.1.167.1.1.1.1.8	TruthValue	read-write	Indicates whether efmCuLowRateCrossing notifications should be generated for this interface. A value of true(1) indicates that efmCuLowRateCrossing notification is enabled. A value of false(2) indicates that the notification is disabled. This object is read-write for the -O subtype EFMCu ports (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. This object MUST be maintained in a persistent manner.
efmCuMIB	1.3.6.1.2.1.167			The objects in this MIB module are used to manage the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces 2BASE-TL and 10PASS-TS, defined in IEEE Std. 802.3ah-2004, which is now a part of IEEE Std. 802.3-2005. The following references are used throughout this MIB module: [802.3ah] refers to: IEEE Std 802.3ah-2004: 'IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications - Amendment: Media Access Control Parameters, Physical Layers and Management Parameters for Subscriber Access Networks', 07 September 2004. Of particular interest are Clause 61, 'Physical Coding Sublayer (PCS) and common specifications, type 10PASS-TS and type 2BASE-TL', Clause 30, 'Management', Clause 45, 'Management Data Input/Output (MDIO) Interface', Annex 62A, 'PMD profiles for 10PASS-TS' and Annex 63A, 'PMD profiles for 2BASE-TL'. [G.991.2] refers to: ITU-T Recommendation G.991.2: 'Single-pair High-speed Digital Subscriber Line (SHDSL) transceivers', December 2003. [ANFP] refers to: NICC Document ND1602:2005/08: 'Specification of the Access Network Frequency Plan (ANFP) applicable to transmission systems used on the BT Access Network,' August 2005. 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: Atn - Attenuation CO - Central Office CPE - Customer Premises Equipment EFM - Ethernet in the First Mile EFMCu - EFM Copper MDIO - Management Data Input/Output Mgn - Margin PAF - PME Aggregation Function PBO - Power Back-Off PCS - Physical Coding Sublayer PMD - Physical Medium Dependent PME - Physical Medium Entity PSD - Power Spectral Density SNR - Signal to Noise Ratio TCPAM - Trellis Coded Pulse Amplitude Modulation Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 5066; see the RFC itself for full legal notices.
efmCuNotificationGroup	1.3.6.1.2.1.167.2.1.6			This group supports notifications of significant conditions associated with EFMCu ports.
U32 efmCuNumPMEs	1.3.6.1.2.1.167.1.1.3.1.3	Unsigned32	read-only	The number of PMEs that is currently aggregated by the local PAF (assigned to the EFMCu port using the ifStackTable). This number is never greater than efmCuPAFCapacity. This object SHALL be automatically incremented or decremented when a PME is added or deleted to/from the EFMCu port using the ifStackTable.
efmCuObjects	1.3.6.1.2.1.167.1
INT efmCuPAFAdminState	1.3.6.1.2.1.167.1.1.1.1.1	INTEGER	read-write	Administrative (desired) state of the PAF of the EFMCu port (PCS). When 'disabled', PME aggregation will not be performed by the PCS. No more than a single PME can be assigned to this PCS in this case. When 'enabled', PAF will be performed by the PCS when the link is Up, even on a single attached PME, if PAF is supported. PCS ports incapable of supporting PAF SHALL return a value of 'disabled'. Attempts to 'enable' such ports SHALL be rejected. A PAF 'enabled' port with multiple PMEs assigned cannot be 'disabled'. Attempts to 'disable' such port SHALL be rejected, until at most one PME is left assigned. Changing PAFAdminState is a traffic-disruptive operation and as such SHALL be done when the link is Down. Attempts to change this object SHALL be rejected if the link is Up or Initializing. This object maps to the Clause 30 attribute aPAFAdminState. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the PAF enable bit in the 10P/2B PCS control register. This object MUST be maintained in a persistent manner.
U32 efmCuPAFCapacity	1.3.6.1.2.1.167.1.1.2.1.3	Unsigned32	read-only	Number of PMEs that can be aggregated by the local PAF. The number of PMEs currently assigned to a particular EFMCu port (efmCuNumPMEs) is never greater than efmCuPAFCapacity. This object maps to the Clause 30 attribute aLocalPAFCapacity.
PHY efmCuPAFDiscoveryCode	1.3.6.1.2.1.167.1.1.1.1.2	PhysAddress	read-write	PAF Discovery Code of the EFMCu port (PCS). A unique 6-octet code used by the Discovery function, when PAF is supported. PCS ports incapable of supporting PAF SHALL return a zero-length octet string on an attempt to read this object. An attempt to write to this object SHALL be rejected for such ports. This object MUST be instantiated for the -O subtype PCS before writing operations on the efmCuPAFRemoteDiscoveryCode (Set_if_Clear and Clear_if_Same) are performed by PMEs associated with the PCS. The initial value of this object for -R subtype ports after reset is all zeroes. For -R subtype ports, the value of this object cannot be changed directly. This value may be changed as a result of writing operation on the efmCuPAFRemoteDiscoveryCode object of remote PME of -O subtype, connected to one of the local PMEs associated with the PCS. Discovery MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing. The PAF Discovery Code maps to the local Discovery code variable in PAF (note that it does not have a corresponding Clause 45 register).
efmCuPAFErrorsGroup	1.3.6.1.2.1.167.2.1.3			A collection of objects supporting OPTIONAL error counters of PAF on EFMCu ports.
efmCuPAFGroup	1.3.6.1.2.1.167.2.1.2			A collection of objects supporting OPTIONAL PME Aggregation Function (PAF) and PAF discovery in EFMCu ports.
C32 efmCuPAFInBadFragments	1.3.6.1.2.1.167.1.1.3.1.7	Counter32	read-only	The number of fragments that do not fit into the sequence expected by the frame assembly function and that have been received across the gamma interface and discarded (the frame buffer is flushed to the next valid frame start). This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF bad fragments register. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
C32 efmCuPAFInErrorsEx	1.3.6.1.2.1.167.1.1.3.1.4	Counter32	read-only	The number of fragments that have been received across the gamma interface with RxErr asserted and discarded. This read-only counter is inactive (not incremented) when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF RX error register. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
C32 efmCuPAFInLargeFragments	1.3.6.1.2.1.167.1.1.3.1.6	Counter32	read-only	The number of fragments larger than maxFragmentSize (512 bytes) that have been received across the gamma interface and discarded. This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF large fragments register. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
C32 efmCuPAFInLostEnds	1.3.6.1.2.1.167.1.1.3.1.10	Counter32	read-only	The number of missing EndOfPacket indicators expected by the frame assembly function. This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF lost start of fragment register. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
C32 efmCuPAFInLostFragments	1.3.6.1.2.1.167.1.1.3.1.8	Counter32	read-only	The number of gaps in the sequence of fragments that have been received across the gamma interface (the frame buffer is flushed to the next valid frame start, when fragment/fragments expected by the frame assembly function is/are not received). This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF lost fragment register. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
C32 efmCuPAFInLostStarts	1.3.6.1.2.1.167.1.1.3.1.9	Counter32	read-only	The number of missing StartOfPacket indicators expected by the frame assembly function. This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF lost start of fragment register. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
C32 efmCuPAFInOverflows	1.3.6.1.2.1.167.1.1.3.1.11	Counter32	read-only	The number of fragments, received across the gamma interface and discarded, which would have caused the frame assembly buffer to overflow. This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF overflow register. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
C32 efmCuPAFInSmallFragments	1.3.6.1.2.1.167.1.1.3.1.5	Counter32	read-only	The number of fragments smaller than minFragmentSize (64 bytes) that have been received across the gamma interface and discarded. This read-only counter is inactive when the PAF is unsupported or disabled. Upon disabling the PAF, the counter retains its previous value. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the 10P/2B PAF small fragments register. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
PHY efmCuPAFRemoteDiscoveryCode	1.3.6.1.2.1.167.1.2.1.1.3	PhysAddress	read-write	PAF Remote Discovery Code of the PME port at the CO. The 6-octet Discovery Code of the peer PCS connected via the PME. Reading this object results in a Discovery Get operation. Setting this object to all zeroes results in a Discovery Clear_if_Same operation (the value of efmCuPAFDiscoveryCode at the peer PCS SHALL be the same as efmCuPAFDiscoveryCode of the local PCS associated with the PME for the operation to succeed). Writing a non-zero value to this object results in a Discovery Set_if_Clear operation. A zero-length octet string SHALL be returned on an attempt to read this object when PAF aggregation is not enabled. This object is irrelevant in CPE port (-R) subtypes: in this case, a zero-length octet string SHALL be returned on an attempt to read this object; writing to this object SHALL be rejected. Discovery MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing. If a Clause 45 MDIO Interface to the PMA/PMD is present, then this object is a function of 10P/2B aggregation discovery control register, Discovery operation result bits in 10P/2B aggregation and discovery status register and 10P/2B aggregation discovery code register.
T/F efmCuPAFSupported	1.3.6.1.2.1.167.1.1.2.1.1	TruthValue	read-only	PME Aggregation Function (PAF) capability of the EFMCu port (PCS). This object has a value of true(1) when the PCS can perform PME aggregation on the available PMEs. Ports incapable of PAF SHALL return a value of false(2). This object maps to the Clause 30 attribute aPAFSupported. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the PAF available bit in the 10P/2B capability register.
U32 efmCuPeerPAFCapacity	1.3.6.1.2.1.167.1.1.2.1.4	Unsigned32	read-only	Number of PMEs that can be aggregated by the PAF of the peer PHY (PCS port). A value of 0 is returned when peer PAF capacity is unknown (peer cannot be reached). This object maps to the Clause 30 attribute aRemotePAFCapacity.
EFM efmCuPeerPAFSupported	1.3.6.1.2.1.167.1.1.2.1.2	EfmTruthValueOrUnknown	read-only	PME Aggregation Function (PAF) capability of the EFMCu port (PCS) link partner. This object has a value of true(1) when the remote PCS can perform PME aggregation on its available PMEs. Ports whose peers are incapable of PAF SHALL return a value of false(2). Ports whose peers cannot be reached because of the link state SHALL return a value of unknown(0). This object maps to the Clause 30 attribute aRemotePAFSupported. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the Remote PAF supported bit in the 10P/2B capability register.
efmCuPme	1.3.6.1.2.1.167.1.2
efmCuPme10P	1.3.6.1.2.1.167.1.2.6
BIT efmCuPme10PBandNotchProfiles	1.3.6.1.2.1.167.1.2.6.1.1.5	Bits	read-create	The 10PASS-TS PME Egress Control Band Notch Profile bitmap, as specified in 802.3 Annex 62A, table 62A-4. Possible values are: --------------+--------+------+------------+------+------ 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 profile2(2) 6-2 15-1 17 1.810 2.000 profile3(3) F-5 #02 - - 1.907 1.912 profile4(4) F-5 #03 - - 3.500 3.575 profile5(5) 6-2 - 17 3.500 3.800 profile6(6) - 15-1 - 3.500 4.000 profile7(7) F-5 #04 - - 3.747 3.754 profile8(8) F-5 #05 - - 3.791 3.805 profile9(9) 6-2 - 17 7.000 7.100 profile10(10) F-5 #06 15-1 - 7.000 7.300 profile11(11) 6-2 15-1 1 10.100 10.150 --------------+--------+------+------------+------+------ Any combination of profiles can be specified by ORing individual profiles, for example, a value of 0x2230 selects profiles 2, 6, 10, and 11.
INT efmCuPme10PBandplanPSDMskProfile	1.3.6.1.2.1.167.1.2.6.1.1.3	INTEGER	read-create	The 10PASS-TS PME Bandplan and PSD Mask Profile, as specified in 802.3ah Annex 62A, table 62A-1. Possible values are: --------------+------------------------+------------+-------- Profile Name PSD Mask Bands G.993.1 0/1/2/3/4/5 Bandplan --------------+------------------------+------------+-------- profile1(1) T1.424 FTTCab.M1 x/D/U/D/U A profile2(2) T1.424 FTTEx.M1 x/D/U/D/U A profile3(3) T1.424 FTTCab.M2 x/D/U/D/U A profile4(4) T1.424 FTTEx.M2 x/D/U/D/U A profile5(5) T1.424 FTTCab.M1 D/D/U/D/U A profile6(6) T1.424 FTTEx.M1 D/D/U/D/U A profile7(7) T1.424 FTTCab.M2 D/D/U/D/U A profile8(8) T1.424 FTTEx.M2 D/D/U/D/U A profile9(9) T1.424 FTTCab.M1 U/D/U/D/x A profile10(10) T1.424 FTTEx.M1 U/D/U/D/x A profile11(11) T1.424 FTTCab.M2 U/D/U/D/x A profile12(12) T1.424 FTTEx.M2 U/D/U/D/x A profile13(13) TS 101 270-1 Pcab.M1.A x/D/U/D/U B profile14(14) TS 101 270-1 Pcab.M1.B x/D/U/D/U B profile15(15) TS 101 270-1 Pex.P1.M1 x/D/U/D/U B profile16(16) TS 101 270-1 Pex.P2.M1 x/D/U/D/U B profile17(17) TS 101 270-1 Pcab.M2 x/D/U/D/U B profile18(18) TS 101 270-1 Pex.P1.M2 x/D/U/D/U B profile19(19) TS 101 270-1 Pex.P2.M2 x/D/U/D/U B profile20(20) TS 101 270-1 Pcab.M1.A U/D/U/D/x B profile21(21) TS 101 270-1 Pcab.M1.B U/D/U/D/x B profile22(22) TS 101 270-1 Pex.P1.M1 U/D/U/D/x B profile23(23) TS 101 270-1 Pex.P2.M1 U/D/U/D/x B profile24(24) TS 101 270-1 Pcab.M2 U/D/U/D/x B profile25(25) TS 101 270-1 Pex.P1.M2 U/D/U/D/x B profile26(26) TS 101 270-1 Pex.P2.M2 U/D/U/D/x B profile27(27) G.993.1 F.1.2.1 x/D/U/D/U Annex F 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 profile30(30) T1.424 FTTCab.M1 (ext.) x/D/U/D/U/D Annex A --------------+------------------------+------------+--------
C32 efmCuPme10PFECCorrectedBlocks	1.3.6.1.2.1.167.1.2.6.2.1.1	Counter32	read-only	The number of received and corrected Forward Error Correction (FEC) codewords in this 10PASS-TS PME. This object maps to the aPMEFECCorrectedBlocks attribute in Clause 30. If a Clause 45 MDIO Interface to the PMA/PMD is present, then this object maps to the 10P FEC correctable errors register. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
C32 efmCuPme10PFECUncorrectedBlocks	1.3.6.1.2.1.167.1.2.6.2.1.2	Counter32	read-only	The number of received uncorrectable FEC codewords in this 10PASS-TS PME. This object maps to the aPMEFECUncorrectableBlocks attribute in Clause 30. If a Clause 45 MDIO Interface to the PMA/PMD is present, then this object maps to the 10P FEC uncorrectable errors register. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
INT efmCuPme10PPayloadDRateProfile	1.3.6.1.2.1.167.1.2.6.1.1.6	INTEGER	read-create	The 10PASS-TS PME Downstream Payload Rate Profile, as specified in 802.3 Annex 62A. Possible values are: profile5(5) - 2.5 Mbps profile10(10) - 5 Mbps profile15(15) - 7.5 Mbps profile20(20) - 10 Mbps profile25(25) - 12.5 Mbps profile30(30) - 15 Mbps profile50(50) - 25 Mbps profile70(70) - 35 Mbps profile100(100) - 50 Mbps profile140(140) - 70 Mbps profile200(200) - 100 Mbps Each value represents a target for the PME's Downstream Payload Bitrate as seen at the MII. If the payload rate of the selected profile cannot be achieved based on the loop environment, bandplan, and PSD mask, the PME initialization SHALL fail.
INT efmCuPme10PPayloadURateProfile	1.3.6.1.2.1.167.1.2.6.1.1.7	INTEGER	read-create	The 10PASS-TS PME Upstream Payload Rate Profile, as specified in 802.3 Annex 62A. Possible values are: profile5(5) - 2.5 Mbps profile10(10) - 5 Mbps profile15(15) - 7.5 Mbps profile20(20) - 10 Mbps profile25(25) - 12.5 Mbps profile30(30) - 15 Mbps profile50(50) - 25 Mbps profile70(70) - 35 Mbps profile100(100) - 50 Mbps Each value represents a target for the PME's Upstream Payload Bitrate as seen at the MII. If the payload rate of the selected profile cannot be achieved based on the loop environment, bandplan, and PSD mask, the PME initialization SHALL fail.
STR efmCuPme10PProfileDescr	1.3.6.1.2.1.167.1.2.6.1.1.2	SnmpAdminString	read-create	A textual string containing information about a 10PASS-TS PME profile. The string may include information about data rate and spectral limitations of this particular profile.
efmCuPme10PProfileEntry	1.3.6.1.2.1.167.1.2.6.1.1		not-accessible	Each entry corresponds to a single 10PASS-TS PME profile. Each profile contains a set of parameters, used either for configuration or representation of a 10PASS-TS PME. In case a particular profile is referenced via the efmCuPmeAdminProfile object (or efmCuAdminProfile if efmCuPmeAdminProfile is zero), it represents the desired parameters for the 10PassTS-O PME initialization. If a profile is referenced via an efmCuPmeOperProfile object, it represents the current operating parameters of the PME. Profiles may be created/deleted using the row creation/ deletion mechanism via efmCuPme10PProfileRowStatus. If an 'active' entry is referenced, the entry MUST remain 'active' until all references are removed. Default entries MUST NOT be removed.
efmCuPme10PProfileGroup	1.3.6.1.2.1.167.2.1.8			A collection of objects that constitute a configuration profile for configuration of 10PASS-TS ports.
EFM efmCuPme10PProfileIndex	1.3.6.1.2.1.167.1.2.6.1.1.1	EfmProfileIndex	not-accessible	10PASS-TS PME profile index. This object is the unique index associated with this profile. Entries in this table are referenced via efmCuAdminProfile or efmCuPmeAdminProfile.
ROW efmCuPme10PProfileRowStatus	1.3.6.1.2.1.167.1.2.6.1.1.8	RowStatus	read-create	This object controls creation, modification, or deletion of the associated entry in efmCuPme10PProfileTable per the semantics of RowStatus. If an active entry is referenced via efmCuAdminProfile or efmCuPmeAdminProfile, the entry MUST remain 'active' until all references are removed. An 'active' entry SHALL NOT be modified. In order to modify an existing entry, it MUST be taken out of service (by setting this object to 'notInService'), modified, and set 'active' again.
efmCuPme10PProfileTable	1.3.6.1.2.1.167.1.2.6.1		not-accessible	This table supports definitions of configuration profiles for 10PASS-TS PMEs. The first 22 entries in this table SHALL always be defined as follows (see 802.3ah Annex 62B.3, table 62B-1): -------+--------+----+---------+-----+-----+--------------- Profile Bandplan UPBO BandNotch DRate URate Comment Index PSDMask# p# p# p# p# -------+--------+----+---------+-----+-----+--------------- 1 1 3 2,6,10,11 20 20 default profile 2 13 5 0 20 20 3 1 1 0 20 20 4 16 0 0 100 100 5 16 0 0 70 50 6 6 0 0 50 10 7 17 0 0 30 30 8 8 0 0 30 5 9 4 0 0 25 25 10 4 0 0 15 15 11 23 0 0 10 10 12 23 0 0 5 5 13 16 0 2,5,9,11 100 100 14 16 0 2,5,9,11 70 50 15 6 0 2,6,10,11 50 10 16 17 0 2,5,9,11 30 30 17 8 0 2,6,10,11 30 5 18 4 0 2,6,10,11 25 25 19 4 0 2,6,10,11 15 15 20 23 0 2,5,9,11 10 10 21 23 0 2,5,9,11 5 5 22 30 0 0 200 50 -------+--------+----+---------+-----+-----+--------------- These default entries SHALL be created during agent initialization and MUST NOT be deleted. Entries following the first 22 can be dynamically created and deleted to provide custom administrative (configuration) profiles and automatic operating profiles. This table MUST be maintained in a persistent manner.
efmCuPme10PStatusEntry	1.3.6.1.2.1.167.1.2.6.2.1		not-accessible	An entry in the EFMCu 10PASS-TS PME Status table.
efmCuPme10PStatusGroup	1.3.6.1.2.1.167.2.1.9			A collection of objects providing status information specific to 10PASS-TS PMEs.
efmCuPme10PStatusTable	1.3.6.1.2.1.167.1.2.6.2		not-accessible	This table provides status information of EFMCu 10PASS-TS PMEs (modems). This table contains live data from the equipment. As such, it is NOT persistent.
INT efmCuPme10PUPBOReferenceProfile	1.3.6.1.2.1.167.1.2.6.1.1.4	INTEGER	read-create	The 10PASS-TS PME Upstream Power Back-Off (UPBO) Reference PSD Profile, as specified in 802.3 Annex 62A, table 62A-3. Possible values are: ------------+----------------------------- Profile Name Reference PSD ------------+----------------------------- profile0(0) no profile profile1(1) T1.424 Noise A M1 profile2(2) T1.424 Noise A M2 profile3(3) T1.424 Noise F M1 profile4(4) T1.424 Noise F M2 profile5(5) TS 101 270-1 Noise A&B profile6(6) TS 101 270-1 Noise C profile7(7) TS 101 270-1 Noise D profile8(8) TS 101 270-1 Noise E profile9(9) TS 101 270-1 Noise F ------------+-----------------------------
efmCuPme2B	1.3.6.1.2.1.167.1.2.5
INT efmCuPme2BConstellation	1.3.6.1.2.1.167.1.2.5.2.1.8	INTEGER	read-create	TCPAM Constellation of the 2BASE-TL PME. The possible values are: adaptive(0) - either 16- or 32-TCPAM tcpam16(1) - 16-TCPAM tcpam32(2) - 32-TCPAM The value of adaptive(0) in the administrative profile means that the constellation is not fixed and SHALL be set to maximize the attainable rate, under the spectral limitations placed by the efmCuPme2BRegion and efmCuPme2BsMode. If a Clause 45 MDIO Interface to the PME is present, then this object maps to the Constellation1 bits in the 2B general parameter register.
U32 efmCuPme2BEquivalentLength	1.3.6.1.2.1.167.1.2.5.4.1.2	Unsigned32	read-create	Maximum allowed equivalent loop's physical length in meters for the specified data rates. An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a perfect square root attenuation characteristic, without any bridged taps.
U32 efmCuPme2BMaxDataRate	1.3.6.1.2.1.167.1.2.5.2.1.6	Unsigned32	read-create	Maximum Data Rate for the 2BASE-TL PME. This object can take values of (n x 64)Kbps, where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM encoding. The data rate of the 2BASE-TL PME is considered 'fixed' when the value of this object equals that of efmCuPme2BMinDataRate. If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in the administrative profile, the data rate is considered 'adaptive', and SHALL be set to the maximum attainable rate not exceeding efmCuPme2BMaxDataRate, under the spectral limitations placed by the efmCuPme2BRegion and efmCuPme2BsMode. Note that the current operational data rate of the PME is represented by the ifSpeed object of IF-MIB. If a Clause 45 MDIO Interface to the PME is present, then this object maps to the Max Data Rate1 bits in the 2B PMD parameters register. This object MUST be maintained in a persistent manner.
U32 efmCuPme2BMaxDataRatePam16	1.3.6.1.2.1.167.1.2.5.4.1.3	Unsigned32	read-create	Maximum data rate for a 2BASE-TL PME at the specified equivalent loop's length using TC-PAM16 encoding. The value of zero means that TC-PAM16 encoding should not be used at this distance.
U32 efmCuPme2BMaxDataRatePam32	1.3.6.1.2.1.167.1.2.5.4.1.4	Unsigned32	read-create	Maximum data rate for a 2BASE-TL PME at the specified equivalent loop's length using TC-PAM32 encoding. The value of zero means that TC-PAM32 encoding should not be used at this distance.
U32 efmCuPme2BMinDataRate	1.3.6.1.2.1.167.1.2.5.2.1.5	Unsigned32	read-create	Minimum Data Rate for the 2BASE-TL PME. This object can take values of (n x 64)Kbps, where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM encoding. The data rate of the 2BASE-TL PME is considered 'fixed' when the value of this object equals that of efmCuPme2BMaxDataRate. If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in the administrative profile, the data rate is considered 'adaptive', and SHALL be set to the maximum attainable rate not exceeding efmCuPme2BMaxDataRate, under the spectral limitations placed by the efmCuPme2BRegion and efmCuPme2BsMode. Note that the current operational data rate of the PME is represented by the ifSpeed object of IF-MIB. If a Clause 45 MDIO Interface to the PME is present, then this object maps to the Min Data Rate1 bits in the 2B PMD parameters register. This object MUST be maintained in a persistent manner.
U32 efmCuPme2BPower	1.3.6.1.2.1.167.1.2.5.2.1.7	Unsigned32	read-create	Signal Transmit Power. Multiple of 0.5 dBm. The value of 0 in the administrative profile means that the signal transmit power is not fixed and SHALL be set to maximize the attainable rate, under the spectral limitations placed by the efmCuPme2BRegion and efmCuPme2BsMode. If a Clause 45 MDIO Interface to the PME is present, then this object maps to the Power1 bits in the 2B PMD parameters register.
STR efmCuPme2BProfileDescr	1.3.6.1.2.1.167.1.2.5.2.1.2	SnmpAdminString	read-create	A textual string containing information about a 2BASE-TL PME profile. The string may include information about the data rate and spectral limitations of this particular profile.
efmCuPme2BProfileEntry	1.3.6.1.2.1.167.1.2.5.2.1		not-accessible	Each entry corresponds to a single 2BASE-TL PME profile. Each profile contains a set of parameters, used either for configuration or representation of a 2BASE-TL PME. In case a particular profile is referenced via the efmCuPmeAdminProfile object (or efmCuAdminProfile if efmCuPmeAdminProfile is zero), it represents the desired parameters for the 2BaseTL-O PME initialization. If a profile is referenced via an efmCuPmeOperProfile object, it represents the current operating parameters of an operational PME. Profiles may be created/deleted using the row creation/ deletion mechanism via efmCuPme2BProfileRowStatus. If an active entry is referenced, the entry MUST remain 'active' until all references are removed. Default entries MUST NOT be removed.
efmCuPme2BProfileGroup	1.3.6.1.2.1.167.2.1.7			A collection of objects that constitute a configuration profile for configuration of 2BASE-TL ports.
EFM efmCuPme2BProfileIndex	1.3.6.1.2.1.167.1.2.5.2.1.1	EfmProfileIndex	not-accessible	2BASE-TL PME profile index. This object is the unique index associated with this profile. Entries in this table are referenced via efmCuAdminProfile or efmCuPmeAdminProfile objects.
ROW efmCuPme2BProfileRowStatus	1.3.6.1.2.1.167.1.2.5.2.1.9	RowStatus	read-create	This object controls the creation, modification, or deletion of the associated entry in the efmCuPme2BProfileTable per the semantics of RowStatus. If an 'active' entry is referenced via efmCuAdminProfile or efmCuPmeAdminProfile instance(s), the entry MUST remain 'active'. An 'active' entry SHALL NOT be modified. In order to modify an existing entry, it MUST be taken out of service (by setting this object to 'notInService'), modified, and set 'active' again.
efmCuPme2BProfileTable	1.3.6.1.2.1.167.1.2.5.2		not-accessible	This table supports definitions of administrative and operating profiles for 2BASE-TL PMEs. The first 14 entries in this table SHALL always be defined as follows (see 802.3ah Annex 63A): -------+-------+-------+-----+------+-------------+----------- Profile MinRate MaxRate Power Region Constellation Comment index (Kbps) (Kbps) (dBm) -------+-------+-------+-----+------+-------------+----------- 1 5696 5696 13.5 1 32-TCPAM default 2 3072 3072 13.5 1 32-TCPAM 3 2048 2048 13.5 1 16-TCPAM 4 1024 1024 13.5 1 16-TCPAM 5 704 704 13.5 1 16-TCPAM 6 512 512 13.5 1 16-TCPAM 7 5696 5696 14.5 2 32-TCPAM 8 3072 3072 14.5 2 32-TCPAM 9 2048 2048 14.5 2 16-TCPAM 10 1024 1024 13.5 2 16-TCPAM 11 704 704 13.5 2 16-TCPAM 12 512 512 13.5 2 16-TCPAM 13 192 5696 0 1 0 best effort 14 192 5696 0 2 0 best effort -------+-------+-------+-----+------+-------------+----------- These default entries SHALL be created during agent initialization and MUST NOT be deleted. Entries following the first 14 can be dynamically created and deleted to provide custom administrative (configuration) profiles and automatic operating profiles. This table MUST be maintained in a persistent manner.
efmCuPme2BReachRateEntry	1.3.6.1.2.1.167.1.2.5.4.1		not-accessible	Each entry specifies maximum 2BASE-TL PME data rates allowed for a certain equivalent loop length, when using 16-TCPAM or 32-TCPAM encoding. When a 2BASE-TL PME is initialized, its data rate MUST NOT exceed one of the following limitations: - the value of efmCuPme2BMaxDataRate - maximum data rate allowed by efmCuPme2BRegion and efmCuPme2BPower - maximum data rate for a given encoding specified in the efmCuPme2BsModeEntry, corresponding to the equivalent loop length, estimated by the PME It is RECOMMENDED that the efmCuPme2BEquivalentLength values are assigned in increasing order, starting from the minimum value. Entries may be created/deleted using the row creation/ deletion mechanism via efmCuPme2ReachRateRowStatus.
EFM efmCuPme2BReachRateIndex	1.3.6.1.2.1.167.1.2.5.4.1.1	EfmProfileIndex	not-accessible	2BASE-TL custom spectral mode Reach-Rate table index. This object is the unique index associated with each entry.
ROW efmCuPme2BReachRateRowStatus	1.3.6.1.2.1.167.1.2.5.4.1.5	RowStatus	read-create	This object controls the creation, modification, or deletion of the associated entry in the efmCuPme2BReachRateTable per the semantics of RowStatus. If an 'active' entry is referenced via efmCuPme2BsMode instance(s), the entry MUST remain 'active'. An 'active' entry SHALL NOT be modified. In order to modify an existing entry, it MUST be taken out of service (by setting this object to 'notInService'), modified, and set 'active' again.
efmCuPme2BReachRateTable	1.3.6.1.2.1.167.1.2.5.4		not-accessible	This table supports the definition of administrative custom spectral modes for 2BASE-TL PMEs, providing spectral limitations in addition to those specified by efmCuPme2BRegion. The spectral regulations in some countries (e.g., UK ANFP) limit the length of the loops for certain data rates. This table allows these country-specific limitations to be specified. Below is an example of this table for [ANFP]: ----------+-------+------- Equivalent MaxRate MaxRate Length PAM16 PAM32 (m) (Kbps) (Kbps) ----------+-------+------- 975 2304 5696 1125 2304 5504 1275 2304 5120 1350 2304 4864 1425 2304 4544 1500 2304 4288 1575 2304 3968 1650 2304 3776 1725 2304 3520 1800 2304 3264 1875 2304 3072 1950 2048 2688 2100 1792 2368 2250 1536 0 2400 1408 0 2550 1280 0 2775 1152 0 2925 1152 0 3150 1088 0 3375 1024 0 ----------+-------+------- Entries in this table referenced by an efmCuPme2BsMode instance MUST NOT be deleted. This table MUST be maintained in a persistent manner.
INT efmCuPme2BRegion	1.3.6.1.2.1.167.1.2.5.2.1.3	INTEGER	read-create	Regional settings for a 2BASE-TL PME, as specified in the relevant Regional Annex of [G.991.2]. Regional settings specify the Power Spectral Density (PSD) mask and the Power Back-Off (PBO) values, and place limitations on the max allowed data rate, power, and constellation. Possible values for this object are: region1 - Annexes A and F (e.g., North America) region2 - Annexes B and G (e.g., Europe) Annex A/B specify regional settings for data rates 192-2304 Kbps using 16-TCPAM encoding. Annex F/G specify regional settings for rates 2320-3840 Kbps using 16-TCPAM encoding and 768-5696 Kbps using 32-TCPAM encoding. If a Clause 45 MDIO Interface to the PME is present, then this object partially maps to the Region bits in the 2B general parameter register.
EFM efmCuPme2BsMode	1.3.6.1.2.1.167.1.2.5.2.1.4	EfmProfileIndexOrZero	read-create	Desired custom Spectral Mode for a 2BASE-TL PME. This object is a pointer to an entry in efmCuPme2BsModeTable and a block of entries in efmCuPme2BRateReachTable, which together define (country-specific) reach-dependent rate limitations in addition to those defined by efmCuPme2BRegion. The value of this object is the index of the referenced spectral mode. The value of zero (default) indicates that no specific spectral mode is applicable. Attempts to set this object to a value that is not the value of the index for an active entry in the corresponding spectral mode table MUST be rejected.
STR efmCuPme2BsModeDescr	1.3.6.1.2.1.167.1.2.5.3.1.2	SnmpAdminString	read-create	A textual string containing information about a 2BASE-TL PME spectral mode. The string may include information about corresponding (country-specific) spectral regulations and rate/reach limitations of this particular spectral mode.
efmCuPme2BsModeEntry	1.3.6.1.2.1.167.1.2.5.3.1		not-accessible	Each entry specifies a spectral mode description and its index, which is used to reference corresponding entries in the efmCu2BReachRateTable. Entries may be created/deleted using the row creation/ deletion mechanism via efmCuPme2BsModeRowStatus.
EFM efmCuPme2BsModeIndex	1.3.6.1.2.1.167.1.2.5.3.1.1	EfmProfileIndex	not-accessible	2BASE-TL PME Spectral Mode index. This object is the unique index associated with this spectral mode. Entries in this table are referenced via the efmCuPme2BsMode object.
ROW efmCuPme2BsModeRowStatus	1.3.6.1.2.1.167.1.2.5.3.1.3	RowStatus	read-create	This object controls creation, modification, or deletion of the associated entry in efmCuPme2BsModeTable per the semantics of RowStatus. If an 'active' entry is referenced via efmCuPme2BsMode instance(s), the entry MUST remain 'active'. An 'active' entry SHALL NOT be modified. In order to modify an existing entry, it MUST be taken out of service (by setting this object to 'notInService'), modified, and set 'active' again.
efmCuPme2BsModeTable	1.3.6.1.2.1.167.1.2.5.3		not-accessible	This table, together with efmCu2BReachRateTable, supports definition of administrative custom spectral modes for 2BASE-TL PMEs, describing spectral limitations in addition to those specified by efmCuPme2BRegion. In some countries, spectral regulations (e.g., UK ANFP) limit the length of the loops for certain data rates. This table allows these country-specific limitations to be specified. Entries in this table referenced by the efmCuPme2BsMode MUST NOT be deleted until all the active references are removed. This table MUST be maintained in a persistent manner.
EFM efmCuPmeAdminProfile	1.3.6.1.2.1.167.1.2.1.1.2	EfmProfileIndexOrZero	read-write	Desired PME configuration profile. This object is a pointer to an entry in either the efmCuPme2BProfileTable or the efmCuPme10PProfileTable, depending on the current operating SubType of the PME. The value of this object is the index of the referenced profile. The value of zero (default) indicates that the PME is configured via the efmCuAdminProfile object for the PCS port to which this PME is assigned. That is, the profile referenced by efmCuPmeAdminProfile takes precedence over the profile(s) referenced by efmCuAdminProfile. This object is writable and readable for the CO subtype PMEs (2BaseTL-O or 10PassTS-O). It is irrelevant for the CPE subtype (2BaseTL-R or 10PassTS-R) -- a zero value SHALL be returned on an attempt to read this object and any attempt to change this object MUST be rejected in this case. Note that the current operational profile value is available via efmCuPmeOperProfile object. Any modification of this object MUST be performed when the link is Down. Attempts to change this object MUST be rejected, if the link is Up or Initializing. Attempts to set this object to a value that is not the value of the index for an active entry in the corresponding profile table MUST be rejected. This object maps to the Clause 30 attribute aProfileSelect. This object MUST be maintained in a persistent manner.
INT efmCuPmeAdminSubType	1.3.6.1.2.1.167.1.2.1.1.1	INTEGER	read-write	Administrative (desired) subtype of the PME. Possible values are: ieee2BaseTLO - PME SHALL operate as 2BaseTL-O ieee2BaseTLR - PME SHALL operate as 2BaseTL-R ieee10PassTSO - PME SHALL operate as 10PassTS-O ieee10PassTSR - PME SHALL operate as 10PassTS-R ieee2BaseTLor10PassTSR - PME SHALL operate as 2BaseTL-R or 10PassTS-R. The actual value will be set by the -O link partner during initialization (handshake). ieee2BaseTLor10PassTSO - PME SHALL operate as 2BaseTL-O (preferred) or 10PassTS-O. The actual value will be set during initialization depending on the -R link partner capability (i.e., if -R is incapable of the preferred 2BaseTL mode, 10PassTS will be used). ieee10PassTSor2BaseTLO - PME SHALL operate as 10PassTS-O (preferred) or 2BaseTL-O. The actual value will be set during initialization depending on the -R link partner capability (i.e., if -R is incapable of the preferred 10PassTS mode, 2BaseTL will be used). Changing efmCuPmeAdminSubType is a traffic-disruptive operation and as such SHALL be done when the link is Down. Attempts to change this object SHALL be rejected if the link is Up or Initializing. Attempts to change this object to an unsupported subtype (see efmCuPmeSubTypesSupported) SHALL be rejected. The current operational subtype is indicated by the efmCuPmeOperSubType variable. If a Clause 45 MDIO Interface to the PMA/PMD is present, then this object combines values of the Port subtype select bits and the PMA/PMD type selection bits in the 10P/2B PMA/PMD control register.
efmCuPmeCapabilityEntry	1.3.6.1.2.1.167.1.2.2.1		not-accessible	An entry in the EFMCu PME Capability table. Each entry represents common aspects of an EFMCu PME port indexed by the ifIndex. Note that an EFMCu PME port can be stacked below a single PCS port, also indexed by ifIndex, possibly together with other PME ports if PAF is enabled.
efmCuPmeCapabilityTable	1.3.6.1.2.1.167.1.2.2		not-accessible	Table for the configuration of common aspects for EFMCu 2BASE-TL/10PASS-TS PME ports (modems). The configuration of aspects specific to 2BASE-TL or 10PASS-TS PME types is represented in the efmCuPme2BConfTable and the efmCuPme10PConfTable, respectively. Entries in this table MUST be maintained in a persistent manner.
efmCuPmeConfEntry	1.3.6.1.2.1.167.1.2.1.1		not-accessible	An entry in the EFMCu PME Configuration table. Each entry represents common aspects of an EFMCu PME port indexed by the ifIndex. Note that an EFMCu PME port can be stacked below a single PCS port, also indexed by ifIndex, possibly together with other PME ports if PAF is enabled.
T/F efmCuPmeConfigInitFailEnable	1.3.6.1.2.1.167.1.2.1.1.9	TruthValue	read-write	Indicates whether efmCuPmeConfigInitFailure notifications should be generated for this interface. A value of true(1) indicates that efmCuPmeConfigInitFailure notification is enabled. A value of false(2) indicates that the notification is disabled.
NTF efmCuPmeConfigInitFailure	1.3.6.1.2.1.167.1.2.0.4			This notification indicates that PME initialization has failed, due to inability of the PME link to achieve the requested configuration profile. Generation of this notification is controlled by the efmCuPmeConfigInitFailEnable object.
efmCuPmeConfTable	1.3.6.1.2.1.167.1.2.1		not-accessible	Table for Configuration of common aspects for EFMCu 2BASE-TL/10PASS-TS PME ports (modems). Configuration of aspects specific to 2BASE-TL or 10PASS-TS PME types is represented in efmCuPme2BConfTable and efmCuPme10PConfTable, respectively. Entries in this table MUST be maintained in a persistent manner.
NTF efmCuPmeDeviceFault	1.3.6.1.2.1.167.1.2.0.3			This notification indicates that a fault in the PME has been detected by a vendor-specific diagnostic or a self-test. Generation of this notification is controlled by the efmCuPmeDeviceFaultEnable object.
T/F efmCuPmeDeviceFaultEnable	1.3.6.1.2.1.167.1.2.1.1.8	TruthValue	read-write	Indicates whether efmCuPmeDeviceFault notifications should be generated for this interface. A value of true(1) indicates that efmCuPmeDeviceFault notification is enabled. A value of false(2) indicates that the notification is disabled.
U32 efmCuPmeEquivalentLength	1.3.6.1.2.1.167.1.2.3.1.9	Unsigned32	read-only	An estimate of the equivalent loop's physical length in meters, as perceived by the PME after the link is established. An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a perfect square root attenuation characteristic, without any bridged taps. The value of 65535 is returned if the link is Down or Initializing or the PME is unable to estimate the equivalent length. For a 10BASE-TL PME, if a Clause 45 MDIO Interface to the PME is present, then this object maps to the 10P Electrical Length register.
BIT efmCuPmeFltStatus	1.3.6.1.2.1.167.1.2.3.1.2	Bits	read-only	Current/Last PME link Fault Status. This is a bitmap of possible conditions. The various bit positions are: lossOfFraming - Loss of Framing for 10P or Loss of Sync word for 2B PMD or Loss of 64/65-octet framing. snrMgnDefect - SNR margin dropped below the threshold. lineAtnDefect - Line Attenuation exceeds the threshold. deviceFault - Indicates a vendor-dependent diagnostic or self-test fault has been detected. configInitFailure - Configuration initialization failure, due to inability of the PME link to support the configuration profile, requested during initialization. protocolInitFailure - Protocol initialization failure, due to an incompatible protocol used by the peer PME during init (that could happen if a peer PMD is a regular G.SDHSL/VDSL modem instead of a 2BASE-TL/10PASS-TS PME). This object is intended to supplement ifOperStatus in IF-MIB. This object holds information about the last fault. efmCuPmeFltStatus is cleared by the device restart. In addition, lossOfFraming, configInitFailure, and protocolInitFailure are cleared by PME init; deviceFault is cleared by successful diagnostics/test; snrMgnDefect and lineAtnDefect are cleared by SNR margin and Line attenuation, respectively, returning to norm and by PME init. This object partially maps to the Clause 30 attribute aPMEStatus. If a Clause 45 MDIO Interface to the PME is present, then this object consolidates information from various PMA/PMD registers, namely: Fault bit in PMA/PMD status 1 register, 10P/2B PMA/PMD link loss register, 10P outgoing indicator bits status register, 10P incoming indicator bits status register, 2B state defects register.
efmCuPmeGroup	1.3.6.1.2.1.167.2.1.4			A collection of objects providing information about a 2BASE-TL/10PASS-TS PME.
I32 efmCuPmeLineAtn	1.3.6.1.2.1.167.1.2.3.1.7	Integer32	read-only	The current Line Attenuation in dB as perceived by the local PME. The value of 65535 is returned when the PME is Down or Initializing. If a Clause 45 MDIO Interface is present, then this object maps to the Line Attenuation register.
NTF efmCuPmeLineAtnCrossing	1.3.6.1.2.1.167.1.2.0.1			This notification indicates that the loop attenuation threshold (as per the efmCuPmeThreshLineAtn value) has been reached/exceeded for the 2BASE-TL/10PASS-TS PME. This notification MAY be sent on the crossing event in both directions: from normal to exceeded and from exceeded to normal. It is RECOMMENDED that a small debouncing period of 2.5 sec, between the detection of the condition and the notification, is implemented to prevent intermittent notifications from being sent. Generation of this notification is controlled by the efmCuPmeLineAtnCrossingEnable object.
T/F efmCuPmeLineAtnCrossingEnable	1.3.6.1.2.1.167.1.2.1.1.6	TruthValue	read-write	Indicates whether efmCuPmeLineAtnCrossing notifications should be generated for this interface. A value of true(1) indicates that efmCuPmeLineAtnCrossing notification is enabled. A value of false(2) indicates that the notification is disabled.
efmCuPmeNotifications	1.3.6.1.2.1.167.1.2.0
EFM efmCuPmeOperProfile	1.3.6.1.2.1.167.1.2.3.1.4	EfmProfileIndexOrZero	read-only	PME current operating profile. This object is a pointer to an entry in either the efmCuPme2BProfileTable or the efmCuPme10PProfileTable, depending on the current operating SubType of the PME as indicated by efmCuPmeOperSubType. Note that a profile entry to which efmCuPmeOperProfile is pointing can be created automatically to reflect achieved parameters in adaptive (not fixed) initialization, i.e., values of efmCuPmeOperProfile and efmCuAdminProfile or efmCuPmeAdminProfile may differ. The value of zero indicates that the PME is Down or Initializing. This object partially maps to the aOperatingProfile attribute in Clause 30.
INT efmCuPmeOperStatus	1.3.6.1.2.1.167.1.2.3.1.1	INTEGER	read-only	Current PME link Operational Status. Possible values are: up(1) - The link is Up and ready to pass 64/65-octet encoded frames or fragments. downNotReady(2) - The link is Down and the PME does not detect Handshake tones from its peer. This value may indicate a possible problem with the peer PME. downReady(3) - The link is Down and the PME detects Handshake tones from its peer. init(4) - The link is Initializing, as a result of ifAdminStatus being set to 'up' for a particular PME or a PCS to which the PME is connected. This object is intended to supplement the Down(2) state of ifOperStatus. This object partially maps to the Clause 30 attribute aPMEStatus. 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 PMA/PMD status register.
INT efmCuPmeOperSubType	1.3.6.1.2.1.167.1.2.3.1.3	INTEGER	read-only	Current operational subtype of the PME. Possible values are: ieee2BaseTLO - PME operates as 2BaseTL-O ieee2BaseTLR - PME operates as 2BaseTL-R ieee10PassTSO - PME operates as 10PassTS-O ieee10PassTSR - PME operates as 10PassTS-R The desired operational subtype of the PME can be configured via the efmCuPmeAdminSubType variable. If a Clause 45 MDIO Interface to the PMA/PMD is present, then this object combines values of the Port subtype select bits, the PMA/PMD type selection bits in the 10P/2B PMA/PMD control register, and the PMA/PMD link status bits in the 10P/2B PMA/PMD status register.
I32 efmCuPmePeerLineAtn	1.3.6.1.2.1.167.1.2.3.1.8	Integer32	read-only	The current Line Attenuation in dB as perceived by the remote (link partner) PME. The value of 65535 is returned when the PME is Down or Initializing. This object is irrelevant for the -R PME subtypes. The value of 65535 SHALL be returned in this case. If a Clause 45 MDIO Interface is present, then this object maps to the 20P/2B link partner Line Attenuation register.
I32 efmCuPmePeerSnrMgn	1.3.6.1.2.1.167.1.2.3.1.6	Integer32	read-only	The current SNR margin in dB with respect to the received signal, as perceived by the remote (link partner) PME. The value of 65535 is returned when the PME is Down or Initializing. This object is irrelevant for the -R PME subtypes. The value of 65535 SHALL be returned in this case. If a Clause 45 MDIO Interface is present, then this object maps to the 10P/2B link partner RX SNR margin register.
T/F efmCuPmeProtocolInitFailEnable	1.3.6.1.2.1.167.1.2.1.1.10	TruthValue	read-write	Indicates whether efmCuPmeProtocolInitFailure notifications should be generated for this interface. A value of true(1) indicates that efmCuPmeProtocolInitFailure notification is enabled. A value of false(2) indicates that the notification is disabled.
NTF efmCuPmeProtocolInitFailure	1.3.6.1.2.1.167.1.2.0.5			This notification indicates that the peer PME was using an incompatible protocol during initialization. Generation of this notification is controlled by the efmCuPmeProtocolInitFailEnable object.
I32 efmCuPmeSnrMgn	1.3.6.1.2.1.167.1.2.3.1.5	Integer32	read-only	The current Signal to Noise Ratio (SNR) margin with respect to the received signal as perceived by the local PME. The value of 65535 is returned when the PME is Down or Initializing. This object maps to the aPMESNRMgn attribute in Clause 30. If a Clause 45 MDIO Interface is present, then this object maps to the 10P/2B RX SNR margin register.
NTF efmCuPmeSnrMgnCrossing	1.3.6.1.2.1.167.1.2.0.2			This notification indicates that the SNR margin threshold (as per the efmCuPmeThreshSnrMgn value) has been reached/exceeded for the 2BASE-TL/10PASS-TS PME. This notification MAY be sent on the crossing event in both directions: from normal to exceeded and from exceeded to normal. It is RECOMMENDED that a small debouncing period of 2.5 sec, between the detection of the condition and the notification, is implemented to prevent intermittent notifications from being sent. Generation of this notification is controlled by the efmCuPmeSnrMgnCrossingEnable object.
T/F efmCuPmeSnrMgnCrossingEnable	1.3.6.1.2.1.167.1.2.1.1.7	TruthValue	read-write	Indicates whether efmCuPmeSnrMgnCrossing notifications should be generated for this interface. A value of true(1) indicates that efmCuPmeSnrMgnCrossing notification is enabled. A value of false(2) indicates that the notification is disabled.
efmCuPmeStatusEntry	1.3.6.1.2.1.167.1.2.3.1		not-accessible	An entry in the EFMCu PME Status table. Each entry represents common aspects of an EFMCu PME port indexed by the ifIndex. Note that an EFMCu PME port can be stacked below a single PCS port, also indexed by ifIndex, possibly together with other PME ports if PAF is enabled.
efmCuPmeStatusTable	1.3.6.1.2.1.167.1.2.3		not-accessible	This table provides common status information of EFMCu 2BASE-TL/10PASS-TS PME ports. Status information specific to 10PASS-TS PME is represented in efmCuPme10PStatusTable. This table contains live data from the equipment. As such, it is NOT persistent.
BIT efmCuPmeSubTypesSupported	1.3.6.1.2.1.167.1.2.2.1.1	Bits	read-only	PME supported subtypes. This is a bitmap of possible subtypes. The various bit positions are: ieee2BaseTLO - PME is capable of operating as 2BaseTL-O ieee2BaseTLR - PME is capable of operating as 2BaseTL-R ieee10PassTSO - PME is capable of operating as 10PassTS-O ieee10PassTSR - PME is capable of operating as 10PassTS-R The desired mode of operation is determined by efmCuPmeAdminSubType, while efmCuPmeOperSubType reflects the current operating mode. If a Clause 45 MDIO Interface to the PCS is present, then this object combines the 10PASS-TS capable and 2BASE-TL capable bits in the 10P/2B PMA/PMD speed ability register and the CO supported and CPE supported bits in the 10P/2B PMA/PMD status register.
C32 efmCuPmeTCCodingErrors	1.3.6.1.2.1.167.1.2.3.1.10	Counter32	read-only	The number of 64/65-octet encapsulation errors. This counter is incremented for each 64/65-octet encapsulation error detected by the 64/65-octet receive function. This object maps to aTCCodingViolations attribute in Clause 30. If a Clause 45 MDIO Interface to the PME TC is present, then this object maps to the TC coding violations register (see 45.2.6.12). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
C32 efmCuPmeTCCrcErrors	1.3.6.1.2.1.167.1.2.3.1.11	Counter32	read-only	The number of TC-CRC errors. This counter is incremented for each TC-CRC error detected by the 64/65-octet receive function (see 61.3.3.3 and Figure 61-19). This object maps to aTCCRCErrors attribute in Clause 30. If a Clause 45 MDIO Interface to the PME TC is present, then this object maps to the TC CRC error register (see 45.2.6.11). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime, defined in IF-MIB.
I32 efmCuPmeThreshLineAtn	1.3.6.1.2.1.167.1.2.1.1.4	Integer32	read-write	Desired Line Attenuation threshold for the 2B/10P PME. This object configures the line attenuation alarm threshold. When the current value of Line Attenuation reaches or exceeds this threshold, an efmCuPmeLineAtnCrossing notification MAY be generated, if enabled by efmCuPmeLineAtnCrossingEnable. This object is writable for the CO subtype PMEs (-O). It is read-only for the CPE subtype (-R). Changing of the Line Attenuation threshold MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing. If a Clause 45 MDIO Interface to the PME is present, then this object maps to the loop attenuation threshold bits in the 2B PMD line quality thresholds register.
I32 efmCuPmeThreshSnrMgn	1.3.6.1.2.1.167.1.2.1.1.5	Integer32	read-write	Desired SNR margin threshold for the 2B/10P PME. This object configures the SNR margin alarm threshold. When the current value of SNR margin reaches or exceeds this threshold, an efmCuPmeSnrMgnCrossing notification MAY be generated, if enabled by efmCuPmeSnrMgnCrossingEnable. This object is writable for the CO subtype PMEs (2BaseTL-O/10PassTS-O). It is read-only for the CPE subtype (2BaseTL-R/10PassTS-R). Changing of the SNR margin threshold MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing. If a Clause 45 MDIO Interface to the PME is present, then this object maps to the SNR margin threshold bits in the 2B PMD line quality thresholds register.
efmCuPort	1.3.6.1.2.1.167.1.1
efmCuPortCapabilityEntry	1.3.6.1.2.1.167.1.1.2.1		not-accessible	An entry in the EFMCu Port Capability table. Each entry represents an EFMCu port indexed by the ifIndex. Note that an EFMCu PCS port runs on top of a single or multiple PME port(s), which are also indexed by ifIndex.
efmCuPortCapabilityTable	1.3.6.1.2.1.167.1.1.2		not-accessible	Table for Capabilities of EFMCu 2BASE-TL/10PASS-TS (PCS) Ports. Entries in this table MUST be maintained in a persistent manner
efmCuPortConfEntry	1.3.6.1.2.1.167.1.1.1.1		not-accessible	An entry in the EFMCu Port Configuration table. Each entry represents an EFMCu port indexed by the ifIndex. Note that an EFMCu PCS port runs on top of a single or multiple PME port(s), which are also indexed by ifIndex.
efmCuPortConfTable	1.3.6.1.2.1.167.1.1.1		not-accessible	Table for Configuration of EFMCu 2BASE-TL/10PASS-TS (PCS) Ports. Entries in this table MUST be maintained in a persistent manner.
efmCuPortNotifications	1.3.6.1.2.1.167.1.1.0
INT efmCuPortSide	1.3.6.1.2.1.167.1.1.3.1.2	INTEGER	read-only	EFM port mode of operation (subtype). The value of 'subscriber' indicates that the port is designated as '-R' subtype (all PMEs assigned to this port are of subtype '-R'). The value of the 'office' indicates that the port is designated as '-O' subtype (all PMEs assigned to this port are of subtype '-O'). The value of 'unknown' indicates that the port has no assigned PMEs yet or that the assigned PMEs are not of the same side (subTypePMEMismatch). This object partially maps to the Clause 30 attribute aPhyEnd.
efmCuPortStatusEntry	1.3.6.1.2.1.167.1.1.3.1		not-accessible	An entry in the EFMCu Port Status table. Each entry represents an EFMCu port indexed by the ifIndex. Note that an EFMCu PCS port runs on top of a single or multiple PME port(s), which are also indexed by ifIndex.
efmCuPortStatusTable	1.3.6.1.2.1.167.1.1.3		not-accessible	This table provides overall status information of EFMCu 2BASE-TL/10PASS-TS ports, complementing the generic status information from the ifTable of IF-MIB and ifMauTable of MAU-MIB. Additional status information about connected PMEs is available from the efmCuPmeStatusTable. This table contains live data from the equipment. As such, it is NOT persistent.
U32 efmCuTargetDataRate	1.3.6.1.2.1.167.1.1.1.1.4	Unsigned32	read-write	Desired EFMCu port 'net' (as seen across MII) Data Rate in Kbps, to be achieved during initialization, under spectral restrictions placed on each PME via efmCuAdminProfile or efmCuPmeAdminProfile, with the desired SNR margin specified by efmCuTargetSnrMgn. In case of PAF, this object represents a sum of individual PME data rates, modified to compensate for fragmentation and 64/65-octet encapsulation overhead (e.g., target data rate of 10 Mbps SHALL allow lossless transmission of a full-duplex 10 Mbps Ethernet frame stream with minimal inter-frame gap). The value is limited above by 100 Mbps as this is the max burst rate across MII for EFMCu ports. The value between 1 and 100000 indicates that the total data rate (ifSpeed) of the EFMCu port after initialization SHALL be equal to the target data rate or less, if the target data rate cannot be achieved under spectral restrictions specified by efmCuAdminProfile/efmCuPmeAdminProfile and with the desired SNR margin. In case the copper environment allows a higher total data rate to be achieved than that specified by the target, the excess capability SHALL be either converted to additional SNR margin or reclaimed by minimizing transmit power as controlled by efmCuAdaptiveSpectra. The value of 999999 means that the target data rate is not fixed and SHALL be set to the maximum attainable rate during initialization (Best Effort), under specified spectral restrictions and with the desired SNR margin. This object is read-write for the -O subtype EFMCu ports (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. Changing of the Target Data Rate MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing. Note that the current Data Rate of the EFMCu port is represented by the ifSpeed object of IF-MIB. This object MUST be maintained in a persistent manner.
U32 efmCuTargetSnrMgn	1.3.6.1.2.1.167.1.1.1.1.5	Unsigned32	read-write	Desired EFMCu port SNR margin to be achieved on all PMEs assigned to the port, during initialization. (The SNR margin is the difference between the desired SNR and the actual SNR). Note that 802.3ah recommends using a default target SNR margin of 5 dB for 2BASE-TL ports and 6 dB for 10PASS-TS ports in order to achieve a mean Bit Error Rate (BER) of 10^-7 at the PMA service interface. This object is read-write for the -O subtype EFMCu ports (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. Changing of the target SNR margin MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing. Note that the current SNR margin of the PMEs comprising the EFMCu port is represented by efmCuPmeSnrMgn. This object MUST be maintained in a persistent manner.
U32 efmCuThreshLowRate	1.3.6.1.2.1.167.1.1.1.1.7	Unsigned32	read-write	This object configures the EFMCu port low-rate crossing alarm threshold. When the current value of ifSpeed for this port reaches/drops below or exceeds this threshold, an efmCuLowRateCrossing notification MAY be generated if enabled by efmCuLowRateCrossingEnable. This object is read-write for the -O subtype EFMCu ports (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. This object MUST be maintained in a persistent manner.

RFC description

Manages Ethernet in First Mile Copper (EFMCu) interfaces per IEEE 802.3ah standards.

Start monitoring DSLAM/EFM access multiplexer or CPE (802.3ah EFM Copper, vendor-neutral IETF standard) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download EFM-CU-MIB