draft-ietf-hubmib-efm-cu-mib-02.txt   draft-ietf-hubmib-efm-cu-mib-03.txt 
Network Working Group E. Beili Network Working Group E. Beili
Internet-Draft Actelis Networks Internet-Draft Actelis Networks
Expires: January 30, 2005 Aug 2004 Expires: October 3, 2005 April 4, 2005
Ethernet in the First Mile Copper (EFMCu) Interfaces MIB Ethernet in the First Mile Copper (EFMCu) Interfaces MIB
draft-ietf-hubmib-efm-cu-mib-02.txt draft-ietf-hubmib-efm-cu-mib-03.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions This document is an Internet-Draft and is subject to all provisions
of section 3 of RFC 3667. By submitting this Internet-Draft, each of section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of author represents that any applicable patent or other IPR claims of
which he or she is aware have been or will be disclosed, and any of which he or she is aware have been or will be disclosed, and any of
which he or she become aware will be disclosed, in accordance with which he or she become aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 January 30, 2005. This Internet-Draft will expire on October 3, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). Copyright (C) The Internet Society (2005).
Abstract Abstract
This document defines a portion of the Management Information Base This document defines a Management Information Base (MIB) module for
(MIB) for use with network management protocols in TCP/IP based use with network management protocols in TCP/IP based internets.
internets. This document proposes an extension to the Ethernet-like This document proposes an extension to the Ethernet-like Interfaces
Interfaces MIB and MAU MIB with a set of objects for managing an MIB and MAU MIB modules with a set of objects for managing an
Ethernet in the First Mile Copper (EFMCu) interfaces 10PASS-TS and Ethernet in the First Mile Copper (EFMCu) interfaces 10PASS-TS and
2BASE-TL, defined in IEEE Std 802.3ah-2004. 2BASE-TL, defined in IEEE Std 802.3ah-2004.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Relation to other MIBs . . . . . . . . . . . . . . . . . . . . 4 3. Relation to other MIB modules . . . . . . . . . . . . . . . . 4
3.1 Relation to Interfaces Group MIB . . . . . . . . . . . . . 4 3.1 Relation to Interfaces Group MIB module . . . . . . . . . 4
3.1.1 Layering Model . . . . . . . . . . . . . . . . . . . . 4 3.1.1 Layering Model . . . . . . . . . . . . . . . . . . . . 4
3.1.2 PME Aggregation Function (PAF) . . . . . . . . . . . . 6 3.1.2 PME Aggregation Function (PAF) . . . . . . . . . . . . 6
3.1.3 Discovery Operation . . . . . . . . . . . . . . . . . 6 3.1.3 Discovery Operation . . . . . . . . . . . . . . . . . 6
3.1.4 EFMCu ports initialization . . . . . . . . . . . . . . 8 3.1.4 EFMCu ports initialization . . . . . . . . . . . . . . 8
3.1.5 Usage of ifTable . . . . . . . . . . . . . . . . . . . 8 3.1.5 Usage of ifTable . . . . . . . . . . . . . . . . . . . 8
3.2 Relation to SHDSL MIB . . . . . . . . . . . . . . . . . . 9 3.2 Relation to SHDSL MIB module . . . . . . . . . . . . . . . 9
3.3 Relation to VDSL MIB . . . . . . . . . . . . . . . . . . . 10 3.3 Relation to VDSL MIB module . . . . . . . . . . . . . . . 10
3.4 Relation to Ethernet-Like and MAU MIBs . . . . . . . . . . 10 3.4 Relation to Ethernet-Like and MAU MIB modules . . . . . . 10
4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 11 4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 11
4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2 Configuration Profiles . . . . . . . . . . . . . . . . . . 11 4.2 PME Profiles . . . . . . . . . . . . . . . . . . . . . . . 11
4.3 Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 12 4.3 Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 12
5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 13 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 13
6. Security Considerations . . . . . . . . . . . . . . . . . . . 65 6. Security Considerations . . . . . . . . . . . . . . . . . . . 67
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 66 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 69
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 66 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 69
8.1 Normative References . . . . . . . . . . . . . . . . . . . . 66 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69
8.2 Informative References . . . . . . . . . . . . . . . . . . . 67 9.1 Normative References . . . . . . . . . . . . . . . . . . . . 69
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 68 9.2 Informative References . . . . . . . . . . . . . . . . . . . 70
Intellectual Property and Copyright Statements . . . . . . . . 69 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 71
Intellectual Property and Copyright Statements . . . . . . . . 72
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) 802.3ah project a.k.a. Electrical and Electronics Engineers (IEEE) Standard 802.3ah-2004
Ethernet in the First Mile (EFM) [802.3ah]. In particular 2BASE-TL [802.3ah], a.k.a. Ethernet in the First Mile (EFM). In particular
and 10PASS-TS physical interfaces (PHYs), defined over voice-grade 2BASE-TL and 10PASS-TS physical interfaces (PHYs), defined over
copper pairs, have been specified for the long and short reach voice-grade copper pairs, have been specified for the long and short
respectively. These interfaces, collectively called EFMCu, are based reach respectively. These interfaces, collectively called EFMCu, are
on ITU-T G.SHDSL and VDSL specifications and support variable rates based on ITU-T G.SHDSL [G.991.2] and VDSL [G.993.1] specifications
and optional Physical Medium Entity (PME) aggregation (a.k.a. and support variable rates and optional Physical Medium Entity (PME)
multi-pair bonding). aggregation (a.k.a. multi-pair bonding).
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 2700 m long
single copper pair with a mean Bit Error Rate (BER) of 10^-7 (using single copper pair with a mean Bit Error Rate (BER) of 10^-7 (using
5dB target noise margin). 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 750 m long
single copper pair with a mean BER of 10^-7 (using 6dB target noise single copper pair with a mean BER of 10^-7 (using 6dB target noise
margin). margin).
This memo defines a portion of the Management Information Base (MIB) This memo defines a Management Information Base (MIB) module for use
for use with network management protocols in the Internet community with network management protocols in the Internet community to manage
to manage EFMCu interfaces. EFMCu interfaces.
Note that managed objects for Operation, Administration and Note that managed objects for Operation, Administration and
Management (OAM) and Ethernet over Passive Optical Networks (EPON) Management (OAM) and Ethernet over Passive Optical Networks (EPON)
clauses of IEEE 802.3ah are defined in EFM-COMMON-MIB clauses of IEEE 802.3ah are defined in EFM-COMMON-MIB
[I-D.ietf-hubmib-efm-mib] and EFM-EPON-MIB [I-D.ietf-hubmib-efm-mib] and EFM-EPON-MIB
[I-D.ietf-hubmib-efm-epon-mib] 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
skipping to change at page 4, line 6 skipping to change at page 4, line 6
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. A detailed introduction to the current SNMP Management [RFC2580]. A detailed introduction to the current SNMP Management
Framework can be found in RFC 2570 [RFC2570]. Framework can be found in RFC 2570 [RFC2570].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. Relation to other MIBs 3. Relation to other MIB modules
This section outlines the relationship of this MIB with other MIB This section outlines the relationship of this MIB with other MIB
modules described in the relevant RFCs. Specifically, Interfaces modules described in the relevant RFCs. Specifically, Interfaces
Group MIB (IF-MIB), Ethernet-Like (EtherLike-MIB), MAU (MAU-MIB), Group MIB (IF-MIB), Ethernet-Like (EtherLike-MIB), MAU (MAU-MIB),
SHDSL (HDSL2-SHDSL-LINE-MIB) and VDSL (VDSL-LINE-EXT-MCM-MIB) are SHDSL (HDSL2-SHDSL-LINE-MIB) and VDSL (VDSL-LINE-EXT-MCM-MIB) are
discussed. discussed.
3.1 Relation to Interfaces Group MIB 3.1 Relation to Interfaces Group MIB module
2BASE-TL and 10PASS-TS PHY's specified in this MIB are stacked 2BASE-TL and 10PASS-TS PHY's specified in this MIB module are stacked
Ethernet interfaces and as such are managed using generic interface Ethernet interfaces and as such are managed using generic interface
management objects defined in the IF-MIB [RFC2863]. The stack management objects defined in the IF-MIB [RFC2863]. The stack
management is done via the ifStackTable, as defined in the IF-MIB management is done via the ifStackTable, as defined in the IF-MIB
[RFC2863] and ifInvStackTable, as defined in the [RFC2863] and ifInvStackTable, as defined in the
IF-INVERTED-STACK-MIB [RFC2864]. IF-INVERTED-STACK-MIB [RFC2864].
3.1.1 Layering Model 3.1.1 Layering Model
An EFMCu interface can aggregate up to 32 Physical Medium Entity An EFMCu interface can aggregate up to 32 Physical Medium Entity
(PME) sub-layer devices (modems), using so called PME Aggregation (PME) sub-layer devices (modems), using so called PME Aggregation
skipping to change at page 4, line 40 skipping to change at page 4, line 40
(PCS) ports, connected to a MAC via Medium Independent Interface (PCS) ports, connected to a MAC via Medium Independent Interface
(MII) at the upper layer, and cross-connected to a number of (MII) at the upper layer, and cross-connected to a number of
underlying PMEs, with a single PCS per PME relationship, see clause underlying PMEs, with a single PCS per PME relationship, see clause
61.1 of [802.3ah] for more details. 61.1 of [802.3ah] for more details.
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 port with ifType of shdsl(169) for table (ifTable) as a separate port with ifType of shdsl(169) for
2BASE-TL or vdsl(97) for 10PASS-TS. The ifType values are defined in 2BASE-TL or vdsl(97) for 10PASS-TS. The ifType values are defined in
[IANAifType-MIB]. [IANAifType-MIB].
ifSpeed for each PME shall return the actual data bitrate of the ifSpeed for each PME SHALL return the actual data bitrate of the
active PME or a configured bitrate for pre-activated modems (e.g. active PME (e.g. for 2BaseTL PMEs it is a multiple of 64Kbps). Zero
for 2BaseTL PMEs it is a multiple of 64Kbps). The ifSpeed of the PCS value SHALL be returned when PME is initializing or down.
is the sum of the current operating data rates of all modems in the
aggregation group, without the 64/65B encapsulation overhead and PAF
overhead, but acounting for the Inter-Frame Gaps (IFG).
The following configuration shall have no frame loss (the test-sets The ifSpeed of the PCS is the sum of the current operating data rates
are configured to generate 100% of back to back traffic, i.e. of all PMEs in the aggregation group, without the 64/65B
minimal IFG, at 10Mbps; the EFM interfaces are obviously aggregated) encapsulation overhead and PAF overhead, but acounting for the
): Inter-Frame Gaps (IFG).
When using the stated definition of ifSpeed for the PCS, there would
be no frame loss in the following configuration (the test-sets are
configured to generate 100% of back to back traffic, i.e. minimal
IFG, at 10 or 100Mbps, with min and max frame sizes; the EFM
interfaces are obviously aggregated):
[testset]--10BaseT--[CO]--2BaseTL--[CPE]--10BaseT--[testset] [testset]--10BaseT--[CO]--2BaseTL--[CPE]--10BaseT--[testset]
ifSpeed=10Mbps ifSpeed=10Mbps ifSpeed=10Mbps ifSpeed= 10Mbps 10Mbps 10Mbps
[testset]--100BaseT--[CO]--10PassTS--[CPE]--100BaseT--[testset] [testset]--100BaseT--[CO]--10PassTS--[CPE]--100BaseT--[testset]
ifSpeed=100Mbps ifSpeed=100Mbps ifSpeed=100Mbps ifSpeed= 100Mbps 100Mbps 100Mbps
Figure 1: Example configuration with no frame loss Figure 1: Example configuration with no frame loss
The following figure shows the layering diagram and corresponding use The following figure shows the layering diagram and corresponding use
of ifTable and ifMauTable: of ifTable and ifMauTable:
_________________________ _ _________________________ _
| LLC | | | LLC | |
+-------------------------+ | 1 ifEntry +-------------------------+ | 1 ifEntry
| MAC | | ifType: ethernetCsmacd(6) | MAC | | ifType: ethernetCsmacd(6)
skipping to change at page 5, line 48 skipping to change at page 5, line 49
The ifStackTable is indexed by the ifIndex values of the aggregated The ifStackTable is indexed by the ifIndex values of the aggregated
EFMCu port (PCS) and the PMEs connected to it. ifStackTable allows a EFMCu port (PCS) and the PMEs connected to it. ifStackTable allows a
Network Management application to determine which PMEs are connected Network Management application to determine which PMEs are connected
to a particular PCS and change connections (if supported by the to a particular PCS and change connections (if supported by the
application). The ifInvStackTable, being an inverted version of the application). The ifInvStackTable, being an inverted version of the
ifStackTable, provides an efficient means for a Network Management ifStackTable, provides an efficient means for a Network Management
application to read a subset of the ifStackTable and thereby application to read a subset of the ifStackTable and thereby
determine which PCS runs on top of a particular PME. determine which PCS runs on top of a particular PME.
A new table ifAvailableStackTable defined in this MIB, specifies for A new table ifAvailableStackTable defined in this MIB module,
each PCS a list of PMEs, which can possibly be cross-connected to specifies for each PCS a list of PMEs, which can possibly be
that PCS, determined by the cross-connect capability of the device. cross-connected to that PCS, determined by the cross-connect
This table, modeled after ifStackTable, is read only, reflecting capability of the device. This table, modeled after ifStackTable, is
current cross-connect capability, which can be dynamic in some read only, reflecting current cross-connect capability, which can be
implementations (e.g. if PMEs are located on a pluggable module and dynamic in some implementations (e.g. if PMEs are located on a
the module is pulled out). Note that PME availability per PCS, pluggable module and the module is pulled out). Note that PME
described by ifAvailableStackTable, can be constrained by other availability per PCS, described by ifAvailableStackTable, can be
parameters, for example by aggregation capacity of a PCS or by the constrained by other parameters, for example by aggregation capacity
PME in question being already connected to another PCS. So, in order of a PCS or by the PME in question being already connected to another
to ensure that a particular PME can be connected to the PCS, all PCS. So, in order to ensure that a particular PME can be connected
respective parameters (e.g. ifAvailableStackTable, ifStackTable and to the PCS, all respective parameters (e.g. ifAvailableStackTable,
efmCuPAFCapacity) SHALL be inspected. ifStackTable and efmCuPAFCapacity) SHALL be inspected.
*EdNote: Add ifInvAvailableStackTable describing which PCS ports can
be connected to a particular PME. Add it to the
ifStackCapabilityGroup conformance statement. *
3.1.2 PME Aggregation Function (PAF) 3.1.2 PME Aggregation Function (PAF)
The PME Aggregation Function (PAF) is OPTIONAL. Note however that The PME Aggregation Function (PAF) allows a number of PMEs to be
the agent is REQUIRED to report on the PAF capability for all EFMCu aggregated onto a PCS port, by fragmenting the Ethernet frames,
ports (2BASE-TL and 10PASS-TS). transmitting the fragments over multiple PMEs and assembling the
original frames at the remote port. PAF is OPTIONAL, meaning that a
device with a single PME MAY perform fragmentation and re-assembly if
this function is supported by the device. Note however that the
agent is REQUIRED to report on the PAF capability for all EFMCu ports
(2BASE-TL and 10PASS-TS).
*EdNote: Add more info.* This MIB module allows a Network Management application to query PAF
capability and enable/disable it if supported. Note that enabling
PAF effectively turns on fragmentation and re-assembly, even on a
single-PME port.
3.1.3 Discovery Operation 3.1.3 Discovery Operation
The EFMCu ports may optionally support discovery operation, whereby The EFMCu ports may optionally support discovery operation, whereby
PMEs, during initialization, exchange information about their PMEs, during initialization, exchange information about their
respective aggregation groups (PCS). This information can then be respective aggregation groups (PCS). This information can then be
used to detect copper missconnections or for an automatic assignment used to detect copper missconnections or for an automatic assignment
of the local PMEs into aggregation groups instead of fixed of the local PMEs into aggregation groups instead of fixed
pre-configuration. pre-configuration.
This MIB allows a Network Management application to control EFM This MIB module allows a Network Management application to control
Discovery mechanism and query its results. Note that the Discovery EFM Discovery mechanism and query its results. Note that the
mechanism can work only if PAF is supported and enabled. Discovery mechanism can work only if PAF is supported and enabled.
Two tables are used by Discovery mechanism: ifStackTable and Two tables are used by Discovery mechanism: ifStackTable and
ifAvailableStackTable defined. The following pseudo-code defines an ifAvailableStackTable defined. The following pseudo-code defines an
example of Discovery and automatic PME assignment for a generic PAF example of Discovery and automatic PME assignment for a generic PAF
enabled multi-PCS EFMCu device, located at Central Office (CO) [Note enabled multi-PCS EFMCu device, located at Central Office (CO), using
that automatic PME assignment is only shown here for the purposes of objects defined in this MIB module. [Note that automatic PME
the example. Fixed PME pre-assignment or manual assignment may be assignment is only shown here for the purposes of the example. Fixed
chosen by a particular implementation]: PME pre-assignment, manual assignment or auto-assignment by an
alternative internal algorithm may be chosen by a particular
implementation]:
FOREACH pcs[i] IN co_device FOREACH pcs[i] IN co_device
{ // Discover only on PAF enabled ports with room for more PMEs { // Discover only on PAF enabled ports 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 Byte per PCS { dc = pcs[i].DiscoveryCode = MAC[i]; // unique 6 Byte per PCS
// go over all currently disconnected PMEs, which can // go over all currently disconnected PMEs, which can
// pottentially be connected to PCS[i] // pottentially be connected to PCS[i]
FOREACH pme[j] IN ifAvailableStackTable[pcs[i]] AND FOREACH pme[j] IN ifAvailableStackTable[pcs[i]] AND
NOT IN ifInvStackTable[pme[j]] // unassigned NOT IN ifInvStackTable[pme[j]] // unassigned
{ pme[j].RemoteDiscoveryCode = dc; // Set if Clear { pme[j].RemoteDiscoveryCode = dc; // Set if Clear
skipping to change at page 8, line 25 skipping to change at page 8, line 25
cooperatively to achieve required data rate on a particular copper cooperatively to achieve required data rate on a particular copper
pair. Sometimes, when the copper line is too long or the noise pair. Sometimes, when the copper line is too long or the noise
environment on the line is too high, that 'training' process may fail environment on the line is too high, that 'training' process may fail
to achieve a specific target rate with required characteristics. to achieve a specific target rate with required characteristics.
The ifAdminStatus object from the IF-MIB, controls the desired state The ifAdminStatus object from the IF-MIB, controls the desired state
of a PCS and a PME port. Setting this object to 'up' instructs a of a PCS and a PME port. Setting this object to 'up' instructs a
particular PCS or PME to start initialization process, which may take particular PCS or PME to start initialization process, which may take
tens of seconds for EFMCu ports, especially if PAF is involved. The tens of seconds for EFMCu ports, especially if PAF is involved. The
ifOperStatus object shows the operational state of an interface ifOperStatus object shows the operational state of an interface
(extended by efmCuPmeOperStatus defined in this MIB for PME (extended by efmCuPmeOperStatus defined in this 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
connected to the PCS are 'down' the PCS SHALL be considered connected to the PCS are 'down' the PCS SHALL be considered
operationally 'lowerLayerDown'. The PCS SHALL be considered operationally 'lowerLayerDown'. The PCS SHALL be considered
operationally 'notPresent' if it is not connected to any PME. The operationally 'notPresent' if it is not connected to any PME. The
PCS/PME interface SHALL remain operationally 'down' during PCS/PME interface SHALL remain operationally 'down' during
initialization. initialization.
The efmCuPmeOperStatus defined in this MIB expands PME's ifOperStatus The efmCuPmeOperStatus defined in this MIB module expands PME's
value of 'down' to 'downReady', 'downNotReady' and 'init' values, ifOperStatus value of 'down' to 'downReady', 'downNotReady' and
indicating various EFMCu PME specific states. 'init' values, indicating various EFMCu PME specific states.
3.1.5 Usage of ifTable 3.1.5 Usage of ifTable
Both PME and PCS interfaces of the EFMCu PHY are managed using Both PME and PCS interfaces of the EFMCu PHY are managed using
interface specific management objects defined in this MIB and generic interface specific management objects defined in this MIB module and
interface objects from the ifTable of IF-MIB, with all management generic interface objects from the ifTable of IF-MIB, with all
table entries referenced by the interface index ifIndex. management table entries referenced by the interface index ifIndex.
The following table summarizes EFMCu specific interpretations for The following table summarizes EFMCu specific interpretations for
some of the ifTable objects specified by the mandatory some of the ifTable objects specified by the mandatory
ifGeneralInformationGroup: ifGeneralInformationGroup:
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| IF-MIB object | EFMCu interpretation | | IF-MIB object | EFMCu interpretation |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| ifIndex | Interface index. Note that each | | ifIndex | Interface index. Note that each |
| | PME and each PCS in the EFMCu | | | PME and each PCS in the EFMCu |
| | PHY MUST have a unique index, | | | PHY MUST have a unique index, |
| | as there some PCS and PME | | | as there some PCS and PME |
| | specific attributes accessible | | | specific attributes accessible |
| | only on the PCS or PME level. | | | only on the PCS or PME level. |
| ifType | ethernetCsmacd(6) for PCS, | | ifType | ethernetCsmacd(6) for PCS, |
| | shdsl(169) for 2BASE-TL PME, | | | shdsl(169) for 2BASE-TL PME, |
| | vdsl(97) for 10PASS-TS PME | | | vdsl(97) for 10PASS-TS PME |
| ifSpeed | Actual 'net' data rate as seen | | ifSpeed | Operating data rate for the |
| | across MII | | | PME. For the PCS it is the sum |
| | of the current operating data |
| | rates of all PMEs in the |
| | aggregation group, without the |
| | 64/65B encapsulation overhead |
| | and PAF overhead, but acounting |
| | for the Inter-Frame Gaps (IFG) |
| ifAdminStatus | Setting this object to 'up' | | ifAdminStatus | Setting this object to 'up' |
| | instructs a particular PCS | | | instructs a particular PCS |
| | (with all PMEs connected to it) | | | (with all PMEs connected to it) |
| | or PME to start initialization | | | or PME to start initialization |
| | process | | | process |
| ifOperStatus | efmCuPmeOperStatus supplements | | ifOperStatus | efmCuPmeOperStatus supplements |
| | the 'down' value of | | | the 'down' value of |
| | ifOperStatus for PMEs. | | | ifOperStatus for PMEs. |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
Table 1 Table 1
3.2 Relation to SHDSL MIB 3.2 Relation to SHDSL MIB module
G.SHDSL.bis modems, similar to PME(s) comprising a 2BASE-TL port, are G.SHDSL.bis modems, similar to PME(s) comprising a 2BASE-TL port, are
described in HDSL2-SHDSL-LINE-MIB [I-D.ietf-adslmib-gshdslbis]. Note described in HDSL2-SHDSL-LINE-MIB [I-D.ietf-adslmib-gshdslbis]. Note
that not all attributes of G.SHDSL modems reflected in that not all attributes of G.SHDSL modems reflected in
HDSL2-SHDSL-LINE-MIB have adequate management objects (Clause 30 HDSL2-SHDSL-LINE-MIB have adequate management objects (Clause 30
attributes and Clause 45 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 and name consistency (e.g. prefixing the 2BASE-TL PME related
objects with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided objects with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided
not to reference HDSL2-SHDSL-LINE-MIB objects, but define all the not to reference HDSL2-SHDSL-LINE-MIB objects, but define all the
relevant objects in this MIB. relevant objects in this MIB module.
However, if some functionality, not available in this MIB, is However, if some functionality, not available in this MIB module, is
required and supported by the PME, e.g. performance monitoring, required and supported by the PME, e.g. performance monitoring,
relevant HDSL2-SHDSL-LINE-MIB groups MAY be included and aplied for relevant HDSL2-SHDSL-LINE-MIB groups MAY be included and aplied for
PMEs of 2BASE-TL subtype. PMEs of 2BASE-TL subtype.
3.3 Relation to VDSL MIB 3.3 Relation to VDSL MIB module
VDSL (DMT) modems, similar to the PME(s) comprising a 10PASS-TS port, VDSL (DMT) modems, similar to the PME(s) comprising a 10PASS-TS port,
are described in VDSL-LINE-EXT-MCM-MIB are described in VDSL-LINE-EXT-MCM-MIB
[I-D.ietf-adslmib-vdsl-ext-mcm]. Note that not all attributes of [I-D.ietf-adslmib-vdsl-ext-mcm]. Note that not all attributes of
VDSL modems reflected in VDSL-LINE-EXT-MCM-MIB have adequate VDSL modems reflected in VDSL-LINE-EXT-MCM-MIB have adequate
management objects (Clause 30 attributes and Clause 45 registers) in management objects (Clause 30 attributes and Clause 45 registers) in
the EFM standard. the EFM standard.
Because of these differences and for the purposes of simplicity, Because of these differences and for the purposes of simplicity,
unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs
and name consistency, it was decided not to reference and name consistency, it was decided not to reference
VDSL-LINE-EXT-MCM-MIB objects, but define all the relevant objects in VDSL-LINE-EXT-MCM-MIB objects, but define all the relevant objects in
this MIB. this MIB module.
However, if some functionality, not available in this MIB, is However, if some functionality, not available in this MIB module, is
required and supported by the PME, relevant VDSL-LINE-EXT-MCM-MIB required and supported by the PME, relevant VDSL-LINE-EXT-MCM-MIB
groups MAY be included and applied for PMEs of 10PASS-TS subtype. groups MAY be included and applied for PMEs of 10PASS-TS subtype.
3.4 Relation to Ethernet-Like and MAU MIBs 3.4 Relation to Ethernet-Like and MAU MIB modules
The implementation of EtherLike-MIB [RFC3635] and MAU-MIB The implementation of EtherLike-MIB [RFC3635] and MAU-MIB
[I-D.ietf-hubmib-rfc3636bis] is REQUIRED for the EFMCu interfaces. [I-D.ietf-hubmib-rfc3636bis] is REQUIRED for the EFMCu interfaces.
Two new values of ifMauType (OBJECT-IDENTITIES of dot3MauType) and Two new values of ifMauType (OBJECT-IDENTITIES of dot3MauType) and
corresponding bit definitions of ifMauTypeListBits corresponding bit definitions of ifMauTypeListBits
(IANAifMauTypeListBits) have been defined in the IANA-MAU-TC-MIB (IANAifMauTypeListBits) have been defined in the IANA-MAU-TC-MIB
[I-D.ietf-hubmib-rfc3636bis] for the EFMCu MAUs: [I-D.ietf-hubmib-rfc3636bis] for the EFMCu MAUs:
o dot3MauType2BaseTL and b2BaseTL - for 2BASE-TL MAU o dot3MauType2BaseTL and b2BaseTL - for 2BASE-TL MAU
o dot3MauType10PassTS and b10PassTS - for 10PASS-TS MAU o dot3MauType10PassTS and b10PassTS - for 10PASS-TS MAU
As an EtherLike interface every EFMCu port (an ifEntry representing a As an EtherLike interface every EFMCu port (an ifEntry representing a
consolidation of LLC, MAC and PCS (sub)layers) SHALL return an ifType consolidation of LLC, MAC and PCS (sub)layers) SHALL return an ifType
of ethernetCsmacd(6). While most of the MAU characteristics is not of ethernetCsmacd(6). While most of the MAU characteristics are not
applicable to the EFMCu ports (no auto-negotiation, media available, applicable to the EFMCu ports (no auto-negotiation, media available,
false carriers or jabber), they SHALL return an appropriate ifMauType false carriers or jabber), they SHALL return an appropriate ifMauType
(dot3MauType2BaseTL or dot3mauType10PassTS) in order to direct the (dot3MauType2BaseTL or dot3mauType10PassTS) in order to direct the
management software to look in the EFM-CU-MIB for the desired management software to look in the EFM-CU-MIB for the desired
information. For example the information on the particular EFMCu information. For example the information on the particular EFMCu
flavor that an EFMCu port is running is available from flavor that an EFMCu port is running is available from
efmCuOperSubType, defined in this MIB module. efmCuOperSubType, defined in this MIB module.
Since EFMCu PMEs are not EtherLike interfaces, they cannot be Since EFMCu PMEs are not EtherLike interfaces, they cannot be
instantiated as MAU interface objects. instantiated as MAU interface objects.
4. MIB Structure 4. MIB Structure
4.1 Overview 4.1 Overview
The main management objects defined in this MIB are split into 2 The main management objects defined in this MIB module are split into
groups: 2 groups:
o efmCuPort - containing objects for configuration, capabilities, o efmCuPort - containing objects for configuration, capabilities,
status and notifications, common to all EFMCu PHYs. status and notifications, common to all EFMCu PHYs.
o efmCuPme - containing objects for configuration, capabilities, o efmCuPme - containing objects for configuration, capabilities,
status and notifications of EFMCu PMEs. status and notifications of EFMCu PMEs.
In addition the ifAvailableStackTable is defined at the same level. In addition the ifAvailableStackTable is defined at the same level.
The efmCuPme group in turn contains efmCuPme2B and efmCuPme10P The efmCuPme group in turn contains efmCuPme2B and efmCuPme10P
groups, which define configuration profiles specific to 2BASE-TL and groups, which define PME Profiles specific to 2BASE-TL and 10PASS-TS
10PASS-TS PMEs respectively as well as PME specific status PMEs respectively, as well as PME specific status information.
information.
4.2 Configuration Profiles 4.2 PME Profiles
Since a managed node can have a large number of EFMCu PHYs, Since a managed node can have a large number of EFMCu PHYs,
provisioning every parameter on every EFMCu PHY may become provisioning every parameter on every EFMCu PHY may become
burdensome. Moreover, most PMEs are provisioned identically with the burdensome. Moreover, most PMEs are provisioned identically with the
same set of parameters. To simplify the provisioning process, this same set of parameters. To simplify the provisioning process, this
MIB makes use of configuration profiles, similar to MIB module makes use of configuration profiles, similar to
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. A profile is a set
of parameters that can be shared by multiple PME ports using the same of parameters, used either for configuration or representation of a
configuration. PME. The same profile can be shared by multiple PME ports, using the
same configuration.
The configuration profiles are defined in efmCuPme2BConfProfileTable The PME profiles are defined in efmCuPme2BProfileTable and
and efmCu10PConfProfileTable for 2BASE-TL and 10PASS-TS PMEs efmCu10PProfileTable for 2BASE-TL and 10PASS-TS PMEs respectively.
respectively. There are 12 predefined standard profiles for 2BASE-TL There are 12 predefined standard profiles for 2BASE-TL and 22
and 22 standard profiles for 10PASS-TS, defined in 802.3ah and standard profiles for 10PASS-TS, defined in 802.3ah and dedicated for
dedicated for rapid provisioning of EFMCu PHYs in most scenarios. An rapid provisioning of EFMCu PHYs in most scenarios. An ability to
ability to define new configuration profiles is also provided to define new configuration profiles is also provided to allow for EFMCu
allow for EFMCu deployment tailored to specific copper environment deployment tailored to specific copper environment and spectral
and spectral regulations. regulations.
A specific configuration profile is assigned to a specific PME via A specific configuration or administrative profile is assigned to a
efmCuPmeAdminProfile object. Alternatively, by assigning a non-empty specific PME via efmCuPmeAdminProfile object. If
profile to a PCS port via efmCuAdminProfile, all PMEs connected to efmCuPmeAdminProfile is zero, then efmCuAdminProfile object of the
the PCS port are made to share that profile, which comes in handy PCS port, connected to the PME, determines the configuration profile
during configuration of aggregated ports. (or a list of possible profiles) for that PME. This mechanism allows
to specify a common profile(s) for all PMEs connected to the PCS
port, with an ability to change individual PME profiles by setting
efmCuPmeAdminProfile objects, which overwrites profile set by
efmCuAdminProfile.
A current operating PME profile is pointed to by efmCuPmeOperProfile
object. Note that this profile entry, can be created automatically,
to reflect achieved parameters in adaptive (not fixed)
initialization.
4.3 Mapping of IEEE 802.3ah Managed Objects 4.3 Mapping of IEEE 802.3ah Managed Objects
This section contains the mapping between managed objects This section contains the mapping between managed objects
(attributes) defined in [802.3ah] Clause 30, and managed objects (attributes) defined in [802.3ah] Clause 30, and managed objects
defined in this document and in associated MIB modules, i.e., the defined in this document and in associated MIB modules, i.e., the
IF-MIB [RFC2863]. IF-MIB [RFC2863].
Note that majority of the objects defined in this MIB do not have Note that majority of the objects defined in this MIB module do not
direct counterparts in Clause 30 and instead refer to Clause 45 have direct counterparts in Clause 30 and instead refer to Clause 45
registers. registers.
*EdNote: It would be a good idea to update Clause 30 of 802.3ah after *EdNote: It would be a good idea to update Clause 30 of 802.3ah after
this MIB is approved. I guess this should be done via a maintanence this MIB module is approved. I guess this should be done via a
request. * maintanence request. *
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| IEEE 802.3 Managed Object | Corresponding SNMP Object | | IEEE 802.3 Managed Object | Corresponding SNMP Object |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| oPAF - Basic Package | | | oPAF - Basic Package | |
| (Mandatory) | | | (Mandatory) | |
| aPAFID | ifIndex (IF-MIB) | | aPAFID | ifIndex (IF-MIB) |
| aPhyEnd | efmCuPhySide | | aPhyEnd | efmCuPhySide |
| aPHYCurrentStatus | efmCuStatus | | aPHYCurrentStatus | efmCuStatus |
| aPAFSupported | efmCuPAFSupported | | aPAFSupported | efmCuPAFSupported |
| oPAF - PME Aggregation Package | | | oPAF - PME Aggregation Package | |
skipping to change at page 13, line 24 skipping to change at page 14, line 10
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- [RFC3411] FROM SNMP-FRAMEWORK-MIB -- [RFC3411]
ifIndex, ifSpeed, InterfaceIndex ifIndex, ifSpeed, InterfaceIndex
FROM IF-MIB -- [RFC2863] FROM IF-MIB -- [RFC2863]
; ;
efmCuMIB MODULE-IDENTITY efmCuMIB MODULE-IDENTITY
LAST-UPDATED "200410240000Z" -- October 24, 2004 LAST-UPDATED "200504040000Z" -- April 04, 2005
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://www.ietf.org/html.charters/hubmib-charter.html http://www.ietf.org/html.charters/hubmib-charter.html
Mailing Lists: Mailing Lists:
General Discussion: hubmib@ietf.org General Discussion: hubmib@ietf.org
To Subscribe: hubmib-request@ietf.org To Subscribe: hubmib-request@ietf.org
In Body: subscribe your_email_address In Body: subscribe your_email_address
skipping to change at page 14, line 10 skipping to change at page 14, line 45
E-mail: edward.beili@actelis.com" E-mail: edward.beili@actelis.com"
DESCRIPTION DESCRIPTION
"The objects in this MIB module are used to manage "The objects in this MIB module are used to manage
the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces
2BASE-TL and 10PASS-TS, defined in IEEE Draft P802.3ah/D3.3. 2BASE-TL and 10PASS-TS, defined in IEEE Draft P802.3ah/D3.3.
The following reference is used throughout this MIB module: The following reference is used throughout this MIB module:
[802.3ah] refers to: [802.3ah] refers to:
IEEE Draft P802.3ah/D3.3: 'Draft amendment to - IEEE Std 802.3ah-2004: 'IEEE Standard for Information
Information technology - Telecommunications and technology - Telecommunications and information exchange
information exchange between systems - Local and between systems - Local and metropolitan area networks -
metropolitan area networks - Specific requirements - Specific requirements -
Part 3: Carrier sense multiple access with collision Part 3: Carrier Sense Multiple Access with Collision
detection (CSMA/CD) access method and physical layer Detection (CSMA/CD) Access Method and Physical Layer
specifications - Media Access Control Parameters, Physical Specifications -
Layers and Management Parameters for subscriber access Amendment: Media Access Control Parameters, Physical
networks', 19 April 2003. Layers and Management Parameters for Subscriber Access
Networks', 07 September 2004.
Of particular interest are Clause 61, 'Physical Coding Of particular interest are Clause 61, 'Physical Coding
Sublayer (PCS) and common specifications, type 10PASS-TS and Sublayer (PCS) and common specifications, type 10PASS-TS and
type 2BASE-TL', Clause 30, 'Management', Clause 45, type 2BASE-TL', Clause 30, 'Management', Clause 45,
'Management Data Input/Output (MDIO) Interface', Annex 62A, 'Management Data Input/Output (MDIO) Interface', Annex 62A,
'PMD profiles for 10PASS-TS' and Annex 63A, 'PMD profiles for 'PMD profiles for 10PASS-TS' and Annex 63A, 'PMD profiles for
2BASE-TL'. 2BASE-TL'.
Naming Conventions: Naming Conventions:
Atn - Attenuation Atn - Attenuation
skipping to change at page 14, line 50 skipping to change at page 15, line 38
SNR - Signal to Noise Ratio SNR - Signal to Noise Ratio
TCPAM - Trellis Coded Pulse Amplitude Modulation TCPAM - Trellis Coded Pulse Amplitude Modulation
Copyright (C) The Internet Society (2004). This version Copyright (C) The Internet Society (2004). This version
of this MIB module is part of RFC XXXX; see the RFC of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices." itself for full legal notices."
-- EdNote: Replace XXXX with the actual RFC number & -- EdNote: Replace XXXX with the actual RFC number &
-- remove this note -- remove this note
REVISION "200410240000Z" -- October 24, 2004 REVISION "200504040000Z" -- April 04, 2005
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
::= { mib-2 YYY }
::= { mib-2 160 }
-- EdNote: Replace YYY with a real OID once it is -- EdNote: Replace YYY with a real OID once it is
-- allocated & remove this note. -- allocated & remove this note.
-- Sections of the module -- Sections of the module
efmCuObjects OBJECT IDENTIFIER ::= { efmCuMIB 1 } efmCuObjects OBJECT IDENTIFIER ::= { efmCuMIB 1 }
efmCuConformance OBJECT IDENTIFIER ::= { efmCuMIB 2 } efmCuConformance OBJECT IDENTIFIER ::= { efmCuMIB 2 }
-- Groups in the module -- Groups in the module
efmCuPort OBJECT IDENTIFIER ::= { efmCuObjects 1 } efmCuPort OBJECT IDENTIFIER ::= { efmCuObjects 1 }
efmCuPme OBJECT IDENTIFIER ::= { efmCuObjects 2 } efmCuPme OBJECT IDENTIFIER ::= { efmCuObjects 2 }
-- Textual Conventions -- Textual Conventions
ProfileIndex ::= TEXTUAL-CONVENTION ProfileIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
skipping to change at page 16, line 8 skipping to change at page 16, line 45
where current operational profile is unknown." where current operational profile is unknown."
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
ProfileIndexList ::= TEXTUAL-CONVENTION ProfileIndexList ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d:" DISPLAY-HINT "1d:"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a list of up to 6 ProfileIndex's. "Represents a list of up to 6 ProfileIndex's.
The ProfileIndex textual convention defines a greater than The ProfileIndex textual convention defines a greater than
zero value used to identify a PME profile in the managed EFMCu zero value used to identify a PME profile in the managed EFMCu
port. The value of this object is a concatenation of zero or port. The value of this object is a concatenation of one 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
ProfileIndex value. ProfileIndex value.
A non-empty profile list specifies a list of alternative The ProfileIndexList specifies a list of alternative
profiles any of which can be chosen for configuration of an profiles, any of which can be chosen for configuration of an
PME. A zero length string value means this list has no members PME."
(empty). Examples of the usage of empty profile list might SYNTAX OCTET STRING (SIZE(1..6))
include situations where configuration profile(s) is unknown, TruthValueOrUnknown ::= TEXTUAL-CONVENTION
or when no common profile(s) need to be referenced and STATUS current
sub-interface profile shall take precedence." DESCRIPTION
SYNTAX OCTET STRING (SIZE(0..6)) "This textual convention is an extension of the TruthValue
convention. The latter defines a boolean value with
possible values of true(1) and false(2). This
extension permits the additional value of unknown(0), which
can be returned as a result of GET operation, when an exact
true or false value of the object cannot be determined."
SYNTAX INTEGER { unknown(0), true(1), false(2) }
-- Port Notifications Group -- Port Notifications Group
efmCuPortNotifications OBJECT IDENTIFIER ::= { efmCuPort 0 } efmCuPortNotifications OBJECT IDENTIFIER ::= { efmCuPort 0 }
efmCuLowBandwidth NOTIFICATION-TYPE efmCuLowBandwidth NOTIFICATION-TYPE
OBJECTS { OBJECTS {
-- ifIndex is not needed here since we are under specific PCS -- ifIndex is not needed here since we are under specific PCS
ifSpeed, ifSpeed,
efmCuThreshLowBandwidth efmCuThreshLowBandwidth
skipping to change at page 18, line 10 skipping to change at page 19, line 5
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 ignored if the link is Up or change this object SHALL be ignored 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.
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 maps to the PAF enable bit in the 10P/2B PCS control object maps to the PAF enable bit in the 10P/2B PCS control
register." register.
This object MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"[802.3ah] 61.2.2, 45.2.3.18.3" "[802.3ah] 61.2.2, 45.2.3.18.3"
::= { efmCuPortConfEntry 1 } ::= { efmCuPortConfEntry 1 }
efmCuPAFDiscoveryCode OBJECT-TYPE efmCuPAFDiscoveryCode OBJECT-TYPE
SYNTAX PhysAddress SYNTAX PhysAddress
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).
skipping to change at page 19, line 5 skipping to change at page 19, line 50
Clause 45 register)" Clause 45 register)"
REFERENCE REFERENCE
"[802.3ah] 61.2.2.8.3, 61.2.2.8.4, 45.2.6.6.1" "[802.3ah] 61.2.2.8.3, 61.2.2.8.4, 45.2.6.6.1"
::= { efmCuPortConfEntry 2 } ::= { efmCuPortConfEntry 2 }
efmCuAdminProfile OBJECT-TYPE efmCuAdminProfile OBJECT-TYPE
SYNTAX ProfileIndexList SYNTAX ProfileIndexList
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 efmCuPme2BConfProfileTable or either efmCuPme2BProfileTable or
efmCuPme10PConfProfileTable, 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
configuration profiles. If this list consists of a single Profiles. If this list consists of a single Profile index,
Profile index, then all PMEs assigned to this EFMCu port SHALL then all PMEs assigned to this EFMCu port SHALL be configured
be configured according to the Configuration Profile according to the Profile referenced by that index, unless it
referenced by that index. The list, consisting of more than is overwritten by corresponding non-zero efmCuPmeAdminProfile,
one index, allows each PME in the port to be configured which takes precedence over efmCuAdminProfile.
according to any configuration profile specified in the list. The list, consisting of more than one index, allows each PME
An empty list means that each PME in the port is configured in the port to be configured according to any Profile
via corresponding efmCuPmeAdminProfile object. specified in the list.
By default this object has a single profile index 1,
referencing 1st entry in efmCuPme2BProfileTable/
efmCuPme2BProfileTable.
This object is writable and readable for the -O subtype This object is writable and readable for the -O subtype
(2BaseTL-O or 10PassTS-O) EFMCu ports. It is unavailable for (2BaseTL-O or 10PassTS-O) EFMCu ports. It is unavailable for
the -R subtype (2BaseTL-R or 10PassTS-R) ports. the -R subtype (2BaseTL-R or 10PassTS-R) ports.
Note that current operational Profile value is available via Note that current operational Profile value is available via
efmCuPmeOperProfile object. efmCuPmeOperProfile object.
Modification of this object must be performed when the link is Modification of this object must be performed when the link is
Down. Attempts to change this object MUST be rejected, if the Down. Attempts to change this object MUST be rejected, if the
link is Up or Initializing. link is Up or Initializing.
Attempts to set this object to a non-empty list with a member Attempts to set this object to a list with a member
value, that is not the value of the index for an active entry value, that is not the value of the index for an active entry
in the corresponding profile table, MUST be rejected." in the corresponding profile table, MUST be rejected.
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 }
::= { 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
skipping to change at page 20, line 35 skipping to change at page 21, line 39
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
with the error inconsistentValue, if the link is Up or with the error inconsistentValue, if the link is Up or
Initializing. Initializing.
Note that current Data Rate of the EFMCu port is represented Note that current Data Rate of the EFMCu port is represented
by ifSpeed object of IF-MIB." by ifSpeed object of IF-MIB.
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 initializiation. (The SNR margin
skipping to change at page 21, line 14 skipping to change at page 22, line 19
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
with the error inconsistentValue, if the link is Up or with the error inconsistentValue, if the link is Up or
Initializing. Initializing.
Note that current SNR Margin of the PMEs comprising the EFMCu Note that current SNR Margin of the PMEs comprising the EFMCu
port is represented by efmCuPmeSnrMgn." port is represented by efmCuPmeSnrMgn.
This object MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"[802.3ah] 61.1.2" "[802.3ah] 61.1.2"
::= { efmCuPortConfEntry 5 } ::= { efmCuPortConfEntry 5 }
efmCuThreshLowBandwidth OBJECT-TYPE efmCuThreshLowBandwidth OBJECT-TYPE
SYNTAX Unsigned32(0..100000) SYNTAX Unsigned32(0..100000)
UNITS "Kbps" UNITS "Kbps"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object configures the EFMCu port Low Bandwidth alarm "This object configures the EFMCu port Low Bandwidth alarm
threshold. When the current value of ifSpeed for this port threshold. When the current value of ifSpeed for this port
reaches or drops below this threshold, an reaches or drops below this threshold, an
efmCuLowBandwidth notification MAY be generated if enabled by efmCuLowBandwidth notification MAY be generated if enabled by
efmCuLowBandwidthEnable. efmCuLowBandwidthEnable.
The value of 0 means no efmCuLowBandwidth notifications The value of 0 means no efmCuLowBandwidth notifications
SHALL ever be generated. SHALL ever be generated.
This object is read-write for the -O subtype EFMCu ports This object is read-write for the -O subtype EFMCu ports
(2BaseTL-O/10PassTS-O) and not available for the -R subtypes." (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
This object MUST be maintained in a persistent manner."
::= { efmCuPortConfEntry 6 } ::= { efmCuPortConfEntry 6 }
efmCuLowBandwidthEnable OBJECT-TYPE efmCuLowBandwidthEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether efmCuLowBandwidth notifications should be "Indicates whether efmCuLowBandwidth notifications should be
generated for this interface. generated for this interface.
Value of truth(1) indicates that efmCuLowBandwidth Value of true(1) indicates that efmCuLowBandwidth
notification is enabled. Value of false(0) indicates the it is notification is enabled. Value of false(2) indicates that
disabled." the notification is disabled.
This object MUST be maintained in a persistent manner."
::= { efmCuPortConfEntry 7 } ::= { efmCuPortConfEntry 7 }
efmCuPortCapabilityTable OBJECT-TYPE efmCuPortCapabilityTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPortCapabilityEntry SYNTAX SEQUENCE OF EfmCuPortCapabilityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table for Capabilities of EFMCu 2BASE-TL/10PASS-TS (PCS) "Table for Capabilities of EFMCu 2BASE-TL/10PASS-TS (PCS)
Ports. Entries in this table MUST be maintained in a Ports. Entries in this table MUST be maintained in a
persistent manner" persistent manner"
skipping to change at page 22, line 28 skipping to change at page 23, line 38
"An entry in the EFMCu Port Capability table. "An entry in the EFMCu Port Capability table.
Each entry represents an EFMCu port indexed by the ifIndex. Each entry represents an EFMCu port indexed by the ifIndex.
Note that an EFMCu PCS port runs on top of a single Note that an EFMCu PCS port runs on top of a single
or multiple PME port(s), which are also indexed by ifIndex." or multiple PME port(s), which are also indexed by ifIndex."
INDEX { ifIndex } INDEX { ifIndex }
::= { efmCuPortCapabilityTable 1 } ::= { efmCuPortCapabilityTable 1 }
EfmCuPortCapabilityEntry ::= EfmCuPortCapabilityEntry ::=
SEQUENCE { SEQUENCE {
efmCuPAFSupported TruthValue, efmCuPAFSupported TruthValue,
efmCuPeerPAFSupported TruthValue, efmCuPeerPAFSupported TruthValueOrUnknown,
efmCuPAFCapacity Unsigned32, efmCuPAFCapacity Unsigned32,
efmCuPeerPAFCapacity Unsigned32 efmCuPeerPAFCapacity Unsigned32
} }
efmCuPAFSupported OBJECT-TYPE efmCuPAFSupported OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
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
skipping to change at page 23, line 4 skipping to change at page 24, line 15
Ports incapable of PAF SHALL return a value of false(2). Ports incapable of PAF SHALL return a value of false(2).
This object maps to the Clause 30 attribute aPAFSupported. This object maps to the Clause 30 attribute aPAFSupported.
If a Clause 45 MDIO Interface to the PCS is present, If a Clause 45 MDIO Interface to the PCS is present,
then this object maps to the PAF available bit in the then this object maps to the PAF available bit in the
10P/2B capability register." 10P/2B capability register."
REFERENCE REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.4, 45.2.3.17.1" "[802.3ah] 61.2.2, 30.11.1.1.4, 45.2.3.17.1"
::= { efmCuPortCapabilityEntry 1 } ::= { efmCuPortCapabilityEntry 1 }
efmCuPeerPAFSupported OBJECT-TYPE efmCuPeerPAFSupported OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValueOrUnknown
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 or cannot be reached Ports whose peers are incapable of PAF, SHALL return a value
because of the link state, SHALL return a value of false(2). of false(2).
Ports whose peers cannot be reached because of the link
state, SHALL return a value if 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 24, line 50 skipping to change at page 26, line 16
efmCuPAFInLargeFragments Counter32, efmCuPAFInLargeFragments Counter32,
efmCuPAFInBadFragments Counter32, efmCuPAFInBadFragments Counter32,
efmCuPAFInLostFragments Counter32, efmCuPAFInLostFragments Counter32,
efmCuPAFInLostStarts Counter32, efmCuPAFInLostStarts Counter32,
efmCuPAFInLostEnds Counter32, efmCuPAFInLostEnds Counter32,
efmCuPAFInOverflows Counter32 efmCuPAFInOverflows Counter32
} }
efmCuFltStatus OBJECT-TYPE efmCuFltStatus OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
noPeer(0), -- peer Phy cannot be reached noPeer(0),
pmeSubTypeMismatch(1), -- Assigned PMEs Sub-type Mismatch pmeSubTypeMismatch(1),
lowBandwidth(2) -- Low Bandwidth lowBandwidth(2)
} }
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 - 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.
skipping to change at page 25, line 33 skipping to change at page 26, line 47
in IF-MIB. in IF-MIB.
Additional information is available via efmCuPmeFltStatus Additional information is available via 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
"ifOperStatus in IF-MIB; efmCuPmeFltStatus" "ifOperStatus in IF-MIB; efmCuPmeFltStatus"
::= { efmCuPortStatusEntry 1 } ::= { efmCuPortStatusEntry 1 }
efmCuPortSide OBJECT-TYPE efmCuPortSide OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
subscriber(1), -- -R sub-type subscriber(1),
office(2), -- -O sub-type office(2),
unknown(3) -- no PMEs assigned or PME sub-type mismatch unknown(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"EFM port mode of operation (subtype). "EFM port mode of operation (subtype).
The value of 'subscriber' indicates the port is designated as The value of 'subscriber' indicates the port is designated as
'-R' subtype (all PMEs assigned to this port are of subtype '-R' subtype (all PMEs assigned to this port are of subtype
'-R'). '-R').
The value of the 'office' indicates that the port is The value of the 'office' indicates that the port is
designated as '-O' subtype (all PMEs assigned to this port are designated as '-O' subtype (all PMEs assigned to this port are
skipping to change at page 30, line 6 skipping to change at page 31, line 21
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." PME. This notification MAY be send on the crossing event in
-- EdNote: add throttling limitations here both directions: from normal to exceeded and from exceeded
to normal.
Generation of this notification is controlled by the
efmCuPmeLineAtnCrossingEnable object."
-- EdNote: add throttling limitations here, with 10 sec
-- debouncing on clear to prevenmt intermittent alarms
::= { 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.
-- EdNote: add throttling limitations here This notification MAY be send on the crossing event in
both directions: from normal to exceeded and from exceeded
to normal.
Generation of this notification is controlled by the
efmCuPmeSnrMgnCrossingEnable object."
-- EdNote: add throttling limitations here, with 10 sec
-- debouncing on clear to prevenmt intermittent alarms
::= { efmCuPmeNotifications 2 } ::= { efmCuPmeNotifications 2 }
efmCuPmeDeviceFault NOTIFICATION-TYPE efmCuPmeDeviceFault NOTIFICATION-TYPE
OBJECTS { OBJECTS {
efmCuPmeFltStatus efmCuPmeFltStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that a fault in the PME has been "This notification indicates that a fault in the PME has been
detected by a vendor specific diagnostic or a self-test." detected by a vendor specific diagnostic or a self-test.
-- EdNote: add throttling limitations here
Generation of this notification is controlled by the
efmCuPmeDeviceFaultEnable object."
::= { efmCuPmeNotifications 3 } ::= { efmCuPmeNotifications 3 }
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 requested
configuration profile." configuration profile.
-- EdNote: add throttling limitations here
Generation of this notification is controlled by the
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 peer PME was using
incompatible protocol during initialization." incompatible protocol during initialization.
-- EdNote: add throttling limitations here
Generation of this notification is controlled by the
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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table for Configuration of common aspects for EFMCu "Table for Configuration of common aspects for EFMCu
skipping to change at page 31, line 45 skipping to change at page 33, line 31
Each entry represents common aspects of an EFMCu PME port Each entry represents common aspects of an EFMCu PME port
indexed by the ifIndex. Note that an EFMCu PME port can be indexed by the ifIndex. Note that an EFMCu PME port can be
stacked below a single PCS port, also indexed by ifIndex, stacked below a single PCS port, also indexed by ifIndex,
possibly together with other PME ports if PAF is enabled." possibly together with other PME ports if PAF is enabled."
INDEX { ifIndex } INDEX { ifIndex }
::= { efmCuPmeConfTable 1 } ::= { efmCuPmeConfTable 1 }
EfmCuPmeConfEntry ::= EfmCuPmeConfEntry ::=
SEQUENCE { SEQUENCE {
efmCuPmeAdminSubType INTEGER, efmCuPmeAdminSubType INTEGER,
efmCuPmeAdminProfile ProfileIndex, efmCuPmeAdminProfile ProfileIndexOrZero,
efmCuPAFRemoteDiscoveryCode PhysAddress, efmCuPAFRemoteDiscoveryCode PhysAddress,
efmCuPmeThreshLineAtn Integer32, efmCuPmeThreshLineAtn Integer32,
efmCuPmeThreshSnrMgn Integer32, efmCuPmeThreshSnrMgn Integer32,
efmCuPmeLineAtnCrossingEnable TruthValue, efmCuPmeLineAtnCrossingEnable TruthValue,
efmCuPmeSnrMgnCrossingEnable TruthValue, efmCuPmeSnrMgnCrossingEnable TruthValue,
efmCuPmeDeviceFaultEnable TruthValue, efmCuPmeDeviceFaultEnable TruthValue,
efmCuPmeConfigInitFailEnable TruthValue, efmCuPmeConfigInitFailEnable TruthValue,
efmCuPmeProtocolInitFailEnable TruthValue efmCuPmeProtocolInitFailEnable TruthValue
} }
skipping to change at page 33, line 18 skipping to change at page 35, line 4
The current operational sub type is indicated by The current operational sub type is indicated by
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 this object combines values of the Port sub-type select
bits and the PMA/PMD type selection bits in the 10P/2B bits and the PMA/PMD type selection bits in the 10P/2B
PMA/PMD control register" PMA/PMD 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 ProfileIndex SYNTAX ProfileIndexOrZero
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 efmCuPme2BConfProfileTable or to an entry in either efmCuPme2BProfileTable or
efmCuPme10PConfProfileTable, depending on the current efmCuPme10PProfileTable, depending on the current
operating SubType of the PME. The value of this object is the operating SubType of the PME. The value of this object is the
index of the referenced profile. index of the referenced profile.
Note that if PME is assigned to a PCS port and value of The value of zero (default) indicates that the PME is
efmCuAdminProfile for that port is not an empty list, then the configured via efmCuAdminProfile object for the PCS port,
profile(s) referenced by efmCuAdminProfile takes precedence to which this PME is assigned. That is, the profile referenced
over the profile referenced by efmCuPmeAdminProfile, i.e. the by efmCuPmeAdminProfile takes precedence over the profile(s)
PME SHALL be configured according to 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 unavailable for the CPE (2BaseTL-O or 10PassTS-O). It is unavailable for the CPE
subtype (2BaseTL-R or 10PassTS-R). subtype (2BaseTL-R or 10PassTS-R).
Note that current operational Profile value is available via Note that current operational Profile value is available via
efmCuPmeOperProfile object. efmCuPmeOperProfile object.
Modification of this object must be performed when the link is Modification of this object must be performed when the link is
Down. Attempts to change this object MUST be rejected, if the Down. Attempts to change this object MUST be rejected, if the
link is Up or Initializing. link is Up or Initializing.
Attempts to set this object to a value that is not the Attempts to set this object to a value that is not the
value of the index for an active entry in the corresponding value of the index for an active entry in the corresponding
profile table, MUST be rejected." profile table, MUST be rejected."
REFERENCE REFERENCE
"[802.3ah] 30.11.2.1.6" "[802.3ah] 30.11.2.1.6"
DEFVAL { 0 }
::= { efmCuPmeConfEntry 2 } ::= { efmCuPmeConfEntry 2 }
efmCuPAFRemoteDiscoveryCode OBJECT-TYPE efmCuPAFRemoteDiscoveryCode OBJECT-TYPE
SYNTAX PhysAddress SYNTAX PhysAddress
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 CO.
A 6 Byte long Discovery Code of the peer PCS connected via A 6 Byte long Discovery Code of the peer PCS connected via
the PME. the PME.
skipping to change at page 36, line 5 skipping to change at page 37, line 40
::= { 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 truth(1) indicates that efmCuPmeLineAtnCrossing Value of true(1) indicates that efmCuPmeLineAtnCrossing
notification is enabled. Value of false(0) indicates the it is notification is enabled. Value of false(2) indicates that
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 truth(1) indicates that efmCuPmeSnrMgnCrossing Value of true(1) indicates that efmCuPmeSnrMgnCrossing
notification is enabled. Value of false(0) indicates the it is notification is enabled. Value of false(2) indicates that
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 truth(1) indicates that efmCuPmeDeviceFault Value of true(1) indicates that efmCuPmeDeviceFault
notification is enabled. Value of false(0) indicates the it is notification is enabled. Value of false(2) indicates that
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 truth(1) indicates that efmCuPmeConfigInitFailure Value of true(1) indicates that efmCuPmeConfigInitFailure
notification is enabled. Value of false(0) indicates the it is notification is enabled. Value of false(2) indicates that
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 truth(1) indicates that efmCuPmeProtocolInitFailure Value of true(1) indicates that efmCuPmeProtocolInitFailure
notification is enabled. Value of false(0) indicates the it is notification is enabled. Value of false(2) indicates that
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 Configuration of common aspects for EFMCu
2BASE-TL/10PASS-TS PME ports (modems). Configuration of 2BASE-TL/10PASS-TS PME ports (modems). Configuration of
aspects specific to 2BASE-TL or 10PASS-TS PME types is aspects specific to 2BASE-TL or 10PASS-TS PME types is
skipping to change at page 38, line 35 skipping to change at page 40, line 22
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,
45.2.1.12.3" 45.2.1.12.3"
::= { efmCuPmeCapabilityEntry 1 } ::= { efmCuPmeCapabilityEntry 1 }
efmCuPmeStatusTable OBJECT-TYPE efmCuPmeStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPmeStatusEntry SYNTAX SEQUENCE OF EfmCuPmeStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table for Configuration of common aspects for EFMCu "This table provides common status information of EFMCu
2BASE-TL/10PASS-TS PME ports (modems). Configuration of 2BASE-TL/10PASS-TS PME ports. Status information specific
aspects specific to 2BASE-TL or 10PASS-TS PME types is to 10PASS-TS PME is represented in efmCuPme10PStatusTable.
represented in efmCuPme2BConfTable and efmCuPme10PConfTable
respectively.
Entries in this table MUST be maintained in a persistent This table contains live data from the equipment. As such,
manner." it is NOT persistent."
::= { efmCuPme 3 } ::= { efmCuPme 3 }
efmCuPmeStatusEntry OBJECT-TYPE efmCuPmeStatusEntry OBJECT-TYPE
SYNTAX EfmCuPmeStatusEntry SYNTAX EfmCuPmeStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the EFMCu PME Status table. "An entry in the EFMCu PME Status table.
Each entry represents common aspects of an EFMCu PME port Each entry represents common aspects of an EFMCu PME port
indexed by the ifIndex. Note that an EFMCu PME port can be indexed by the ifIndex. Note that an EFMCu PME port can be
stacked below a single PCS port, also indexed by ifIndex, stacked below a single PCS port, also indexed by ifIndex,
possibly together with other PME ports if PAF is enabled." possibly together with other PME ports if PAF is enabled."
INDEX { ifIndex } INDEX { ifIndex }
::= { efmCuPmeStatusTable 1 } ::= { efmCuPmeStatusTable 1 }
EfmCuPmeStatusEntry ::= EfmCuPmeStatusEntry ::=
SEQUENCE { SEQUENCE {
efmCuPmeOperStatus INTEGER, efmCuPmeOperStatus INTEGER,
skipping to change at page 39, line 27 skipping to change at page 41, line 11
efmCuPmeOperProfile ProfileIndexOrZero, efmCuPmeOperProfile ProfileIndexOrZero,
efmCuPmeSnrMgn Integer32, efmCuPmeSnrMgn Integer32,
efmCuPmePeerSnrMgn Integer32, efmCuPmePeerSnrMgn Integer32,
efmCuPmeLineAtn Integer32, efmCuPmeLineAtn Integer32,
efmCuPmePeerLineAtn Integer32, efmCuPmePeerLineAtn Integer32,
efmCuPmeTCCodingErrors Counter32 efmCuPmeTCCodingErrors Counter32
} }
efmCuPmeOperStatus OBJECT-TYPE efmCuPmeOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), -- link is Up up(1),
downNotReady(2), -- link is Down and not Ready downNotReady(2),
downReady(3), -- link is Down and Ready downReady(3),
init(4) -- link is Initializing 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) - 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) - link is Down and the PME does not detect
Handshake tones from its peer. This value Handshake tones from its peer. This value
may indicate a possible problem with may indicate a possible problem with
skipping to change at page 40, line 15 skipping to change at page 41, line 48
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"
::= { efmCuPmeStatusEntry 1 } ::= { efmCuPmeStatusEntry 1 }
efmCuPmeFltStatus OBJECT-TYPE efmCuPmeFltStatus OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
lossOfFraming(0), -- Loss of Framing lossOfFraming(0),
snrMgnDefect(1), -- SNR Margin dropped below Threshold snrMgnDefect(1),
lineAtnDefect(2), -- Line Attenuation exceeds Threshold lineAtnDefect(2),
deviceFault(3), -- Vendor-dependent diag or self-test deviceFault(3),
-- fault configInitFailure(4),
configInitFailure(4), -- Configuration Init. failure protocolInitFailure(5)
protocolInitFailure(5) -- Protocol Initialization failure
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Current PME link Fault Status. This is a bitmap of possible "Current/Last PME link Fault Status. This is a bitmap of
conditions. The various bit positions are: possible conditions. The various bit positions are:
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,
skipping to change at page 40, line 50 skipping to change at page 42, line 34
requested during initialization. requested during initialization.
protocolInitFailure - Protocol initialization failure, protocolInitFailure - Protocol initialization failure,
due to 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 G.SDHSL/VDSL happen if a peer PMD is G.SDHSL/VDSL
modem for 2BASE-TL/10PASS-TS PME modem for 2BASE-TL/10PASS-TS PME
respectively). respectively).
This object is intended to supplement ifOperStatus in IF-MIB. This object is intended to supplement ifOperStatus in IF-MIB.
The indications hold 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 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,
10P/2B PMA/PMD link loss register, 10P/2B PMA/PMD link loss register,
10P outgoing indicator bits status register, 10P outgoing indicator bits status register,
10P incoming indicator bits status register, 10P incoming indicator bits status register,
2B state defects register." 2B state defects register."
skipping to change at page 41, line 51 skipping to change at page 43, line 44
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 ProfileIndexOrZero SYNTAX ProfileIndexOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"PME current operating Profile. This object is a pointers to "PME current operating Profile. This object is a pointer to
an entry in either efmCuPme2BConfProfileTable or an entry in either efmCuPme2BProfileTable or
efmCuPme10PConfProfileTable, depending on the current efmCuPme10PProfileTable, depending on the current
operating SubType of the PME as indicated by operating SubType of the PME as indicated by
efmCuPmeOperSubType. efmCuPmeOperSubType.
Note that a profile entry, to which efmCuPmeOperProfile is
pointing to, 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 PME is down or initializing. The value of zero indicates that PME is down or initializing.
This object partially maps to the aOperatingProfile This object partially maps to the aOperatingProfile
attribute in Clause 30." attribute 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) 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
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) 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
initializing.
This object is not supported by -R PME subtypes. This object is not supported by -R PME subtypes.
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) 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
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) 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
initializing.
This object is not supported by CPE port subtypes. This object is not supported by CPE port subtypes.
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 }
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 "A number of 64/65-octet encapsulation errors. This counter is
incremented for each 64/65-octet encapsulation error detected incremented for each 64/65-octet encapsulation error detected
by the 64/65-octet receive function. by the 64/65-octet receive function.
The value of zero SHALL be returned when PME is down or
initializing.
If a Clause 45 MDIO Interface to the PME TC is present, then If a Clause 45 MDIO Interface to the PME TC is present, then
this object maps to the TC coding violations register this object maps to the TC coding violations register
(see 45.2.6.12)." (see 45.2.6.12)."
REFERENCE REFERENCE
"[802.3ah] 61.3.3.1, 45.2.6.12" "[802.3ah] 61.3.3.1, 45.2.6.12"
::= { efmCuPmeStatusEntry 9 } ::= { efmCuPmeStatusEntry 9 }
-- 2BASE-TL specific PME group -- 2BASE-TL specific PME group
efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 } efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 }
efmCuPme2BConfProfileTable OBJECT-TYPE efmCuPme2BProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme2BConfProfileEntry SYNTAX SEQUENCE OF EfmCuPme2BProfileEntry
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 administrative and
2BASE-TL PMEs. operating Profiles for 2BASE-TL PMEs.
First 12 entries in this table SHALL always be defined as First 14 entries in this table SHALL always be defined as
follows (see 802.3ah Annex 63A): follows (see 802.3ah Annex 63A):
-------+------+-----+--------+------------------ -------+------+-----+--------+------------------
Profile Rate Power Region Constellation Profile Rate Power Region Constellation
index (Kbps) (dBm) (G.991.2) index (Kbps) (dBm) (G.991.2)
-------+------+-----+--------+------------------ -------+------+-----+--------+------------------
1 5696 13.5 Annex A 32-TCPAM 1 512 13.5 1 16-TCPAM (default)
2 3072 13.5 Annex A 32-TCPAM 2 704 13.5 1 16-TCPAM
3 2048 13.5 Annex A 16-TCPAM 3 1024 13.5 1 16-TCPAM
4 1024 13.5 Annex A 16-TCPAM 4 2048 13.5 1 16-TCPAM
5 704 13.5 Annex A 16-TCPAM 5 3072 13.5 1 32-TCPAM
6 512 13.5 Annex A 16-TCPAM 6 5696 13.5 1 32-TCPAM
7 5696 14.5 Annex B 32-TCPAM 7 512 13.5 2 16-TCPAM
8 3072 14.5 Annex B 32-TCPAM 8 704 13.5 2 16-TCPAM
9 2048 14.5 Annex B 16-TCPAM 9 1024 13.5 2 16-TCPAM
10 1024 13.5 Annex B 16-TCPAM 10 2048 14.5 2 16-TCPAM
11 704 13.5 Annex B 16-TCPAM 11 3072 14.5 2 32-TCPAM
12 512 13.5 Annex B 16-TCPAM 12 5696 14.5 2 32-TCPAM
13 0 0 1 0 (best effort)
14 0 0 2 0 (best effort)
These default entries SHALL be created by default and MUST These default entries SHALL be created during agent
not be deleted. initialization and MUST not be deleted.
Entries following the first 12, can be dynamically created and Entries following the first 14, can be dynamically created and
deleted, to provide custom profiles. deleted, to provide custom administrative (configuration)
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 }
efmCuPme2BConfProfileEntry OBJECT-TYPE efmCuPme2BProfileEntry OBJECT-TYPE
SYNTAX EfmCuPme2BConfProfileEntry 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 configuration "Each entry corresponds to a single 2BASE-TL PME profile.
profile. Each profile contains a set of configuration Each profile contains a set of parameters, used either for
parameters, which are applied to all 2BaseTL-O PMEs configuration or representation of a 2BASE-TL PME.
assigned to the 2BASE-TL (PCS) port, referencing that profile In case a particular profile is referenced via
via efmCuAdminProfile object or, if efmCuAdminProfile is zero, efmCuPmeAdminProfile object (or efmCuAdminProfile if
all 2BaseTL-O PMEs, referencing that profile via efmCuPmeAdminProfile is zero), it represent the desired
efmCuPmeAdminProfile. parameters the 2BaseTL-O PME initialization.
If a profile is referenced via efmCuPmeOperProfile object,
it represents current operating parameters of the
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 (first 12) MUST not be removed." Default entries MUST not be removed."
INDEX { efmCuPme2BProfileIndex } INDEX { efmCuPme2BProfileIndex }
::= { efmCuPme2BConfProfileTable 1 } ::= { efmCuPme2BProfileTable 1 }
EfmCuPme2BConfProfileEntry ::= EfmCuPme2BProfileEntry ::=
SEQUENCE { SEQUENCE {
efmCuPme2BProfileIndex ProfileIndex, efmCuPme2BProfileIndex ProfileIndex,
efmCuPme2BProfileDescr SnmpAdminString, efmCuPme2BProfileDescr SnmpAdminString,
efmCuPme2BRegion INTEGER, efmCuPme2BRegion INTEGER,
efmCuPme2BDataRate Unsigned32, efmCuPme2BDataRate Unsigned32,
efmCuPme2BPower Unsigned32, efmCuPme2BPower Unsigned32,
efmCuPme2BConstellation INTEGER, efmCuPme2BConstellation INTEGER,
efmCuPme2BProfileRowStatus RowStatus efmCuPme2BProfileRowStatus RowStatus
} }
efmCuPme2BProfileIndex OBJECT-TYPE efmCuPme2BProfileIndex OBJECT-TYPE
SYNTAX ProfileIndex SYNTAX ProfileIndex
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 efmCuPmeAdminProfile objects." or efmCuPmeAdminProfile objects."
::= { efmCuPme2BConfProfileEntry 1 } ::= { efmCuPme2BProfileEntry 1 }
efmCuPme2BProfileDescr OBJECT-TYPE efmCuPme2BProfileDescr OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..255)) SYNTAX SnmpAdminString (SIZE(0..255))
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 2BASE-TL 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."
::= { efmCuPme2BConfProfileEntry 2 } ::= { efmCuPme2BProfileEntry 2 }
efmCuPme2BRegion OBJECT-TYPE efmCuPme2BRegion OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
regionA(1), -- Annex A region1(1),
regionB(2), -- Annex B region2(2)
regionC(3) -- Annex C
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Desired Power Spectral Density (PSD) Regional setting as "Power Spectral Density (PSD) Regional settings as
specified in Regional Annex of [ITU-T G.991.2] to operate specified in the relevant Regional Annex of [G.991.2].
under. Regional settings place limitations on the max allowed
data rate, power and constellation.
Possible values for this object are: Possible values for this object are:
regionA -- Annex A region1 -- Annexes A and F (e.g. North America)
regionB -- Annex B region2 -- Annexes B and G (e.g. Europe)
regionC -- Annex C
Changing Regional Annex must be performed when the link is Changing of the Region must be performed when the link is
Down. Attempts to change this object MUST be rejected with Down.
Attempts to change this object MUST be rejected with
the error inconsistentValue, if the link is Up or the error inconsistentValue, if the link is Up or
Initializing. 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 Region bits in the 2B general object maps to the Region bits in the 2B general
parameter register." parameter register."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.42" "[802.3ah] 45.2.1.42"
::= { efmCuPme2BConfProfileEntry 3 } ::= { efmCuPme2BProfileEntry 3 }
efmCuPme2BDataRate OBJECT-TYPE efmCuPme2BDataRate OBJECT-TYPE
SYNTAX Unsigned32(0..5696) SYNTAX Unsigned32(0..5696)
UNITS "Kbps" UNITS "Kbps"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Desired 2BASE-TL PME Data Rate. "2BASE-TL PME Data Rate.
The rate is fixed when the value of this object is n x 64Kbps, The rate is fixed when the value of this object is n x 64Kbps,
where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM. where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM.
The value of 0 means that data rate is not fixed but is The value of 0 in the administrative profile means that data
adaptive and should be set to the maximum attainable rate rate is not fixed but is adaptive and should be set to the
during line probing. maximum attainable rate during line probing, under the
spectral limitations placed by the efmCuPme2BRegion.
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/Max Data Rate1 bits in the 2B PMD object maps to the Min/Max Data Rate1 bits in the 2B PMD
parameters register." parameters register.
This object MUST be maintained in a persistent manner."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.43" "[802.3ah] 45.2.1.43"
::= { efmCuPme2BConfProfileEntry 4 } ::= { efmCuPme2BProfileEntry 4 }
efmCuPme2BPower OBJECT-TYPE efmCuPme2BPower OBJECT-TYPE
SYNTAX Unsigned32(10..42) SYNTAX Unsigned32(0|10..42)
UNITS "0.5 dBm" UNITS "0.5 dBm"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Desired Signal Transmit Power. Multiple of 0.5dBm. "Signal Transmit Power. Multiple of 0.5dBm.
The value of 0 in the administrative profile means that the
signal transmit power is not fixed and should be set to
maximize the attainable rate, under the spectral limitations
placed by the efmCuPme2BRegion.
Changing of the Signal Transmit Power must be performed when Changing of the Signal Transmit Power 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 with the error inconsistentValue, if the link is Up rejected with the error inconsistentValue, if the link is Up
or Initializing. 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 will map to the Power1 bits in the 2B PMD object will map to the Power1 bits in the 2B PMD
parameters register" parameters register"
REFERENCE REFERENCE
"[802.3ah] 45.2.1.43" "[802.3ah] 45.2.1.43"
::= { efmCuPme2BConfProfileEntry 5 } ::= { efmCuPme2BProfileEntry 5 }
efmCuPme2BConstellation OBJECT-TYPE efmCuPme2BConstellation OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
tcpam16(1), -- 16-TCPAM adaptive(0),
tcpam32(2) -- 32-TCPAM tcpam16(1),
tcpam32(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Desired TCPAM Constellation of the 2BASE-TL PME. The possible "TCPAM Constellation of the 2BASE-TL PME.
values are: The possible values are:
adaptive(0) - either 16- or 32-TCPAM
tcpam16(1) - 16-TCPAM tcpam16(1) - 16-TCPAM
tcpam32(2) - 32-TCPAM tcpam32(2) - 32-TCPAM
The value of adaptive(0) in the administrative profile means
that the constellation is not fixed and should be set to
maximize the attainable rate, under the spectral limitations
placed by the efmCuPme2BRegion.
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 map to the Constellation1 bits in the 2B general object map to the Constellation1 bits in the 2B general
parameter register." parameter register."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.43" "[802.3ah] 45.2.1.43"
::= { efmCuPme2BConfProfileEntry 6 } ::= { efmCuPme2BProfileEntry 6 }
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/deletion of the associated "This object controls creation/deletion of the associated
entry in efmCuPme2BConfProfileTable per the semantics of entry in efmCuPme2BProfileTable per the semantics of
RowStatus. 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, the entry MUST remain 'active' until all
references are removed." references are removed."
::= { efmCuPme2BConfProfileEntry 7 } ::= { efmCuPme2BProfileEntry 7 }
-- 10PASS-TS specific PME group -- 10PASS-TS specific PME group
efmCuPme10P OBJECT IDENTIFIER ::= { efmCuPme 6 } efmCuPme10P OBJECT IDENTIFIER ::= { efmCuPme 6 }
efmCuPme10PConfProfileTable OBJECT-TYPE efmCuPme10PProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme10PConfProfileEntry 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
10PassTL PMEs. 10PassTL PMEs.
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): follows (see 802.3ah Annex 62B.3):
-------+--------+----+---------+-----+------------ -------+--------+----+---------+-----+------------
Profile Bandplan UPBO BandNotch DRate URate Profile Bandplan UPBO BandNotch DRate URate
Index PSDMask# p# p# p# p# Index PSDMask# p# p# p# p#
skipping to change at page 48, line 47 skipping to change at page 51, line 27
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 default and MUST These default entries SHALL be created by during agent
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 profiles. deleted, to provide custom administrative (configuration)
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 }
efmCuPme10PConfProfileEntry OBJECT-TYPE efmCuPme10PProfileEntry OBJECT-TYPE
SYNTAX EfmCuPme10PConfProfileEntry 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
configuration profile. Each profile contains a set of profile.
configuration parameters, which are applied to all PMEs Each profile contains a set of parameters, used either for
assigned to the 10PASS-TS (PCS) port, referencing that profile configuration or representation of a 10PASS-TS PME.
via efmCuAdminProfile object, or, if efmCuAdminProfile is In case a particular profile is referenced via
zero, to all PMEs referencing that profile via efmCuPmeAdminProfile object (or efmCuAdminProfile if
efmCuPmeAdminProfile. efmCuPmeAdminProfile is zero), it represent the desired
parameters the 10PassTS-O PME initialization.
If a profile is referenced via efmCuPmeOperProfile object,
it represents 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 (first 22) MUST not be removed." Default entries MUST not be removed."
INDEX { efmCuPme10PProfileIndex } INDEX { efmCuPme10PProfileIndex }
::= { efmCuPme10PConfProfileTable 1 } ::= { efmCuPme10PProfileTable 1 }
EfmCuPme10PConfProfileEntry ::= EfmCuPme10PProfileEntry ::=
SEQUENCE { SEQUENCE {
efmCuPme10PProfileIndex ProfileIndex, efmCuPme10PProfileIndex ProfileIndex,
efmCuPme10PProfileDescr SnmpAdminString, efmCuPme10PProfileDescr SnmpAdminString,
efmCuPme10PBandplanPSDMskProfile INTEGER, efmCuPme10PBandplanPSDMskProfile INTEGER,
efmCuPme10PUPBOReferenceProfile INTEGER, efmCuPme10PUPBOReferenceProfile INTEGER,
efmCuPme10PBandNotchProfiles BITS, efmCuPme10PBandNotchProfiles BITS,
efmCuPme10PPayloadURateProfile INTEGER, efmCuPme10PPayloadURateProfile INTEGER,
efmCuPme10PPayloadDRateProfile INTEGER, efmCuPme10PPayloadDRateProfile INTEGER,
efmCuPme10PProfileRowStatus RowStatus efmCuPme10PProfileRowStatus RowStatus
} }
efmCuPme10PProfileIndex OBJECT-TYPE efmCuPme10PProfileIndex OBJECT-TYPE
SYNTAX ProfileIndex SYNTAX ProfileIndex
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."
::= { efmCuPme10PConfProfileEntry 1 } ::= { efmCuPme10PProfileEntry 1 }
efmCuPme10PProfileDescr OBJECT-TYPE efmCuPme10PProfileDescr OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..255)) SYNTAX SnmpAdminString (SIZE(0..255))
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 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."
::= { efmCuPme10PConfProfileEntry 2 } ::= { efmCuPme10PProfileEntry 2 }
efmCuPme10PBandplanPSDMskProfile OBJECT-TYPE efmCuPme10PBandplanPSDMskProfile OBJECT-TYPE
SYNTAX INTEGER {-- PSD Mask Bands Bandplan SYNTAX INTEGER {
profile1(1), -- T1.424/T-U P1 FTTCab.M1 x/D/U/D/U A profile1(1),
profile2(2), -- T1.424/T-U P1 FTTEx.M1 profile2(2),
profile3(3), -- T1.424/T-U P1 FTTCab.M2 profile3(3),
profile4(4), -- T1.424/T-U P1 FTTEx.M2 profile4(4),
profile5(5), -- T1.424/T-U P1 FTTCab.M1 D/D/U/D/U profile5(5),
profile6(6), -- T1.424/T-U P1 FTTEx.M1 profile6(6),
profile7(7), -- T1.424/T-U P1 FTTCab.M2 profile7(7),
profile8(8), -- T1.424/T-U P1 FTTEx.M2 profile8(8),
profile9(9), -- T1.424/T-U P1 FTTCab.M1 U/D/U/D/x profile9(9),
profile10(10), -- T1.424/T-U P1 FTTEx.M1 profile10(10),
profile11(11), -- T1.424/T-U P1 FTTCab.M2 profile11(11),
profile12(12), -- T1.424/T-U P1 FTTEx.M2 profile12(12),
profile13(13), -- TS1 101 270-1 Pcab.M1.A x/D/U/D/U B profile13(13),
profile14(14), -- TS1 101 270-1 Pcab.M1.B profile14(14),
profile15(15), -- TS1 101 270-1 Pex.P1.M1 profile15(15),
profile16(16), -- TS1 101 270-1 Pex.P2.M1 profile16(16),
profile17(17), -- TS1 101 270-1 Pcab.M2 profile17(17),
profile18(18), -- TS1 101 270-1 Pex.P1.M2 profile18(18),
profile19(19), -- TS1 101 270-1 Pex.P2.M2 profile19(19),
profile20(20), -- TS1 101 270-1 Pcab.M1.A U/D/U/D/x profile20(20),
profile21(21), -- TS1 101 270-1 Pcab.M1.B profile21(21),
profile22(22), -- TS1 101 270-1 Pex.P1.M1 profile22(22),
profile23(23), -- TS1 101 270-1 Pex.P2.M1 profile23(23),
profile24(24), -- TS1 101 270-1 Pcab.M2 profile24(24),
profile25(25), -- TS1 101 270-1 Pex.P1.M2 profile25(25),
profile26(26), -- TS1 101 270-1 Pex.P2.M2 profile26(26),
profile27(27), -- G.993.1 F.1.2.1 (VDSLoPOTS) x/D/U/D/U F profile27(27),
profile28(28), -- G.993.1 F.1.2.2 (VDSLoTCM-ISDN) profile28(28),
profile29(29) -- G.993.1 F.1.2.3 (PSD reduction) profile29(29)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"10PASS-TS PME Bandplan and PSD Mask profile, "10PASS-TS PME Bandplan and PSD Mask profile,
as specified in 802.3ah Annex 62A. Possible values are: as specified in 802.3ah Annex 62A. Possible values are:
--------------+------------------------+-----------+--------- --------------+------------------------+-----------+---------
Profile Name PSD Mask Bands Bandplan Profile Name PSD Mask Bands Bandplan
--------------+------------------------+-----------+--------- --------------+------------------------+-----------+---------
profile1(1) - T1.424/T-U P1 FTTCab.M1 x/D/U/D/U A profile1(1) - T1.424/T-U P1 FTTCab.M1 x/D/U/D/U A
skipping to change at page 51, line 40 skipping to change at page 54, line 26
profile25(25) - TS1 101 270-1 Pex.P1.M2 profile25(25) - TS1 101 270-1 Pex.P1.M2
profile26(26) - TS1 101 270-1 Pex.P2.M2 profile26(26) - TS1 101 270-1 Pex.P2.M2
profile27(27) - G.993.1 F.1.2.1 (VDSLoPOTS) x/D/U/D/U F profile27(27) - G.993.1 F.1.2.1 (VDSLoPOTS) x/D/U/D/U F
profile28(28) - G.993.1 F.1.2.2 (VDSLoTCM-ISDN) profile28(28) - G.993.1 F.1.2.2 (VDSLoTCM-ISDN)
profile29(29) - G.993.1 F.1.2.3 (PSD reduction) profile29(29) - G.993.1 F.1.2.3 (PSD reduction)
This object maps to the aBandplanPSDMaskProfile attribute This object maps to the aBandplanPSDMaskProfile attribute
in Clause 30." in Clause 30."
REFERENCE REFERENCE
"[802.3ah] Annex 62A, 30.5.1.1.22" "[802.3ah] Annex 62A, 30.5.1.1.22"
::= { efmCuPme10PConfProfileEntry 3 } ::= { efmCuPme10PProfileEntry 3 }
efmCuPme10PUPBOReferenceProfile OBJECT-TYPE efmCuPme10PUPBOReferenceProfile OBJECT-TYPE
SYNTAX INTEGER {-- Reference PSD SYNTAX INTEGER {
profile1(1), -- T1.424/T-U Noise A M1 profile1(1),
profile2(2), -- T1.424/T-U Noise A M2 profile2(2),
profile3(3), -- T1.424/T-U Noise F M1 profile3(3),
profile4(4), -- T1.424/T-U Noise F M2 profile4(4),
profile5(5), -- ETSI TS 101 270-1 Noise A&B profile5(5),
profile6(6), -- ETSI TS 101 270-1 Noise C profile6(6),
profile7(7), -- ETSI TS 101 270-1 Noise D profile7(7),
profile8(8), -- ETSI TS 101 270-1 Noise E profile8(8),
profile9(9) -- ETSI TS 101 270-1 Noise F 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 "10PASS-TS PME Upstream Power Back-Off (UPBO) Reference PSD
Profile, as specified in 802.3ah Annex 62A. Possible values Profile, as specified in 802.3ah Annex 62A. Possible values
are: are:
profile1(1) - T1.424/T-U Noise A M1 profile1(1) - T1.424/T-U Noise A M1
profile2(2) - T1.424/T-U Noise A M2 profile2(2) - T1.424/T-U Noise A M2
profile3(3) - T1.424/T-U Noise F M1 profile3(3) - T1.424/T-U Noise F M1
skipping to change at page 52, line 26 skipping to change at page 55, line 12
profile5(5) - ETSI TS 101 270-1 Noise A&B profile5(5) - ETSI TS 101 270-1 Noise A&B
profile6(6) - ETSI TS 101 270-1 Noise C profile6(6) - ETSI TS 101 270-1 Noise C
profile7(7) - ETSI TS 101 270-1 Noise D profile7(7) - ETSI TS 101 270-1 Noise D
profile8(8) - ETSI TS 101 270-1 Noise E profile8(8) - ETSI TS 101 270-1 Noise E
profile9(9) - ETSI TS 101 270-1 Noise F profile9(9) - ETSI TS 101 270-1 Noise F
This object maps to the aUPBOReferenceProfile attribute This object maps to the aUPBOReferenceProfile attribute
in Clause 30." in Clause 30."
REFERENCE REFERENCE
"[802.3ah] Annex 62A.3.4, 30.5.1.1.23" "[802.3ah] Annex 62A.3.4, 30.5.1.1.23"
::= { efmCuPme10PConfProfileEntry 4 } ::= { efmCuPme10PProfileEntry 4 }
efmCuPme10PBandNotchProfiles OBJECT-TYPE efmCuPme10PBandNotchProfiles OBJECT-TYPE
SYNTAX BITS { -- G.991.3 T1.424/T-U TS101 270-1 StartF EndF SYNTAX BITS {
-- Table Table Table (MHz) (MHz) profile0(0),
profile0(0), -- no profile profile1(1),
profile1(1), -- F-5 #01 - - 1.810 1.825 profile2(2),
profile2(2), -- 6-2 15-1 17 1.810 2.000 profile3(3),
profile3(3), -- F-5 #02 - - 1.907 1.912 profile4(4),
profile4(4), -- F-5 #03 - - 3.500 3.575 profile5(5),
profile5(5), -- 6-2 - 17 3.500 3.800 profile6(6),
profile6(6), -- - 15-1 - 3.500 4.000 profile7(7),
profile7(7), -- F-5 #04 - - 3.747 3.754 profile8(8),
profile8(8), -- F-5 #05 - - 3.791 3.805 profile9(9),
profile9(9), -- 6-2 - 17 7.000 7.100 profile10(10),
profile10(10),-- F-5 #06 15-1 - 7.000 7.300 profile11(11)
profile11(11) -- 6-2 15-1 1 10.100 10.150
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"10PASS-TS PME Egress Control Band Notch Profile bitmap, "10PASS-TS PME Egress Control Band Notch Profile bitmap,
as specified in 802.3ah Annex 62A. Possible values are: as specified in 802.3ah Annex 62A. Possible values are:
--------------+---------+----------+-----------+------+----- --------------+---------+----------+-----------+------+-----
Profile Name G.991.3 T1.424/T-U TS101 270-1 StartF EndF Profile Name G.991.3 T1.424/T-U TS101 270-1 StartF EndF
Table Table Table (MHz) (MHz) Table Table Table (MHz) (MHz)
--------------+---------+----------+-----------+------+----- --------------+---------+----------+-----------+------+-----
skipping to change at page 53, line 26 skipping to change at page 56, line 11
profile11(11) - 6-2 15-1 1 10.100 10.150 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 0x0622 selects
profiles 2,6,10 and 11. profiles 2,6,10 and 11.
This object maps to the aBandNotchProfile attribute This object maps to the aBandNotchProfile attribute
in Clause 30." in Clause 30."
REFERENCE REFERENCE
"[802.3ah] Annex 62A.3.5, 30.5.1.1.19" "[802.3ah] Annex 62A.3.5, 30.5.1.1.19"
::= { efmCuPme10PConfProfileEntry 5 } ::= { efmCuPme10PProfileEntry 5 }
efmCuPme10PPayloadURateProfile OBJECT-TYPE efmCuPme10PPayloadURateProfile OBJECT-TYPE
SYNTAX INTEGER {-- Upstream Payload Rate (Mbps) SYNTAX INTEGER {
profile5(5), -- 2.5 profile5(5),
profile10(10), -- 5 profile10(10),
profile15(15), -- 7.5 profile15(15),
profile20(20), -- 10 profile20(20),
profile25(25), -- 12.5 profile25(25),
profile30(30), -- 15 profile30(30),
profile50(50), -- 25 profile50(50),
profile70(70), -- 35 profile70(70),
profile100(100) -- 50 profile100(100)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"10PASS-TS PME Upstream Payload Rate Profile, "10PASS-TS PME Upstream Payload Rate Profile,
as specified in 802.3ah Annex 62A. Possible values are: as specified in 802.3ah 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
skipping to change at page 54, line 17 skipping to change at page 56, line 50
Each value represents a target for the PME's Upstream Payload Each value represents a target for the PME's Upstream Payload
Bitrate as seen at the MII. If the payload rate of the Bitrate as seen at the MII. If the payload rate of 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 aPayloadRateProfileUpstream This object maps to the aPayloadRateProfileUpstream
attribute in Clause 30." attribute in Clause 30."
REFERENCE REFERENCE
"[802.3ah] Annex 62A.3.6, 30.5.1.1.20" "[802.3ah] Annex 62A.3.6, 30.5.1.1.20"
::= { efmCuPme10PConfProfileEntry 6 } ::= { efmCuPme10PProfileEntry 6 }
efmCuPme10PPayloadDRateProfile OBJECT-TYPE efmCuPme10PPayloadDRateProfile OBJECT-TYPE
SYNTAX INTEGER {-- Downstream Payload Rate (Mbps) SYNTAX INTEGER {
profile5(5), -- 2.5 profile5(5),
profile10(10), -- 5 profile10(10),
profile15(15), -- 7.5 profile15(15),
profile20(20), -- 10 profile20(20),
profile25(25), -- 12.5 profile25(25),
profile30(30), -- 15 profile30(30),
profile50(50), -- 25 profile50(50),
profile70(70), -- 35 profile70(70),
profile100(100), -- 50 profile100(100),
profile140(140), -- 70 profile140(140),
profile200(200) -- 100 profile200(200)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"10PASS-TS PME Downstream Payload Rate Profile, "10PASS-TS PME Downstream Payload Rate Profile,
as specified in 802.3ah Annex 62A. Possible values are: as specified in 802.3ah 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
skipping to change at page 55, line 12 skipping to change at page 57, line 45
Each value represents a target for the PME's Downstream Each value represents a target for the PME's Downstream
Payload Bitrate as seen at the MII. If the payload rate of Payload Bitrate as seen at the MII. If the payload rate of
the 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 aPayloadRateProfileDownstream This object maps to the aPayloadRateProfileDownstream
attribute in Clause 30." attribute in Clause 30."
REFERENCE REFERENCE
"[802.3ah] Annex 62A.3.6, 30.5.1.1.21" "[802.3ah] Annex 62A.3.6, 30.5.1.1.21"
::= { efmCuPme10PConfProfileEntry 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/deletion of the associated "This object controls creation/deletion of the associated
entry in efmCuPme10PConfProfileTable per the semantics of entry in efmCuPme10PProfileTable per the semantics of
RowStatus. 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 efmCuPmeAdminProfile, the entry MUST remain 'active' until
all references are removed." all references are removed."
::= { efmCuPme10PConfProfileEntry 8 } ::= { efmCuPme10PProfileEntry 8 }
efmCuPme10PStatusTable OBJECT-TYPE efmCuPme10PStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme10PStatusEntry SYNTAX SEQUENCE OF EfmCuPme10PStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table reflecting status of EFMCu 10PASS-TS PMEs (modems)." "Table reflecting status of EFMCu 10PASS-TS PMEs (modems)."
::= { efmCuPme10P 2 } ::= { efmCuPme10P 2 }
efmCuPme10PStatusEntry OBJECT-TYPE efmCuPme10PStatusEntry OBJECT-TYPE
skipping to change at page 57, line 47 skipping to change at page 60, line 33
This table is read only as it describes device capability" This table is read only as it describes device capability"
REFERENCE REFERENCE
"ifStackTable of RFC 2863" "ifStackTable of RFC 2863"
::= { efmCuObjects 3 } ::= { efmCuObjects 3 }
ifAvailableStackEntry OBJECT-TYPE ifAvailableStackEntry OBJECT-TYPE
SYNTAX IfAvailableStackEntry SYNTAX IfAvailableStackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information on a particular relationship between two sub- "Information on a particular relationship between two
layers, specifying that one sub-layer (PCS) runs on 'top' of sub-layers, specifying that one sub-layer (PCS) runs on 'top'
the other sub-layer (PME). Each sub-layer corresponds to a of the other sub-layer (PME). Each sub-layer corresponds to a
conceptual row in the ifTable (interface index for PCS and conceptual row in the ifTable (interface index for PCS and
PME respectively)." PME respectively)."
INDEX { INDEX {
ifAvailableStackHigherLayer, ifAvailableStackHigherLayer,
ifAvailableStackLowerLayer ifAvailableStackLowerLayer
} }
::= { ifAvailableStackTable 1 } ::= { ifAvailableStackTable 1 }
IfAvailableStackEntry ::= IfAvailableStackEntry ::=
SEQUENCE { SEQUENCE {
skipping to change at page 65, line 21 skipping to change at page 68, line 7
example: example:
o Changing of efmCuPmeAdminSubType MAY lead to a potential locking o Changing of efmCuPmeAdminSubType MAY lead to a potential locking
of the link, as peer PMEs of the same sub-type cannot exchange of the link, as peer PMEs of the same sub-type cannot exchange
handshake messages. handshake messages.
o Changing of efmCuPAFAdminState to enabled MAY lead to a potential o Changing of efmCuPAFAdminState to enabled MAY lead to a potential
locking of the link, if the peer Phy does not support PAF. locking of the link, if the peer Phy does not support PAF.
o Changing of efmCuPAFDiscoveryCode, before the discovery operation, o Changing of efmCuPAFDiscoveryCode, before the discovery operation,
MAY lead to a wrongful discovery, with possile multiple -O ports MAY lead to a wrongful discovery, for example when two -O ports
connecting to the same -R (both -O ports have the same Discovery are connected to the same multi-PME -R port and both -O ports have
register value) and similar cases. the same Discovery register value.
o Changing PCS or PME configuration parameters (e.g. profile of a o Changing PCS or PME configuration parameters (e.g. profile of a
PCS or PME via efmCuAdminProfile or efmCuPmeAdminProfile) MAY lead PCS or PME via efmCuAdminProfile or efmCuPmeAdminProfile) MAY lead
to anything from link quality and rate degradation to a complete to anything from link quality and rate degradation to a complete
link initialization failure, as ability of an EFMCu port to link initialization failure, as ability of an EFMCu port to
support a particular configuration depends on the copper support a particular configuration depends on the copper
environment. environment.
o Activation of a PME can cause a severe degradation of service for o Activation of a PME can cause a severe degradation of service for
another EFMCu Phy whose PME(s) MAY be affected by the cross-talk another EFMCu Phy, whose PME(s) MAY be affected by the cross-talk
from the newly activated PME. from the newly activated PME.
o Removal of a PME from the operationally 'up' EFMCu port, o Removal of a PME from an operationally 'up' EFMCu port,
aggregating several PMEs, MAY lead a link rate degradation aggregating several PMEs, MAY cause port's rate degradation
The user of this MIB module must therefore be aware that support for The user of this MIB module must therefore be aware that support for
SET operations in a non-secure environment without proper protection SET operations in a non-secure environment without proper protection
can have a negative effect on network operations. can have a negative effect on network operations.
The readable objects in this MIB module (i.e., those with MAX-ACCESS The readable objects in this MIB module (i.e., those with MAX-ACCESS
other than not-accessible) may be considered sensitive in some 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
skipping to change at page 66, line 27 skipping to change at page 69, line 14
authentication and privacy). authentication and privacy).
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 this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate 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.
7. Acknowledgments 7. IANA Considerations
The two new values of dot3MauType (dot3MauType2BaseTL and
dot3MauType10PassTS) and corresponding IANAifMauTypeListBits bit
definitions (b2BaseTL and b10PassTS) SHALL be defined by the IANA in
the IANA-MAU-TC-MIB module (see [I-D.ietf-hubmib-rfc3636bis]) before
this document is published as an RFC.
8. 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, whose efforts were greatly advanced by the MIB Working Group, whose efforts were greatly advanced by the
contributions of the following people (in alphabetical order): contributions of the following people (in alphabetical order):
Dan Romascanu Dan Romascanu
Mathias Riess Mathias Riess
Matt Squire Matt Squire
Mike Heard Mike Heard
Udi Ashkenazi Udi Ashkenazi
8. References 9. References
8.1 Normative References 9.1 Normative References
[802.3ah] IEEE, "Draft amendment to - Information technology - [802.3ah] IEEE, "IEEE Standard for Information technology -
Telecommunications and information exchange between Telecommunications and information exchange between
systems - Local and metropolitan area networks - Specific systems - Local and metropolitan area networks - Specific
requirements - Part 3: Carrier sense multiple access with requirements - Part 3: Carrier Sense Multiple Access with
collision detection (CSMA/CD) access method and physical Collision Detection (CSMA/CD) Access Method and Physical
layer specifications - Media Access Control Parameters, Layer Specifications - Amendment: Media Access Control
Physical Layers and Management Parameters for Subscriber Parameters, Physical Layers and Management Parameters for
Access Networks", IEEE Std 802.3ah-2004, September 2004. Subscriber Access Networks", IEEE Std 802.3ah-2004,
September 2004.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction to Version 3 of the Internet-standard "Introduction to Version 3 of the Internet-standard
Network Management Framework", RFC 2570, April 1999. Network Management Framework", RFC 2570, April 1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of
skipping to change at page 67, line 34 skipping to change at page 70, line 30
[RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
8.2 Informative References 9.2 Informative References
[G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber Line
(SHDSL) transceivers", ITU-T Recommendation G.991.2,
December 2003.
[G.993.1] ITU-T, "Very High speed Digital Subscriber Line
transceivers", ITU-T Recommendation G.993.1, June 2004.
[I-D.ietf-adslmib-gshdslbis] [I-D.ietf-adslmib-gshdslbis]
Sikes, C., Ray, B. and R. Abbi, "Definitions of Managed Sikes, C., Ray, B. and R. Abbi, "Definitions of Managed
Objects for G.SHDSL.BIS Lines", Objects for G.shdsl.bis Lines",
draft-ietf-adslmib-gshdslbis-02 (work in progress), June draft-ietf-adslmib-gshdslbis-09 (work in progress), March
2004. 2005.
[I-D.ietf-adslmib-vdsl-ext-mcm] [I-D.ietf-adslmib-vdsl-ext-mcm]
Dodge, M. and B. Ray, "Definitions of Managed Object 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", draft-ietf-adslmib-vdsl-ext-mcm-04 (work in Coding", draft-ietf-adslmib-vdsl-ext-mcm-06 (work in
progress), May 2004. progress), January 2005.
[I-D.ietf-hubmib-efm-epon-mib] [I-D.ietf-hubmib-efm-epon-mib]
Khermosh, L., "Managed Objects for the Ethernet Passive Khermosh, L., "Managed Objects for the Ethernet Passive
Optical Networks", draft-ietf-hubmib-efm-epon-mib-02 (work Optical Networks", draft-ietf-hubmib-efm-epon-mib-03 (work
in progress), September 2004. in progress), March 2005.
[I-D.ietf-hubmib-efm-mib] [I-D.ietf-hubmib-efm-mib]
Squire, M., "Ethernet in the First Mile (EFM) Common MIB", Squire, M., "Ethernet in the First Mile (EFM) Common MIB",
draft-ietf-hubmib-efm-mib-01 (work in progress), June draft-ietf-hubmib-efm-mib-03 (work in progress), March
2004. 2005.
[I-D.ietf-hubmib-rfc3636bis] [I-D.ietf-hubmib-rfc3636bis]
Beili, E., "Definitions of Managed Objects for IEEE 802.3 Beili, E., "Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs)", Medium Attachment Units (MAUs)",
draft-ietf-hubmib-rfc3636bis-00 (work in progress), draft-ietf-hubmib-rfc3636bis-00 (work in progress),
October 2004. October 2004.
[IANAifType-MIB] [IANAifType-MIB]
Internet Assigned Numbers Authority (IANA), "IANAifType Internet Assigned Numbers Authority (IANA), "IANAifType
Textual Convention definition", Textual Convention definition",
skipping to change at page 69, line 41 skipping to change at page 72, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

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