draft-ietf-hubmib-efm-cu-mib-01.txt   draft-ietf-hubmib-efm-cu-mib-02.txt 
Network Working Group E. Beili Network Working Group E. Beili
Internet-Draft Actelis Networks Internet-Draft Actelis Networks
Expires: January 14, 2005 July 16, 2004 Expires: January 30, 2005 Aug 2004
Ethernet in the First Mile Copper (EFMCu) Interfaces MIB Ethernet in the First Mile Copper (EFMCu) Interfaces MIB
draft-ietf-hubmib-efm-cu-mib-01.txt draft-ietf-hubmib-efm-cu-mib-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable This document is an Internet-Draft and is subject to all provisions
patent or other IPR claims of which I am aware have been disclosed, of section 3 of RFC 3667. By submitting this Internet-Draft, each
and any of which I become aware will be disclosed, in accordance with 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 become aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as other groups may also distribute working documents as
Internet-Drafts. Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 14, 2005. This Internet-Draft will expire on January 30, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004).
Abstract Abstract
This document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in TCP/IP based (MIB) for use with network management protocols in TCP/IP based
nternets. This document proposes an extension to the Ethernet-like internets. This document proposes an extension to the Ethernet-like
Interfaces MIB and MAU MIB with a set of objects for managing an Interfaces MIB and MAU MIB 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 standard 802.3ah. 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 MIBs . . . . . . . . . . . . . . . . . . . . 4
3.1 Relation to Interfaces Group MIB . . . . . . . . . . . . . 4 3.1 Relation to Interfaces Group MIB . . . . . . . . . . . . . 4
3.1.1 Layering Model . . . . . . . . . . . . . . . . . . . . 4 3.1.1 Layering Model . . . . . . . . . . . . . . . . . . . . 4
3.1.2 PME Aggregation Function (PAF) . . . . . . . . . . . . 5 3.1.2 PME Aggregation Function (PAF) . . . . . . . . . . . . 6
3.1.3 Discovery Operation . . . . . . . . . . . . . . . . . 5 3.1.3 Discovery Operation . . . . . . . . . . . . . . . . . 6
3.1.4 EFMCu ports initialization . . . . . . . . . . . . . . 7 3.1.4 EFMCu ports initialization . . . . . . . . . . . . . . 8
3.1.5 Usage of ifTable . . . . . . . . . . . . . . . . . . . 7 3.1.5 Usage of ifTable . . . . . . . . . . . . . . . . . . . 8
3.2 Relation to SHDSL MIB . . . . . . . . . . . . . . . . . . 8 3.2 Relation to SHDSL MIB . . . . . . . . . . . . . . . . . . 9
3.3 Relation to VDSL MIB . . . . . . . . . . . . . . . . . . . 9 3.3 Relation to VDSL MIB . . . . . . . . . . . . . . . . . . . 10
3.4 Relation to Ethernet-Like and MAU MIBs . . . . . . . . . . 9 3.4 Relation to Ethernet-Like and MAU MIBs . . . . . . . . . . 10
4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 9 4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 11
4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2 Configuration Profiles . . . . . . . . . . . . . . . . . . 10 4.2 Configuration Profiles . . . . . . . . . . . . . . . . . . 11
4.3 Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 10 4.3 Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 12
5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 13
6. Security Considerations . . . . . . . . . . . . . . . . . . . 63 6. Security Considerations . . . . . . . . . . . . . . . . . . . 65
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 64 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 66
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 65 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 66
8.1 Normative References . . . . . . . . . . . . . . . . . . . . 65 8.1 Normative References . . . . . . . . . . . . . . . . . . . . 66
8.2 Informative References . . . . . . . . . . . . . . . . . . . 65 8.2 Informative References . . . . . . . . . . . . . . . . . . . 67
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 66 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 68
Intellectual Property and Copyright Statements . . . . . . . . 67 Intellectual Property and Copyright Statements . . . . . . . . 69
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) 802.3ah project a.k.a.
Ethernet in the First Mile (EFM) [802.3ah]. In particular 2Base-TL Ethernet in the First Mile (EFM) [802.3ah]. In particular 2BASE-TL
and 10Pass-TS physical interfaces (PHYs), defined over voice-grade and 10PASS-TS physical interfaces (PHYs), defined over voice-grade
copper pairs, have been specified for the long and short reach copper pairs, have been specified for the long and short reach
respectively. These interfaces, collectively called EFMCu, are based respectively. These interfaces, collectively called EFMCu, are based
on ITU-T G.SHDSL and VDSL specifications and support variable rates on ITU-T G.SHDSL and VDSL specifications and support variable rates
and optional Physical Medium Entity (PME) aggregation (a.k.a. and optional Physical Medium Entity (PME) aggregation (a.k.a.
multi-pair bonding). 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 portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community for use with network management protocols in the Internet community
to manage EFMCu interfaces. to manage EFMCu interfaces.
skipping to change at page 4, line 8 skipping to change at page 4, line 8
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 MIBs
This section outlines the relationship of this MIB with other MIBs This section outlines the relationship of this MIB with other MIB
described in the relevant RFCs. Specifically, Interfaces Group MIB modules described in the relevant RFCs. Specifically, Interfaces
(IF-MIB), Ethernet-Like (EtherLike-MIB), MAU (MAU-MIB), SHDSL Group MIB (IF-MIB), Ethernet-Like (EtherLike-MIB), MAU (MAU-MIB),
(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
2Base-TL and 10Pass-TS PHY's specified in this MIB are stacked 2BASE-TL and 10PASS-TS PHY's specified in this MIB 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 in 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) sublayer devices (modems), using so called PME Aggregation (PME) sub-layer devices (modems), using so called PME Aggregation
Function (PAF). Function (PAF).
An generic EFMCu device can have a number of Physical Coding Sublayer A generic EFMCu device can have a number of Physical Coding Sublayer
(PCS) ports, connected to a MAC via Medium Independent Interface (PCS) ports, connected to a MAC via Medium Independent Interface
(MII) at the upper layer, and cross-connected to a number of (MII) at the upper layer, and cross-connected to a number of
underlying PMEs, with a single PCS per PME relationship, see clause underlying PMEs, with a single PCS per PME relationship, see clause
61.1 of [802.3ah] for more details. 61.1 of [802.3ah] for more details.
Each PME comprising an aggregated EFMCu port is represented in the Each PME in the aggregated EFMCu port is represented in the Interface
Interface table 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. ifSpeed for each PME shall return an actual bitrate [IANAifType-MIB].
of the active PME or a configured bitrate for pre-activated modems
(note that unassigned PME has its default bitrate). ifSpeed for each PME shall return the actual data bitrate of the
active PME or a configured bitrate for pre-activated modems (e.g.
for 2BaseTL PMEs it is a multiple of 64Kbps). The ifSpeed of the PCS
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
are configured to generate 100% of back to back traffic, i.e.
minimal IFG, at 10Mbps; the EFM interfaces are obviously aggregated)
):
[testset]--10BaseT--[CO]--2BaseTL--[CPE]--10BaseT--[testset]
ifSpeed=10Mbps ifSpeed=10Mbps ifSpeed=10Mbps
[testset]--100BaseT--[CO]--10PassTS--[CPE]--100BaseT--[testset]
ifSpeed=100Mbps ifSpeed=100Mbps ifSpeed=100Mbps
Figure 1: Example configuration with no frame loss
The following figure shows the layering diagram and corresponding use
of ifTable and ifMauTable:
_________________________ _
| LLC | |
+-------------------------+ | 1 ifEntry
| MAC | | ifType: ethernetCsmacd(6)
+-------------------------+ > ifMauEntry
| Reconsiliation | | ifMauType: dot3MauType2BaseTL or
+-------------------------+ | dot3MauType10PassTS
| PCS | |
+-------------+---+-------+ +
| TC \ | | | |
+-----\ | | | |
| PMA > PME 1 |...| PME N | > N ifEntry (N=1..32)
+-----/ | | | | ifType: shdsl(169) or vdsl(97)
| PMD/ | | | |
-------------+---+------- -
Figure 2: Use of ifTable and ifMauTable for EFMCu ports
The ifStackTable is indexed by the ifIndex values of the aggregated 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 efmCuAvailableStackTable defined in this MIB, specifies A new table ifAvailableStackTable defined in this MIB, specifies for
for each PCS a list of PMEs, which can possibly be cross-connected to each PCS a list of PMEs, which can possibly be cross-connected to
that PCS, determined by the cross-connect capability of the device. that PCS, determined by the cross-connect capability of the device.
This table, modeled after ifStackTable, is read only, reflecting This table, modeled after ifStackTable, is read only, reflecting
current cross-connect capability, which can be dynamic in some current cross-connect capability, which can be dynamic in some
implementations (e.g. if PMEs are located on a pluggable module and implementations (e.g. if PMEs are located on a pluggable module and
the card is pulled out). Note that PME availability per PCS, the module is pulled out). Note that PME availability per PCS,
described by efmCuAvailableStackTable, can be constrained by other described by ifAvailableStackTable, can be constrained by other
parameters, for example by aggregation capacity of a PCS or by the parameters, for example by aggregation capacity of a PCS or by the
PME in question being already connected to another PCS. So, in order PME in question being already connected to another PCS. So, in order
to ensure that a particular PME can be connected to the PCS, all to ensure that a particular PME can be connected to the PCS, all
respective parameters (e.g. efmCuAvailableStackTable, ifStackTable respective parameters (e.g. ifAvailableStackTable, ifStackTable and
and efmCuPAFCapacity) SHALL be inspected. efmCuPAFCapacity) SHALL be inspected.
The efmCuAvailableStackTable allows to define new entries
*EdNote: Add efmCuInvAvailableStackTable describing which PCS ports *EdNote: Add ifInvAvailableStackTable describing which PCS ports can
can be connected to a particular PME. Possibly move these 2 tables to be connected to a particular PME. Add it to the
a separate MIB to make cross-connect capability available to other ifStackCapabilityGroup conformance statement. *
MIBs for import (changing the prefix of course from 'efmCu' to say
'if'). *
3.1.2 PME Aggregation Function (PAF) 3.1.2 PME Aggregation Function (PAF)
The PME Aggregation Function (PAF) is OPTIONAL and MAY not be The PME Aggregation Function (PAF) is OPTIONAL. Note however that
supported. Note however that the agent is REQUIRED to report on the the agent is REQUIRED to report on the PAF capability for all EFMCu
PAF capability for all EFMCu ports (2Base-TL and 10Pass-TS). ports (2BASE-TL and 10PASS-TS).
*EdNote: Add more info.* *EdNote: Add more info.*
3.1.3 Discovery Operation 3.1.3 Discovery Operation
The EFMCu ports may optionally support discovery operation, whereby
PMEs, during initialization, exchange information about their
respective aggregation groups (PCS). This information can then be
used to detect copper missconnections or for an automatic assignment
of the local PMEs into aggregation groups instead of fixed
pre-configuration.
This MIB allows a Network Management application to control EFM This MIB allows a Network Management application to control EFM
Discovery mechanism and query its results. Note that the Discovery Discovery mechanism and query its results. Note that the Discovery
mechanism can work only if PAF is supported and enabled. 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
efmCuAvailableStackTable defined. The following pseudo-code defines ifAvailableStackTable defined. The following pseudo-code defines an
an example of Discovery and automatic PME assignment for a generic example of Discovery and automatic PME assignment for a generic PAF
PAF enabled multi-PCS EFMCu device, located at Central Office (CO): enabled multi-PCS EFMCu device, located at Central Office (CO) [Note
that automatic PME assignment is only shown here for the purposes of
the example. Fixed PME pre-assignment or manual assignment 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 efmCuAvailableStackTable[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
r = pme[j].RemoteDiscoveryCode; // Get r = pme[j].RemoteDiscoveryCode; // Get
IF ( r == dc AND pcs[i].NumPMEs < pcs[i].PAFCapacity) IF ( r == dc AND pcs[i].NumPMEs < pcs[i].PAFCapacity)
{ // Remote CPE connected via PME[j] is/was a peer for { // Remote CPE connected via PME[j] is/was a peer for
// PCS[i]. Connect this PME to the PCS (there's room) // PCS[i]. Connect this PME to the PCS (there's room)
ADD pme[j] TO ifStackTable[pcs[i]]; ADD pme[j] TO ifStackTable[pcs[i]];
pcs[i].NumPMEs = pcs[i].NumPMEs + 1; pcs[i].NumPMEs = pcs[i].NumPMEs + 1;
// Discover all other currently disconnected PMEs, // Discover all other currently disconnected PMEs,
// attached to the same CPE and connect them to the PCS // attached to the same CPE and connect them to the PCS
// provided there is enough room for more PMEs. // provided there is enough room for more PMEs.
FOREACH pme[k] IN efmCuAvailableStackTable[pcs[i]] and FOREACH pme[k] IN ifAvailableStackTable[pcs[i]] and
NOT IN ifInvStackTable[pme[k]] NOT IN ifInvStackTable[pme[k]]
{ r = pme[k].RemoteDiscoveryCode; // Get { r = pme[k].RemoteDiscoveryCode; // Get
IF ( r == dc AND IF ( r == dc AND
pcs[i].NumPMEs < pcs[i].PAFCapacity) pcs[i].NumPMEs < pcs[i].PAFCapacity)
{ ADD pme[k] TO ifStackTable[pcs[i]]; { ADD pme[k] TO ifStackTable[pcs[i]];
pcs[i].NumPMEs = pcs[i].NumPMEs + 1; pcs[i].NumPMEs = pcs[i].NumPMEs + 1;
} }
} }
} }
// Discovered all PMEs which lead to the same CPE and // Discovered all PMEs which lead to the same CPE and
skipping to change at page 7, line 8 skipping to change at page 8, line 8
and 45.2.3.21). and 45.2.3.21).
Note that PCS port does not have to be operationally 'down' for the Note that PCS port does not have to be operationally 'down' for the
connection to succeed. In fact, a dynamic PME addition (and removal) connection to succeed. In fact, a dynamic PME addition (and removal)
MAY be implemented whith an available PME being initialized first (by MAY be implemented whith an available PME being initialized first (by
setting its ifAdminStatus to 'up') and then added to an operationally setting its ifAdminStatus to 'up') and then added to an operationally
'up' PCS port, by modifying a respective ifStackTable entry. 'up' PCS port, by modifying a respective ifStackTable entry.
It is RECOMMENDED that a removal of the last operationally 'up' PME It is RECOMMENDED that a removal of the last operationally 'up' PME
from an operationally 'up' PCS would be rejected by the from an operationally 'up' PCS would be rejected by the
implementation, as this action would completetly drop the link. implementation, as this action would completely drop the link.
3.1.4 EFMCu ports initialization 3.1.4 EFMCu ports initialization
EFMCu ports being built on top of xDSL technology, require a lengthy EFMCu ports being built on top of xDSL technology, require a lengthy
initialization or 'training' process, before any data can pass. initialization or 'training' process, before any data can pass.
During this initialization both ends of a link (peers) work During this initialization both ends of a link (peers) work
cooperatively to achieve required data rate on a particular copper cooperatively to achieve required data rate on a particular copper
pair. Sometimes, when the copper line is too long or the noise pair. Sometimes, when the copper line is too long or the noise
environment on the line is too high, that 'training' process may fail environment on the line is too high, that 'training' process may fail
to achieve a specific target rate with required characteristics. to achieve a specific target rate with required characteristics.
skipping to change at page 7, line 32 skipping to change at page 8, line 32
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 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
suceed. The PCS is considered operationally 'up' if at least one PME succeed. The PCS is considered operationally 'up' if at least one
aggregated by its PAF is operationally 'up'. When all PMEs connected PME aggregated by its PAF is operationally 'up'. When all PMEs
to the PCS are 'down' the PCS SHALL be considered operationally connected to the PCS are 'down' the PCS SHALL be considered
'lowerLayerDown'. The PCS SHALL be considered operationally operationally 'lowerLayerDown'. The PCS SHALL be considered
'notPresent' if it is not connected to any PME. The PCS/PME operationally 'notPresent' if it is not connected to any PME. The
interface SHALL remain operationally 'down' during initialization. PCS/PME interface SHALL remain operationally 'down' during
initialization.
The efmCuPmeOperStatus defined in this MIB expands PME's ifOperStatus The efmCuPmeOperStatus defined in this MIB expands PME's ifOperStatus
value of 'down' to 'downReady', 'downNotReady' and 'init' values, value of 'down' to 'downReady', 'downNotReady' and 'init' values,
indicating various EFMCu PME specific states. 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 and generic
interface objects from the ifTable of IF-MIB, with all management interface objects from the ifTable of IF-MIB, with all management
skipping to change at page 8, line 16 skipping to change at page 9, line 17
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| 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 | Actual 'net' data rate as seen |
| | across MII | | | across MII |
| 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
G.SHDSL.bis modems, similar to PME(s) comprising a 2BaseTL 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 2BaseTL PME related objects and name consistency (e.g. prefixing the 2BASE-TL PME related
with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided not to objects with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided
reference HDSL2-SHDSL-LINE-MIB objects, but define all the relevant not to reference HDSL2-SHDSL-LINE-MIB objects, but define all the
objects in this MIB. relevant objects in this MIB.
However, if some functionality, not available in this MIB, is However, if some functionality, not available in this MIB, 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
VDSL (DMT) modems, similar to the PME(s) comprising a 10PassTS 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.
However, if some functionality, not available in this MIB, is However, if some functionality, not available in this MIB, 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 MIBs
The implementation of EtherLike-MIB [RFC3635] and MAU-MIB [RFC3636] The implementation of EtherLike-MIB [RFC3635] and MAU-MIB
is REQUIRED for the EFMCu interfaces. As such EFMCu interfaces [I-D.ietf-hubmib-rfc3636bis] is REQUIRED for the EFMCu interfaces.
2Base-TL/10Pass-TS SHALL return an ifType of ethernetCsmacd(6).
Information on the particular flavor of EFMCu that an interface is
running is available from ifSpeed in the IF-MIB [RFC2863], and
ifMauType in the MAU-MIB.
The MAU-MIB shall be augmented to include the following new values Two new values of ifMauType (OBJECT-IDENTITIES of dot3MauType) and
for ifMauType (instances of dot2MauType): corresponding bit definitions of ifMauTypeListBits
(IANAifMauTypeListBits) have been defined in the IANA-MAU-TC-MIB
[I-D.ietf-hubmib-rfc3636bis] for the EFMCu MAUs:
o dot3MauType2BaseTL - voice grade UTP Phy specified in Clause 61 o dot3MauType2BaseTL and b2BaseTL - for 2BASE-TL MAU
and 63
o dot3MauType10PassTS - voice grade UTP Phy specified in Clause 61 o dot3MauType10PassTS and b10PassTS - for 10PASS-TS MAU
and 62
*EdNote: Should we also include -O/-R subtypes?* As an EtherLike interface every EFMCu port (an ifEntry representing a
consolidation of LLC, MAC and PCS (sub)layers) SHALL return an ifType
of ethernetCsmacd(6). While most of the MAU characteristics is not
applicable to the EFMCu ports (no auto-negotiation, media available,
false carriers or jabber), they SHALL return an appropriate ifMauType
(dot3MauType2BaseTL or dot3mauType10PassTS) in order to direct the
management software to look in the EFM-CU-MIB for the desired
information. For example the information on the particular EFMCu
flavor that an EFMCu port is running is available from
efmCuOperSubType, defined in this MIB module.
Since EFMCu PMEs are not EtherLike interfaces, they cannot be
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 are split into 2
groups: 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 efmCuAvailableStackTable is defined at the same In addition the ifAvailableStackTable is defined at the same level.
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 2BaseTL and groups, which define configuration profiles specific to 2BASE-TL and
10PassTS PMEs respectively as well as PME specific status 10PASS-TS PMEs respectively as well as PME specific status
information. information.
4.2 Configuration Profiles 4.2 Configuration 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 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 that can be shared by multiple PME ports using the same
configuration. configuration.
The configuration profiles are defined in efmCuPme2BConfProfileTable The configuration profiles are defined in efmCuPme2BConfProfileTable
and efmCu10PConfProfileTable for 2Base-TL and 10Pass-TS PMEs and efmCu10PConfProfileTable for 2BASE-TL and 10PASS-TS PMEs
respectively. There are 12 predefined standard profiles for 2Base-TL respectively. There are 12 predefined standard profiles for 2BASE-TL
and 22 standard profiles for 10Pass-TS, defined in 802.3ah and and 22 standard profiles for 10PASS-TS, defined in 802.3ah and
dedicated for rapid provisioning of EFMCu PHYs in most scenarios. An dedicated for rapid provisioning of EFMCu PHYs in most scenarios. An
ability to define new configuration profiles is also provided to ability to define new configuration profiles is also provided to
allow for EFMCu deployment tailored to specific copper environment allow for EFMCu deployment tailored to specific copper environment
and spectral regulations. and spectral regulations.
A specific configuration profile is assigned to a specific PME via A specific configuration profile is assigned to a specific PME via
efmCuPmeAdminProfile object. Alternatively, by assigning a non-empty efmCuPmeAdminProfile object. Alternatively, by assigning a non-empty
profile to a PCS port via efmCuAdminProfile, all PMEs connected to profile to a PCS port via efmCuAdminProfile, all PMEs connected to
the PCS port are made to share that profile, which comes handy during the PCS port are made to share that profile, which comes in handy
configuration of aggregated ports. during configuration of aggregated ports.
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 do not have
direct counterparts in Clause 30 and instead refer to Clause 45 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 is approved. I guess this should be done via a maintanence
request. * request. *
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| IEEE 802.3 Managed Object | Corresponding SNMP Object | | IEEE 802.3 Managed Object | Corresponding SNMP Object |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| oPAF - PME 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 | |
| (Optional) | | | (Optional) | |
| aPAFAdminState | efmCuPAFAdminState | | aPAFAdminState | efmCuPAFAdminState |
| aPAFID | ifIndex (IF-MIB) |
| aLocalPAFCapacity | efmCuPAFCapacity | | aLocalPAFCapacity | efmCuPAFCapacity |
| aLocalPMEAvailable | efmCuAvailableStackTable | | aLocalPMEAvailable | ifAvailableStackTable |
| aLocalPMEAggregate | ifStackTable (IF-MIB) | | aLocalPMEAggregate | ifStackTable (IF-MIB) |
| aRemotePAFSupported | efmCuRemotePAFSupported | | aRemotePAFSupported | efmCuRemotePAFSupported |
| aRemotePAFCapacity | efmCuRemotePAFCapacity | | aRemotePAFCapacity | efmCuRemotePAFCapacity |
| aRemotePMEAvailable | |
| aRemotePMEAggregate | | | aRemotePMEAggregate | |
| oPME - 10P/2B Package | | | oPME - 10P/2B Package | |
| (Mandatory) | | | (Mandatory) | |
| aPMEID | ifIndex (IF-MIB) | | aPMEID | ifIndex (IF-MIB) |
| aPMEAdminState | ifAdminState (IF-MIB) | | aPMEAdminState | ifAdminState (IF-MIB) |
| aPMEStatus | efmCuPmeStatus | | aPMEStatus | efmCuPmeStatus |
| aPMESNRMgn | efmCuPmeSnrMgn | | aPMESNRMgn | efmCuPmeSnrMgn |
| aTCCodingViolations | efmCuPmeTCCodingErrors | | aTCCodingViolations | efmCuPmeTCCodingErrors |
| aProfileSelect | efmCuAdminProfile, | | aProfileSelect | efmCuAdminProfile, |
| | efmCuPmeAdminProfile | | | efmCuPmeAdminProfile |
skipping to change at page 12, line 7 skipping to change at page 13, line 15
5. Definitions 5. Definitions
EFM-CU-MIB DEFINITIONS ::= BEGIN EFM-CU-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32,
Unsigned32, Counter32, mib-2 Unsigned32, Counter32, mib-2
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
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]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580]
; ;
efmCuMIB MODULE-IDENTITY efmCuMIB MODULE-IDENTITY
LAST-UPDATED "200407150000Z" -- July 15, 2004 LAST-UPDATED "200410240000Z" -- October 24, 2004
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 13, line 15 skipping to change at page 14, line 22
information exchange between systems - Local and information exchange between systems - Local and
metropolitan area networks - Specific requirements - metropolitan area networks - 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 - Media Access Control Parameters, Physical
Layers and Management Parameters for subscriber access Layers and Management Parameters for subscriber access
networks', 19 April 2003. networks', 19 April 2003.
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', and Clause 45, type 2BASE-TL', Clause 30, 'Management', Clause 45,
'Management Data Input/Output (MDIO) Interface'. 'Management Data Input/Output (MDIO) Interface', Annex 62A,
'PMD profiles for 10PASS-TS' and Annex 63A, 'PMD profiles for
2BASE-TL'.
Naming Conventions: Naming Conventions:
Atn - Attenuation Atn - Attenuation
CO - Central Office CO - Central Office
CPE - Customer Premises Equipment CPE - Customer Premises Equipment
EFM - Ethernet in the First Mile EFM - Ethernet in the First Mile
EFMCu - EFM Copper EFMCu - EFM Copper
MDIO - Management Data Input/Output MDIO - Management Data Input/Output
Mgn - Margin Mgn - Margin
PAF - PME Aggregation Function PAF - PME Aggregation Function
skipping to change at page 13, line 41 skipping to change at page 14, line 50
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 "200407150000Z" -- July 15, 2004 REVISION "200410240000Z" -- October 24, 2004
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
::= { mib-2 YYY } ::= { mib-2 YYY }
-- EdNote: Replace YYY with a real OID once it is -- EdNote: Replace YYY with a real OID once it is
-- allocated & remove this note. -- allocated & remove this note.
-- 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
skipping to change at page 15, line 17 skipping to change at page 16, line 26
or when no common profile(s) need to be referenced and or when no common profile(s) need to be referenced and
sub-interface profile shall take precedence." sub-interface profile shall take precedence."
SYNTAX OCTET STRING (SIZE(0..6)) SYNTAX OCTET STRING (SIZE(0..6))
-- 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
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification indicates that EFMCu port's data rate "This notification indicates that EFMCu port's data rate
reached or droped below a Low Bandwidth Threshold reached or dropped below a Low Bandwidth Threshold
(i.e. bandwidth degradation happening in case of PAF when one (i.e. bandwidth degradation happening in case of PAF when one
or more PMEs drop)." or more PMEs drop)."
-- EdNote: add throttling limitations here -- EdNote: add throttling limitations here
::= { efmCuPortNotifications 1 } ::= { efmCuPortNotifications 1 }
-- PCS Port group -- PCS Port group
efmCuPortConfTable OBJECT-TYPE efmCuPortConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPortConfEntry SYNTAX SEQUENCE OF EfmCuPortConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table for Configuration of EFMCu 2BaseTL/10PassTS (PCS) "Table for Configuration 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"
::= { efmCuPort 1 } ::= { efmCuPort 1 }
efmCuPortConfEntry OBJECT-TYPE efmCuPortConfEntry OBJECT-TYPE
SYNTAX EfmCuPortConfEntry SYNTAX EfmCuPortConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the EFMCu Port Configuration table. "An entry in the EFMCu Port Configuration table.
skipping to change at page 16, line 38 skipping to change at page 17, line 47
PCS. No more than a single PME can be assigned to this PCS in PCS. No more than a single PME can be assigned to this PCS in
this case. this case.
When 'enabled', PAF will be performed by the PCS when the link When 'enabled', PAF will be performed by the PCS when the link
is Up, even on a single attached PME, if PAF is supported. is Up, even on a single attached PME, if PAF is supported.
PCS ports incapable of supporting PAF SHALL return a value of PCS ports incapable of supporting PAF SHALL return a value of
'disabled'. Attempts to 'enable' such ports SHALL be ignored. 'disabled'. Attempts to 'enable' such ports SHALL be ignored.
PAF 'enabled' port with multiple PMEs assigned cannot be PAF 'enabled' port with multiple PMEs assigned cannot be
'disabled'. Attempts to 'disable' such port SHALL be rejected, 'disabled'. Attempts to 'disable' such port SHALL be rejected,
untill at most one PME is left assigned. until at most one PME is left assigned.
Changing PAFAdminState is a traffic disruptive operation and Changing PAFAdminState is a traffic disruptive operation and
as such SHALL be done when the link is Down. Attempts to as such SHALL be done when the link is Down. Attempts to
change this object SHALL be 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
skipping to change at page 19, line 5 skipping to change at page 20, line 14
shall allow lossless transmission of full-duplex 10Mbps shall allow lossless transmission of full-duplex 10Mbps
Ethernet frame stream with minimal inter-frame gap). Ethernet frame stream with minimal inter-frame gap).
The value is limited above by 100Mbps as this is the max The value is limited above by 100Mbps as this is the max
burst rate across MII for EFMCu ports. burst rate across MII for EFMCu ports.
The value between 1 and 100000 indicates that the total data The value between 1 and 100000 indicates that the total data
rate (ifSpeed) of the EFMCu port after initialization should rate (ifSpeed) of the EFMCu port after initialization should
be equal to the target data rate or less, if the target data be equal to the target data rate or less, if the target data
rate cannot be achieved under spectral restrictions specified rate cannot be achieved under spectral restrictions specified
by efmCuAdminProfile/efmCiPmeAdminProfile and with desired SNR by efmCuAdminProfile/efmCuPmeAdminProfile and with desired SNR
margin. In case the copper environment allows to achieve margin. In case the copper environment allows to achieve
higher total data rate than specified by the target, the higher total data rate than specified by the target, the
excess capability SHALL be converted to additional SNR margin excess capability SHALL be converted to additional SNR margin
and spread evenly across all active PMEs assigned to the (PCS) and spread evenly across all active PMEs assigned to the (PCS)
port. port.
The value of 999999 means that the target data rate is not The value of 999999 means that the target data rate is not
fixed and should be set to the maximum attainable rate during fixed and should be set to the maximum attainable rate during
initialization (Best Effort), under specified spectral initialization (Best Effort), under specified spectral
restrictions and with desired SNR Margin. restrictions and with desired SNR Margin.
skipping to change at page 19, line 40 skipping to change at page 20, line 49
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
is the difference between the desired SNR and the actual SNR). is the difference between the desired SNR and the actual SNR).
Note that 802.3ah recommends using default Target SNR Margin Note that 802.3ah recommends using default Target SNR Margin
of 5dB for 2BaseTL ports and 6dB for 10PassTS ports in order of 5dB for 2BASE-TL ports and 6dB for 10PASS-TS ports in order
to achieve mean Bit Error Rate (BER) of 10^-7 at the PMA to achieve mean Bit Error Rate (BER) of 10^-7 at the PMA
service interface. service interface.
This object is read-write for the -O subtype EFMCu ports This object is read-write for the -O subtype EFMCu ports
(2BaseTL-O/10PassTS-O) and not available for the -R subtypes. (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
Changing of the Target SNR Margin MUST be performed when the Changing of the Target SNR Margin MUST be performed when the
link is Down. Attempts to change this object MUST be rejected link is Down. Attempts to change this object MUST be rejected
with the error inconsistentValue, if the link is Up or with the error inconsistentValue, if the link is Up or
Initializing. Initializing.
skipping to change at page 20, line 48 skipping to change at page 22, line 8
Value of truth(1) indicates that efmCuLowBandwidth Value of truth(1) indicates that efmCuLowBandwidth
notification is enabled. Value of false(0) indicates the it is notification is enabled. Value of false(0) indicates the it is
disabled." disabled."
::= { 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 2BaseTL/10PassTS (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"
::= { efmCuPort 2 } ::= { efmCuPort 2 }
efmCuPortCapabilityEntry OBJECT-TYPE efmCuPortCapabilityEntry OBJECT-TYPE
SYNTAX EfmCuPortCapabilityEntry SYNTAX EfmCuPortCapabilityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"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 }
skipping to change at page 22, line 24 skipping to change at page 23, line 32
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 }
efmCuPAFCapacity OBJECT-TYPE efmCuPAFCapacity OBJECT-TYPE
SYNTAX Unsigned32 (1..32) SYNTAX Unsigned32 (1..32)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of PMEs that can be aggregated by the local PAF. "Number of PMEs that can be aggregated by the local PAF.
The number of PMEs currently assigned to a particluar The number of PMEs currently assigned to a particular
EFMCu port (efmCuNumPMEs) is never greater than EFMCu port (efmCuNumPMEs) is never greater than
efmCuPAFCapacity. efmCuPAFCapacity.
This object maps to the Clause 30 attribute This object maps to the Clause 30 attribute
aLocalPAFCapacity." aLocalPAFCapacity."
REFERENCE REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.6" "[802.3ah] 61.2.2, 30.11.1.1.6"
::= { efmCuPortCapabilityEntry 3 } ::= { efmCuPortCapabilityEntry 3 }
efmCuPeerPAFCapacity OBJECT-TYPE efmCuPeerPAFCapacity OBJECT-TYPE
skipping to change at page 23, line 9 skipping to change at page 24, line 17
REFERENCE REFERENCE
"[802.3ah] 61.2.2, 30.11.1.1.10" "[802.3ah] 61.2.2, 30.11.1.1.10"
::= { efmCuPortCapabilityEntry 4 } ::= { efmCuPortCapabilityEntry 4 }
efmCuPortStatusTable OBJECT-TYPE efmCuPortStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPortStatusEntry SYNTAX SEQUENCE OF EfmCuPortStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provides overall status information of EFMCu "This table provides overall status information of EFMCu
2BaseTL/10PassTS ports. This table contains live data from 2BASE-TL/10PASS-TS ports. This table contains live data from
the equipment. As such, it is NOT persistent." the equipment. As such, it is NOT persistent."
::= { efmCuPort 3 } ::= { efmCuPort 3 }
efmCuPortStatusEntry OBJECT-TYPE efmCuPortStatusEntry OBJECT-TYPE
SYNTAX EfmCuPortStatusEntry SYNTAX EfmCuPortStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the EFMCu Port Status table. "An entry in the EFMCu Port Status table.
Each entry represents an EFMCu port indexed by the ifIndex. Each entry represents an EFMCu port indexed by the ifIndex.
skipping to change at page 24, line 4 skipping to change at page 25, line 12
noPeer(0), -- peer Phy cannot be reached noPeer(0), -- peer Phy cannot be reached
pmeSubTypeMismatch(1), -- Assigned PMEs Sub-type Mismatch pmeSubTypeMismatch(1), -- Assigned PMEs Sub-type Mismatch
lowBandwidth(2) -- Low Bandwidth lowBandwidth(2) -- Low Bandwidth
} }
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.
pmeSubTypeMismatch - PMEs in the aggregation group are not pmeSubTypeMismatch - local PMEs in the aggregation group
of the same sub-type, e.g. PMEs with are not of the same sub-type, e.g.
-O and -R subtype some PMEs in the local device are -O
while others are -R subtype.
lowBandwidth - ifSpeed of the port reached or droped lowBandwidth - ifSpeed of the port reached or droped
below efmCuThreshLowBandwidth below efmCuThreshLowBandwidth
This object is intended to supplement ifOperStatus object This object is intended to supplement ifOperStatus object
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"
skipping to change at page 28, line 45 skipping to change at page 30, line 5
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."
-- EdNote: add throttling limitations here -- EdNote: add throttling limitations here
::= { 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 -- EdNote: add throttling limitations here
::= { 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
skipping to change at page 30, line 4 skipping to change at page 31, line 11
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 -- EdNote: add throttling limitations here
::= { 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
2BaseTL/10PassTS PME ports (modems). Configuration of aspects 2BASE-TL/10PASS-TS PME ports (modems). Configuration of
specific to 2BaseTL or 10PassTS PME types is represented in aspects specific to 2BASE-TL or 10PASS-TS PME types is
efmCuPme2BConfTable and efmCuPme10PConfTable respectively. represented in efmCuPme2BConfTable and efmCuPme10PConfTable
respectively.
Entries in this table MUST be maintained in a persistent Entries in this table MUST be maintained in a persistent
manner." manner."
::= { efmCuPme 1 } ::= { efmCuPme 1 }
efmCuPmeConfEntry OBJECT-TYPE efmCuPmeConfEntry OBJECT-TYPE
SYNTAX EfmCuPmeConfEntry SYNTAX EfmCuPmeConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 36, line 4 skipping to change at page 37, line 12
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 truth(1) indicates that efmCuPmeProtocolInitFailure
notification is enabled. Value of false(0) indicates the it is notification is enabled. Value of false(0) indicates the it is
disabled." 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
2BaseTL/10PassTS PME ports (modems). Configuration of aspects 2BASE-TL/10PASS-TS PME ports (modems). Configuration of
specific to 2BaseTL or 10PassTS PME types is represented in aspects specific to 2BASE-TL or 10PASS-TS PME types is
efmCuPme2BConfTable and efmCuPme10PConfTable respectively. represented in efmCuPme2BConfTable and efmCuPme10PConfTable
respectively.
Entries in this table MUST be maintained in a persistent Entries in this table MUST be maintained in a persistent
manner." manner."
::= { efmCuPme 2 } ::= { efmCuPme 2 }
efmCuPmeCapabilityEntry OBJECT-TYPE efmCuPmeCapabilityEntry OBJECT-TYPE
SYNTAX EfmCuPmeCapabilityEntry SYNTAX EfmCuPmeCapabilityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the EFMCu PME Configuration table. "An entry in the EFMCu PME Capability 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 }
::= { efmCuPmeCapabilityTable 1 } ::= { efmCuPmeCapabilityTable 1 }
EfmCuPmeCapabilityEntry ::= EfmCuPmeCapabilityEntry ::=
SEQUENCE { SEQUENCE {
efmCuPmeSubTypesSupported BITS efmCuPmeSubTypesSupported BITS
skipping to change at page 37, line 4 skipping to change at page 38, line 15
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"PME supported sub-types. This is a bitmap of possible "PME supported sub-types. This is a bitmap of possible
sub-types. The various bit positions are: sub-types. The various bit positions are:
ieee2BaseTLO - PME is capable of operating as 2BaseTL-O ieee2BaseTLO - PME is capable of operating as 2BaseTL-O
ieee2BaseTLR - PME is capable of operating as 2BaseTL-R ieee2BaseTLR - PME is capable of operating as 2BaseTL-R
ieee10PassTSO - PME is capable of operating as 10PassTS-O ieee10PassTSO - PME is capable of operating as 10PassTS-O
ieee10PassTSR - PME is capable of operating as 10PassTS-R ieee10PassTSR - PME is capable of operating as 10PassTS-R
An actual mode of operation is determined by
efmCuPmeAdminSubType. An desired mode of operation is determined by
efmCuPmeAdminSubType, while efmCuPmeOperSubType relects the
current operating mode.
If a Clause 45 MDIO Interface to the PCS is present, then this If a Clause 45 MDIO Interface to the PCS is present, then this
object combines the 10PASS-TS capable and 2BASE-TL capable object combines the 10PASS-TS capable and 2BASE-TL capable
bits in the 10P/2B PMA/PMD speed ability register and the bits in the 10P/2B PMA/PMD speed ability register and the
CO supported and CPE supported bits in the 10P/2B PMA/PMD CO supported and CPE supported bits in the 10P/2B PMA/PMD
status register" status register"
REFERENCE REFERENCE
"[802.3ah] 61.1, 45.2.1.4.1, 45.2.1.4.2, 45.2.1.12.2, "[802.3ah] 61.1, 45.2.1.4.1, 45.2.1.4.2, 45.2.1.12.2,
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 "Table for Configuration of common aspects for EFMCu
2BaseTL/10PassTS PME ports (modems). Configuration of aspects 2BASE-TL/10PASS-TS PME ports (modems). Configuration of
specific to 2BaseTL or 10PassTS PME types is represented in aspects specific to 2BASE-TL or 10PASS-TS PME types is
efmCuPme2BConfTable and efmCuPme10PConfTable respectively. represented in efmCuPme2BConfTable and efmCuPme10PConfTable
respectively.
Entries in this table MUST be maintained in a persistent Entries in this table MUST be maintained in a persistent
manner." manner."
::= { efmCuPme 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 Configuration 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 31 skipping to change at page 40, line 45
diagnostic or self-test fault diagnostic or self-test fault
has been detected. has been detected.
configInitFailure - Configuration initialization failure, configInitFailure - Configuration initialization failure,
due to inability of the PME link to due to inability of the PME link to
support configuration profile, support configuration profile,
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 2BaseTL/10PassTS 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.
This object partially maps to the Clause 30 attribute This object partially maps to the Clause 30 attribute
aPMEStatus. aPMEStatus.
If a Clause 45 MDIO Interface to the PME is present, then this If a Clause 45 MDIO Interface to the PME is present, then this
object consolidates information from various PMA/PMD object consolidates information from various PMA/PMD
registers, namely: Fault bit in PMA/PMD status 1 register, registers, namely: Fault bit in PMA/PMD status 1 register,
skipping to change at page 42, line 38 skipping to change at page 43, line 51
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.
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 }
-- 2BaseTL specific PME group -- 2BASE-TL specific PME group
efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 } efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 }
efmCuPme2BConfProfileTable OBJECT-TYPE efmCuPme2BConfProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme2BConfProfileEntry SYNTAX SEQUENCE OF EfmCuPme2BConfProfileEntry
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
2BaseTL PMEs. 2BASE-TL PMEs.
First 12 entries in this table SHALL always be defined as First 12 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 5696 13.5 Annex A 32-TCPAM
2 3072 13.5 Annex A 32-TCPAM 2 3072 13.5 Annex A 32-TCPAM
3 2048 13.5 Annex A 16-TCPAM 3 2048 13.5 Annex A 16-TCPAM
4 1024 13.5 Annex A 16-TCPAM 4 1024 13.5 Annex A 16-TCPAM
skipping to change at page 43, line 36 skipping to change at page 44, line 48
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 efmCuPme2BConfProfileEntry OBJECT-TYPE
SYNTAX EfmCuPme2BConfProfileEntry SYNTAX EfmCuPme2BConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry corresponds to a single 2BaseTL PME configuration "Each entry corresponds to a single 2BASE-TL PME configuration
profile. Each profile contains a set of configuration profile. Each profile contains a set of configuration
parameters, which are applied to all 2BaseTL-O PMEs parameters, which are applied to all 2BaseTL-O PMEs
assigned to the 2BaseTL (PCS) port, referencing that profile assigned to the 2BASE-TL (PCS) port, referencing that profile
via efmCuAdminProfile object or, if efmCuAdminProfile is zero, via efmCuAdminProfile object or, if efmCuAdminProfile is zero,
all 2BaseTL-O PMEs, referencing that profile via all 2BaseTL-O PMEs, referencing that profile via
efmCuPmeAdminProfile. efmCuPmeAdminProfile.
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 (first 12) MUST not be removed."
INDEX { efmCuPme2BProfileIndex } INDEX { efmCuPme2BProfileIndex }
skipping to change at page 44, line 20 skipping to change at page 45, line 32
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
"2BaseTL 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 } ::= { efmCuPme2BConfProfileEntry 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 2BaseTL 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 } ::= { efmCuPme2BConfProfileEntry 2 }
efmCuPme2BRegion OBJECT-TYPE efmCuPme2BRegion OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
regionA(1), -- Annex A regionA(1), -- Annex A
regionB(2), -- Annex B regionB(2), -- Annex B
regionC(3) -- Annex C regionC(3) -- Annex C
} }
skipping to change at page 45, line 24 skipping to change at page 46, line 36
REFERENCE REFERENCE
"[802.3ah] 45.2.1.42" "[802.3ah] 45.2.1.42"
::= { efmCuPme2BConfProfileEntry 3 } ::= { efmCuPme2BConfProfileEntry 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 2BaseTL PME Data Rate. "Desired 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 means that data rate is not fixed but is
adaptive and should be set to the maximum attainable rate adaptive and should be set to the maximum attainable rate
during line probing. during line probing.
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."
REFERENCE REFERENCE
skipping to change at page 46, line 18 skipping to change at page 47, line 30
::= { efmCuPme2BConfProfileEntry 5 } ::= { efmCuPme2BConfProfileEntry 5 }
efmCuPme2BConstellation OBJECT-TYPE efmCuPme2BConstellation OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
tcpam16(1), -- 16-TCPAM tcpam16(1), -- 16-TCPAM
tcpam32(2) -- 32-TCPAM tcpam32(2) -- 32-TCPAM
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Desired TCPAM Constellation of the 2BaseTL PME. The possible "Desired TCPAM Constellation of the 2BASE-TL PME. The possible
values are: values are:
tcpam16(1) - 16-TCPAM tcpam16(1) - 16-TCPAM
tcpam32(2) - 32-TCPAM tcpam32(2) - 32-TCPAM
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 } ::= { efmCuPme2BConfProfileEntry 6 }
skipping to change at page 46, line 43 skipping to change at page 48, line 7
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 efmCuPme2BConfProfileTable 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 } ::= { efmCuPme2BConfProfileEntry 7 }
-- 10PassTS specific PME group -- 10PASS-TS specific PME group
efmCuPme10P OBJECT IDENTIFIER ::= { efmCuPme 6 } efmCuPme10P OBJECT IDENTIFIER ::= { efmCuPme 6 }
efmCuPme10PConfProfileTable OBJECT-TYPE efmCuPme10PConfProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme10PConfProfileEntry SYNTAX SEQUENCE OF EfmCuPme10PConfProfileEntry
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.
skipping to change at page 47, line 51 skipping to change at page 49, line 15
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 efmCuPme10PConfProfileEntry OBJECT-TYPE
SYNTAX EfmCuPme10PConfProfileEntry SYNTAX EfmCuPme10PConfProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry corresponds to a single 10PassTS PME configuration "Each entry corresponds to a single 10PASS-TS PME
profile. Each profile contains a set of configuration configuration profile. Each profile contains a set of
parameters, which are applied to all PMEs assigned to the configuration parameters, which are applied to all PMEs
10PassTS (PCS) port, referencing that profile via assigned to the 10PASS-TS (PCS) port, referencing that profile
efmCuAdminProfile object, or, if efmCuAdminProfile is zero, via efmCuAdminProfile object, or, if efmCuAdminProfile is
to all PMEs referencing that profile via efmCuPmeAdminProfile. zero, to all PMEs referencing that profile via
efmCuPmeAdminProfile.
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 (first 22) MUST not be removed."
INDEX { efmCuPme10PProfileIndex } INDEX { efmCuPme10PProfileIndex }
::= { efmCuPme10PConfProfileTable 1 } ::= { efmCuPme10PConfProfileTable 1 }
EfmCuPme10PConfProfileEntry ::= EfmCuPme10PConfProfileEntry ::=
SEQUENCE { SEQUENCE {
skipping to change at page 48, line 34 skipping to change at page 49, line 47
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
"10PassTS 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 } ::= { efmCuPme10PConfProfileEntry 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 10PassTS 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 } ::= { efmCuPme10PConfProfileEntry 2 }
efmCuPme10PBandplanPSDMskProfile OBJECT-TYPE efmCuPme10PBandplanPSDMskProfile OBJECT-TYPE
SYNTAX INTEGER {-- PSD Mask Bands Bandplan SYNTAX INTEGER {-- 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
profile2(2), -- T1.424/T-U P1 FTTEx.M1 profile2(2), -- T1.424/T-U P1 FTTEx.M1
profile3(3), -- T1.424/T-U P1 FTTCab.M2 profile3(3), -- T1.424/T-U P1 FTTCab.M2
profile4(4), -- T1.424/T-U P1 FTTEx.M2 profile4(4), -- T1.424/T-U P1 FTTEx.M2
skipping to change at page 49, line 37 skipping to change at page 50, line 49
profile24(24), -- TS1 101 270-1 Pcab.M2 profile24(24), -- TS1 101 270-1 Pcab.M2
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)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"10PassTS 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
profile2(2) - T1.424/T-U P1 FTTEx.M1 profile2(2) - T1.424/T-U P1 FTTEx.M1
profile3(3) - T1.424/T-U P1 FTTCab.M2 profile3(3) - T1.424/T-U P1 FTTCab.M2
profile4(4) - T1.424/T-U P1 FTTEx.M2 profile4(4) - T1.424/T-U P1 FTTEx.M2
profile5(5) - T1.424/T-U P1 FTTCab.M1 D/D/U/D/U profile5(5) - T1.424/T-U P1 FTTCab.M1 D/D/U/D/U
profile6(6) - T1.424/T-U P1 FTTEx.M1 profile6(6) - T1.424/T-U P1 FTTEx.M1
skipping to change at page 50, line 45 skipping to change at page 52, line 9
profile4(4), -- T1.424/T-U Noise F M2 profile4(4), -- T1.424/T-U Noise F M2
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
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"10PassTS 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
profile4(4) - T1.424/T-U Noise F M2 profile4(4) - T1.424/T-U Noise F M2
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
skipping to change at page 51, line 35 skipping to change at page 52, line 47
profile6(6), -- - 15-1 - 3.500 4.000 profile6(6), -- - 15-1 - 3.500 4.000
profile7(7), -- F-5 #04 - - 3.747 3.754 profile7(7), -- F-5 #04 - - 3.747 3.754
profile8(8), -- F-5 #05 - - 3.791 3.805 profile8(8), -- F-5 #05 - - 3.791 3.805
profile9(9), -- 6-2 - 17 7.000 7.100 profile9(9), -- 6-2 - 17 7.000 7.100
profile10(10),-- F-5 #06 15-1 - 7.000 7.300 profile10(10),-- F-5 #06 15-1 - 7.000 7.300
profile11(11) -- 6-2 15-1 1 10.100 10.150 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
"10PassTS 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)
--------------+---------+----------+-----------+------+----- --------------+---------+----------+-----------+------+-----
profile0(0) - no profile profile0(0) - no profile
profile1(1) - F-5 #01 - - 1.810 1.825 profile1(1) - F-5 #01 - - 1.810 1.825
profile2(2) - 6-2 15-1 17 1.810 2.000 profile2(2) - 6-2 15-1 17 1.810 2.000
profile3(3) - F-5 #02 - - 1.907 1.912 profile3(3) - F-5 #02 - - 1.907 1.912
profile4(4) - F-5 #03 - - 3.500 3.575 profile4(4) - F-5 #03 - - 3.500 3.575
skipping to change at page 52, line 31 skipping to change at page 53, line 43
profile20(20), -- 10 profile20(20), -- 10
profile25(25), -- 12.5 profile25(25), -- 12.5
profile30(30), -- 15 profile30(30), -- 15
profile50(50), -- 25 profile50(50), -- 25
profile70(70), -- 35 profile70(70), -- 35
profile100(100) -- 50 profile100(100) -- 50
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"10PassTS 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
profile25(25) - 12.5 Mbps profile25(25) - 12.5 Mbps
profile30(30) - 15 Mbps profile30(30) - 15 Mbps
profile50(50) - 25 Mbps profile50(50) - 25 Mbps
profile70(70) - 35 Mbps profile70(70) - 35 Mbps
profile100(100) - 50 Mbps profile100(100) - 50 Mbps
skipping to change at page 53, line 24 skipping to change at page 54, line 36
profile30(30), -- 15 profile30(30), -- 15
profile50(50), -- 25 profile50(50), -- 25
profile70(70), -- 35 profile70(70), -- 35
profile100(100), -- 50 profile100(100), -- 50
profile140(140), -- 70 profile140(140), -- 70
profile200(200) -- 100 profile200(200) -- 100
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"10PassTS 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
profile25(25) - 12.5 Mbps profile25(25) - 12.5 Mbps
profile30(30) - 15 Mbps profile30(30) - 15 Mbps
profile50(50) - 25 Mbps profile50(50) - 25 Mbps
profile70(70) - 35 Mbps profile70(70) - 35 Mbps
profile100(100) - 50 Mbps profile100(100) - 50 Mbps
skipping to change at page 54, line 20 skipping to change at page 55, line 32
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 } ::= { efmCuPme10PConfProfileEntry 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 10PassTS PMEs (modems)." "Table reflecting status of EFMCu 10PASS-TS PMEs (modems)."
::= { efmCuPme10P 2 } ::= { efmCuPme10P 2 }
efmCuPme10PStatusEntry OBJECT-TYPE efmCuPme10PStatusEntry OBJECT-TYPE
SYNTAX EfmCuPme10PStatusEntry SYNTAX EfmCuPme10PStatusEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the EFMCu 10PassTS PME Status table." "An entry in the EFMCu 10PASS-TS PME Status table."
AUGMENTS { efmCuPmeStatusEntry } AUGMENTS { efmCuPmeStatusEntry }
::= { efmCuPme10PStatusTable 1 } ::= { efmCuPme10PStatusTable 1 }
EfmCuPme10PStatusEntry ::= EfmCuPme10PStatusEntry ::=
SEQUENCE { SEQUENCE {
efmCuPme10PElectricalLength Integer32, efmCuPme10PElectricalLength Integer32,
efmCuPme10PFECCorrectedBlocks Counter32, efmCuPme10PFECCorrectedBlocks Counter32,
efmCuPme10PFECUncorrectedBlocks Counter32 efmCuPme10PFECUncorrectedBlocks Counter32
-- EdNote: To be continued -- EdNote: To be continued
} }
skipping to change at page 54, line 39 skipping to change at page 56, line 4
AUGMENTS { efmCuPmeStatusEntry } AUGMENTS { efmCuPmeStatusEntry }
::= { efmCuPme10PStatusTable 1 } ::= { efmCuPme10PStatusTable 1 }
EfmCuPme10PStatusEntry ::= EfmCuPme10PStatusEntry ::=
SEQUENCE { SEQUENCE {
efmCuPme10PElectricalLength Integer32, efmCuPme10PElectricalLength Integer32,
efmCuPme10PFECCorrectedBlocks Counter32, efmCuPme10PFECCorrectedBlocks Counter32,
efmCuPme10PFECUncorrectedBlocks Counter32 efmCuPme10PFECUncorrectedBlocks Counter32
-- EdNote: To be continued -- EdNote: To be continued
} }
efmCuPme10PElectricalLength OBJECT-TYPE efmCuPme10PElectricalLength OBJECT-TYPE
SYNTAX Integer32(0..8192|65535) SYNTAX Integer32(0..8192|65535)
UNITS "m" UNITS "m"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Electrical Length in meters as perceived by the 10PassTS PME "Electrical Length in meters as perceived by the 10PASS-TS PME
after the link is established. after the link is established.
The value of 65535 is returned if the link is Down or The value of 65535 is returned if the link is Down or
Initializing or the PME is unable to estimate the Electrical Initializing or the PME is unable to estimate the Electrical
Length. Length.
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 10P Electrical Length register" object maps to the 10P Electrical Length register"
REFERENCE REFERENCE
"[802.3ah] 45.2.1.21" "[802.3ah] 45.2.1.21"
::= { efmCuPme10PStatusEntry 1 } ::= { efmCuPme10PStatusEntry 1 }
efmCuPme10PFECCorrectedBlocks OBJECT-TYPE efmCuPme10PFECCorrectedBlocks OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of received and corrected FEC codewords in 10Pass-TS "A count of received and corrected FEC codewords in 10PASS-TS
PME. PME.
This object maps to aPMEFECCorrectedBlocks attribute in This object maps to aPMEFECCorrectedBlocks attribute in
clause 30. clause 30.
If a Clause 45 MDIO Interface to the PMA/PMD is present, If a Clause 45 MDIO Interface to the PMA/PMD is present,
then this object maps to the 10P FEC correctable errors then this object maps to the 10P FEC correctable errors
register" register"
REFERENCE REFERENCE
"[802.3ah] 45.2.1.22" "[802.3ah] 45.2.1.22"
::= { efmCuPme10PStatusEntry 2 } ::= { efmCuPme10PStatusEntry 2 }
efmCuPme10PFECUncorrectedBlocks OBJECT-TYPE efmCuPme10PFECUncorrectedBlocks OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of received FEC codewords in 10Pass-TS PME, which are "A count of received FEC codewords in 10PASS-TS PME, which are
uncorrectable. uncorrectable.
This object maps to aPMEFECUncorrectableBlocks attribute in This object maps to aPMEFECUncorrectableBlocks attribute in
clause 30. clause 30.
If a Clause 45 MDIO Interface to the PMA/PMD is present, If a Clause 45 MDIO Interface to the PMA/PMD is present,
then this object maps to the 10P FEC uncorrectable errors then this object maps to the 10P FEC uncorrectable errors
register" register"
REFERENCE REFERENCE
"[802.3ah] 45.2.1.23" "[802.3ah] 45.2.1.23"
::= { efmCuPme10PStatusEntry 3 } ::= { efmCuPme10PStatusEntry 3 }
-- efmCuAvailableStackTable for use in Discovery -- ifAvailableStackTable for use in Discovery
efmCuAvailableStackTable OBJECT-TYPE ifAvailableStackTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuAvailableStackEntry SYNTAX SEQUENCE OF IfAvailableStackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table, modeled after ifStackTable from [IF-MIB], "This table, modeled after ifStackTable from [IF-MIB],
contains information on the possible 'on-top-of' contains information on the possible 'on-top-of'
relationships between the multiple sub-layers of network relationships between the multiple sub-layers of network
interfaces (as opposed to actual relationships in interfaces (as opposed to actual relationships in
ifStackTable). In particular, it contains information on ifStackTable). In particular, it contains information on
which PCS ports (sublayers) can possibly run 'on top of' which PCS ports (sublayers) can possibly run 'on top of'
which PMEs (sublayers), as determined by cross-connect which PMEs (sublayers), as determined by cross-connect
capability of the EFMCu device, where each sub-layer capability of the EFMCu device, where each sub-layer
corresponds to a conceptual row in the ifTable. For example, corresponds to a conceptual row in the ifTable. For example,
when the PCS port with ifIndex value x can be connected when the PCS port with ifIndex value x can be connected
to run on top of the PME with ifIndex value y, then this table to run on top of the PME with ifIndex value y, then this table
contains: contains:
efmCuAvailableStackStatus.x.y=capable ifAvailableStackStatus.x.y=capable
Note that there's always at least on PCS for each PME and at Note that there's always at least on PCS for each PME and at
least one PME for each PCS in the EFMCu devices, with least one PME for each PCS in the EFMCu devices, with
efmCuPAFCapacity and efmCuPeerPAFCapacity indicating efmCuPAFCapacity and efmCuPeerPAFCapacity indicating
maximum number of PMEs which can be aggregated by local and maximum number of PMEs which can be aggregated by local and
remote PCS port respectively. remote PCS port respectively.
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 }
efmCuAvailableStackEntry OBJECT-TYPE ifAvailableStackEntry OBJECT-TYPE
SYNTAX EfmCuAvailableStackEntry 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 sub-
layers, specifying that one sub-layer (PCS) runs on 'top' of layers, specifying that one sub-layer (PCS) runs on 'top' of
the other sub-layer (PME). Each sub-layer corresponds to a 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 {
efmCuAvailableStackHigherLayer, ifAvailableStackHigherLayer,
efmCuAvailableStackLowerLayer ifAvailableStackLowerLayer
} }
::= { efmCuAvailableStackTable 1 } ::= { ifAvailableStackTable 1 }
EfmCuAvailableStackEntry ::= IfAvailableStackEntry ::=
SEQUENCE { SEQUENCE {
efmCuAvailableStackHigherLayer InterfaceIndex, ifAvailableStackHigherLayer InterfaceIndex,
efmCuAvailableStackLowerLayer InterfaceIndex, ifAvailableStackLowerLayer InterfaceIndex,
efmCuAvailableStackStatus INTEGER ifAvailableStackStatus INTEGER
} }
efmCuAvailableStackHigherLayer OBJECT-TYPE
ifAvailableStackHigherLayer OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of ifIndex corresponding to the higher sub-layer "The value of ifIndex corresponding to the higher sub-layer
of the 'cross-connect capability' relationship, i.e., the of the 'cross-connect capability' relationship, i.e., the
PCS sub-layer which MAY run on 'top' of the PME sub-layer PCS sub-layer which MAY run on 'top' of the PME sub-layer
identified by the corresponding instance of identified by the corresponding instance of
efmCuAvailableStackLowerLayer." ifAvailableStackLowerLayer."
::= { efmCuAvailableStackEntry 1 } ::= { ifAvailableStackEntry 1 }
efmCuAvailableStackLowerLayer OBJECT-TYPE ifAvailableStackLowerLayer OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of ifIndex corresponding to the lower sub-layer "The value of ifIndex corresponding to the lower sub-layer
of the 'cross-connect capability' relationship, i.e., the of the 'cross-connect capability' relationship, i.e., the
PME sub-layer which MAY run 'below' the PCS sub-layer PME sub-layer which MAY run 'below' the PCS sub-layer
identified by the corresponding instance of identified by the corresponding instance of
efmCuAvailableStackHigherLayer." ifAvailableStackHigherLayer."
::= { efmCuAvailableStackEntry 2 } ::= { ifAvailableStackEntry 2 }
efmCuAvailableStackStatus OBJECT-TYPE ifAvailableStackStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
capable(1), capable(1),
outOfService(2) outOfService(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of the 'cross-connect capability' relationship "The status of the 'cross-connect capability' relationship
between two sub-layers. The following values are defined: between two sub-layers. The following values are defined:
capable(1) - the PME sub-layer interface, identified by capable(1) - the PME sub-layer interface, identified by
the efmCuAvailableStackLowerLayer MAY be the ifAvailableStackLowerLayer MAY be
connected to run 'below' the PCS sub-layer connected to run 'below' the PCS sub-layer
interface, identified by the interface, identified by the
efmCuAvailableStackLowerLayer. ifAvailableStackLowerLayer.
outOfService(2) - the PME sub-layer interface cannot be outOfService(2) - the PME sub-layer interface cannot be
connected due to unavailability of the connected due to unavailability of the
interface. interface.
Note that PME availability per PCS, indicated by 'capable' Note that PME availability per PCS, indicated by 'capable'
value, can be constrained by other parameters, value, can be constrained by other parameters,
for example by aggregation capacity of a PCS or by the PME in for example by aggregation capacity of a PCS or by the PME in
question being already connected to another PCS. So, in question being already connected to another PCS. So, in
order to ensure that a particular PME can be connected to the order to ensure that a particular PME can be connected to the
PCS, all respective parameters (e.g. efmCuAvailableStackTable, PCS, all respective parameters (e.g. ifAvailableStackTable,
ifStackTable and efmCuPAFCapacity) SHALL be inspected. ifStackTable and efmCuPAFCapacity) SHALL be inspected.
This object is read only, unlike ifStackStatus, as it This object is read only, unlike ifStackStatus, as it
describes the device capability." describes the device capability."
::= { efmCuAvailableStackEntry 3 } ::= { ifAvailableStackEntry 3 }
-- --
-- Conformance Statements -- Conformance Statements
-- --
efmCuGroups OBJECT IDENTIFIER ::= { efmCuConformance 1 } efmCuGroups OBJECT IDENTIFIER ::= { efmCuConformance 1 }
efmCuCompliances OBJECT IDENTIFIER ::= { efmCuConformance 2 } efmCuCompliances OBJECT IDENTIFIER ::= { efmCuConformance 2 }
-- Object Groups -- Object Groups
skipping to change at page 58, line 45 skipping to change at page 60, line 11
efmCuPAFGroup OBJECT-GROUP efmCuPAFGroup OBJECT-GROUP
OBJECTS { OBJECTS {
efmCuPeerPAFSupported, efmCuPeerPAFSupported,
efmCuPAFCapacity, efmCuPAFCapacity,
efmCuPeerPAFCapacity, efmCuPeerPAFCapacity,
efmCuPAFAdminState, efmCuPAFAdminState,
efmCuPAFDiscoveryCode, efmCuPAFDiscoveryCode,
efmCuPAFRemoteDiscoveryCode, efmCuPAFRemoteDiscoveryCode,
efmCuNumPMEs, efmCuNumPMEs,
efmCuAvailableStackStatus ifAvailableStackStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects required for optional PME "A collection of objects required for optional PME
Aggregation Function (PAF) and PAF discovery in EFMCu ports." Aggregation Function (PAF) and PAF discovery in EFMCu ports."
::= { efmCuGroups 2 } ::= { efmCuGroups 2 }
ifStackCapabilityGroup OBJECT-GROUP
OBJECTS {
ifAvailableStackStatus
}
STATUS current
DESCRIPTION
"A collection of objects providing information on
the stacking capability of MIB-II interfaces."
::= { efmCuGroups 3 }
efmCuPAFErrorsGroup OBJECT-GROUP efmCuPAFErrorsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
efmCuPAFInErrors, efmCuPAFInErrors,
efmCuPAFInSmallFragments, efmCuPAFInSmallFragments,
efmCuPAFInLargeFragments, efmCuPAFInLargeFragments,
efmCuPAFInBadFragments, efmCuPAFInBadFragments,
efmCuPAFInLostFragments, efmCuPAFInLostFragments,
efmCuPAFInLostStarts, efmCuPAFInLostStarts,
efmCuPAFInLostEnds, efmCuPAFInLostEnds,
efmCuPAFInOverflows efmCuPAFInOverflows
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects supporting optional error counters "A collection of objects supporting optional error counters
of PAF on EFMCu ports." of PAF on EFMCu ports."
::= { efmCuGroups 3 } ::= { efmCuGroups 4 }
efmCuPmeGroup OBJECT-GROUP efmCuPmeGroup OBJECT-GROUP
OBJECTS { OBJECTS {
efmCuPmeAdminProfile, efmCuPmeAdminProfile,
efmCuPmeOperStatus, efmCuPmeOperStatus,
efmCuPmeFltStatus, efmCuPmeFltStatus,
efmCuPmeSubTypesSupported, efmCuPmeSubTypesSupported,
efmCuPmeAdminSubType, efmCuPmeAdminSubType,
efmCuPmeOperSubType, efmCuPmeOperSubType,
efmCuPAFRemoteDiscoveryCode, efmCuPAFRemoteDiscoveryCode,
skipping to change at page 59, line 44 skipping to change at page 61, line 19
efmCuPmePeerSnrMgn, efmCuPmePeerSnrMgn,
efmCuPmeLineAtn, efmCuPmeLineAtn,
efmCuPmePeerLineAtn, efmCuPmePeerLineAtn,
efmCuPmeTCCodingErrors, efmCuPmeTCCodingErrors,
efmCuPmeThreshLineAtn, efmCuPmeThreshLineAtn,
efmCuPmeThreshSnrMgn efmCuPmeThreshSnrMgn
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about "A collection of objects providing information about
a 2BaseTL/10PassTS PME." a 2BASE-TL/10PASS-TS PME."
::= { efmCuGroups 4 } ::= { efmCuGroups 5 }
efmCuAlarmConfGroup OBJECT-GROUP efmCuAlarmConfGroup OBJECT-GROUP
OBJECTS { OBJECTS {
efmCuThreshLowBandwidth, efmCuThreshLowBandwidth,
efmCuLowBandwidthEnable, efmCuLowBandwidthEnable,
efmCuPmeThreshLineAtn, efmCuPmeThreshLineAtn,
efmCuPmeLineAtnCrossingEnable, efmCuPmeLineAtnCrossingEnable,
efmCuPmeThreshSnrMgn, efmCuPmeThreshSnrMgn,
efmCuPmeSnrMgnCrossingEnable, efmCuPmeSnrMgnCrossingEnable,
efmCuPmeLineAtnCrossingEnable, efmCuPmeLineAtnCrossingEnable,
skipping to change at page 60, line 21 skipping to change at page 61, line 44
-- efmCuPmeThreshES, -- efmCuPmeThreshES,
-- efmCuPmethreshSES, -- efmCuPmethreshSES,
-- efmCuPmeThreshCRCanomalies, -- efmCuPmeThreshCRCanomalies,
-- efmCuPmeThreshLOSWS, -- efmCuPmeThreshLOSWS,
-- efmCuPmeThreshUAS -- efmCuPmeThreshUAS
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects required for configuration of alarm "A collection of objects required for configuration of alarm
thresholds and notifications in EFMCu ports." thresholds and notifications in EFMCu ports."
::= { efmCuGroups 5 } ::= { efmCuGroups 6 }
efmCuNotificationGroup NOTIFICATION-GROUP efmCuNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
efmCuLowBandwidth, efmCuLowBandwidth,
efmCuPmeLineAtnCrossing, efmCuPmeLineAtnCrossing,
efmCuPmeSnrMgnCrossing, efmCuPmeSnrMgnCrossing,
efmCuPmeDeviceFault, efmCuPmeDeviceFault,
efmCuPmeConfigInitFailure, efmCuPmeConfigInitFailure,
efmCuPmeProtocolInitFailure efmCuPmeProtocolInitFailure
-- efmCuPmePerfES, -- efmCuPmePerfES,
skipping to change at page 60, line 43 skipping to change at page 62, line 18
-- efmCuPmePerfCRCanomalies, -- efmCuPmePerfCRCanomalies,
-- efmCuPmePerfLOSWS, -- efmCuPmePerfLOSWS,
-- efmCuPmePerfUAS, -- efmCuPmePerfUAS,
-- efmCuPmeDeviceFault, -- efmCuPmeDeviceFault,
-- efmCuPmeLocalPowerLoss -- efmCuPmeLocalPowerLoss
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group supports notifications of significant conditions "This group supports notifications of significant conditions
associated with EFMCu ports." associated with EFMCu ports."
::= { efmCuGroups 6 } ::= { efmCuGroups 7 }
efmCuPme2BProfileGroup OBJECT-GROUP efmCuPme2BProfileGroup OBJECT-GROUP
OBJECTS { OBJECTS {
efmCuPme2BProfileDescr, efmCuPme2BProfileDescr,
efmCuPme2BRegion, efmCuPme2BRegion,
efmCuPme2BDataRate, efmCuPme2BDataRate,
efmCuPme2BPower, efmCuPme2BPower,
efmCuPme2BConstellation, efmCuPme2BConstellation,
efmCuPme2BProfileRowStatus efmCuPme2BProfileRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects that constitute a configuration "A collection of objects that constitute a configuration
profile for configuration of 2BaseTL ports." profile for configuration of 2BASE-TL ports."
::= { efmCuGroups 7 } ::= { efmCuGroups 8 }
efmCuPme10PProfileGroup OBJECT-GROUP efmCuPme10PProfileGroup OBJECT-GROUP
OBJECTS { OBJECTS {
efmCuPme10PProfileDescr, efmCuPme10PProfileDescr,
efmCuPme10PBandplanPSDMskProfile, efmCuPme10PBandplanPSDMskProfile,
efmCuPme10PUPBOReferenceProfile, efmCuPme10PUPBOReferenceProfile,
efmCuPme10PBandNotchProfiles, efmCuPme10PBandNotchProfiles,
efmCuPme10PPayloadURateProfile, efmCuPme10PPayloadURateProfile,
efmCuPme10PPayloadDRateProfile, efmCuPme10PPayloadDRateProfile,
efmCuPme10PProfileRowStatus efmCuPme10PProfileRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects that constitute a configuration "A collection of objects that constitute a configuration
profile for configuration of 10PassTS ports." profile for configuration of 10PASS-TS ports."
::= { efmCuGroups 8 } ::= { efmCuGroups 9 }
efmCuPme10PStatusGroup OBJECT-GROUP efmCuPme10PStatusGroup OBJECT-GROUP
OBJECTS { OBJECTS {
efmCuPme10PElectricalLength, efmCuPme10PElectricalLength,
efmCuPme10PFECCorrectedBlocks, efmCuPme10PFECCorrectedBlocks,
efmCuPme10PFECUncorrectedBlocks efmCuPme10PFECUncorrectedBlocks
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing status information "A collection of objects providing status information
specific to 10PassTS PMEs." specific to 10PASS-TS PMEs."
::= { efmCuGroups 9 } ::= { efmCuGroups 10 }
-- Compliance Statements -- Compliance Statements
efmCuCompliance MODULE-COMPLIANCE efmCuCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for 2BaseTL/10PassTS interfaces. "The compliance statement for 2BASE-TL/10PASS-TS interfaces.
Compliance with the following external compliance statements Compliance with the following external compliance statements
is prerequisite: is prerequisite:
MIB Module Compliance Statement MIB Module Compliance Statement
---------- -------------------- ---------- --------------------
IF-MIB ifCompliance3 IF-MIB ifCompliance3
IF-INVERTED-STACK-MIB ifInvCompliance IF-INVERTED-STACK-MIB ifInvCompliance
EtherLike-MIB dot3Compliance2 EtherLike-MIB dot3Compliance2
MAU-MIB mauModIfCompl3" MAU-MIB mauModIfCompl3"
skipping to change at page 62, line 19 skipping to change at page 63, line 42
MANDATORY-GROUPS { MANDATORY-GROUPS {
efmCuBasicGroup, efmCuBasicGroup,
efmCuPmeGroup, efmCuPmeGroup,
efmCuAlarmConfGroup, efmCuAlarmConfGroup,
efmCuNotificationGroup efmCuNotificationGroup
} }
GROUP efmCuPme2BProfileGroup GROUP efmCuPme2BProfileGroup
DESCRIPTION DESCRIPTION
"Support for this group is only required for implementations "Support for this group is only required for implementations
supporting 2Base-TL Phy." supporting 2BASE-TL Phy."
GROUP efmCuPme10PProfileGroup GROUP efmCuPme10PProfileGroup
DESCRIPTION DESCRIPTION
"Support for this group is only required for implementations "Support for this group is only required for implementations
supporting 10Pass-TS Phy." supporting 10PASS-TS Phy."
GROUP efmCuPAFGroup GROUP efmCuPAFGroup
DESCRIPTION DESCRIPTION
"Support for this group is only required for implementations "Support for this group is only required for
supporting PME Aggregation Function (PAF)." implementations supporting PME Aggregation Function (PAF)."
GROUP ifStackCapabilityGroup
DESCRIPTION
"Support for this group is optional for implementations
supporting layered interfaces architecture with
flexible cross-connect between the layers."
GROUP efmCuPAFErrorsGroup GROUP efmCuPAFErrorsGroup
DESCRIPTION DESCRIPTION
"Support for this group is optional for implementations "Support for this group is optional for implementations
supporting PME Aggregation Function (PAF)." supporting PME Aggregation Function (PAF)."
GROUP efmCuPme10PStatusGroup GROUP efmCuPme10PStatusGroup
DESCRIPTION DESCRIPTION
"Support for this group is optional for implementations "Support for this group is optional for implementations
supporting 10Pass-TS Phy." supporting 10PASS-TS Phy."
OBJECT efmCuPmeSubTypesSupported OBJECT efmCuPmeSubTypesSupported
SYNTAX BITS { SYNTAX BITS {
ieee2BaseTLO(0), ieee2BaseTLO(0),
ieee2BaseTLR(1), ieee2BaseTLR(1),
ieee10PassTSO(2), ieee10PassTSO(2),
ieee10PassTSR(3) ieee10PassTSR(3)
} }
DESCRIPTION DESCRIPTION
"Support for all subtypes is not required. However at least "Support for all subtypes is not required. However at least
skipping to change at page 63, line 16 skipping to change at page 64, line 45
DESCRIPTION DESCRIPTION
"Write access is not required (needed only for PMEs "Write access is not required (needed only for PMEs
supporting more than a single subtype, e.g. supporting more than a single subtype, e.g.
ieee2BaseTLO and ieee2BaseTSR or ieee2BaseTLR and ieee2BaseTLO and ieee2BaseTSR or ieee2BaseTLR and
ieee10PassTSR)" ieee10PassTSR)"
OBJECT efmCuTargetSnrMgn OBJECT efmCuTargetSnrMgn
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is optional. For PHYs without write access "Write access is optional. For PHYs without write access
the target SNR margin SHALL be fixed at 5dB for 2BaseTL the target SNR margin SHALL be fixed at 5dB for 2BASE-TL
and 6dB for 10PassTS." and 6dB for 10PASS-TS."
-- EdNote: To be Continued -- EdNote: To be Continued
::= { efmCuCompliances 1 } ::= { efmCuCompliances 1 }
END END
6. Security Considerations 6. Security Considerations
There is a number of managed objects defined in this MIB module that There is a number of managed objects defined in this MIB module that
have a MAX-ACCESS clause of read-write or read-create. Most objects have a MAX-ACCESS clause of read-write or read-create. Most objects
skipping to change at page 64, line 51 skipping to change at page 66, line 29
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. Acknowledgments
Not yet. This document was produced by the IETF Ethernet Interfaces and Hub
MIB Working Group, whose efforts were greatly advanced by the
contributions of the following people (in alphabetical order):
Dan Romascanu
Mathias Riess
Matt Squire
Mike Heard
Udi Ashkenazi
8. References 8. References
8.1 Normative References 8.1 Normative References
[802.3ah] IEEE, "Draft amendment to - Information technology - [802.3ah] IEEE, "Draft amendment to - 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 - Media Access Control Parameters,
Physical Layers and Management Parameters for subscriber Physical Layers and Management Parameters for Subscriber
access networks", IEEE Draft P802.3ah/D3.3, April 2004. 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 66, line 11 skipping to change at page 67, line 51
[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-04 (work in
progress), May 2004. progress), May 2004.
[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-01 (work Optical Networks", draft-ietf-hubmib-efm-epon-mib-02 (work
in progress), April 2004. in progress), September 2004.
[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-01 (work in progress), June
2004. 2004.
[I-D.ietf-hubmib-rfc3636bis]
Beili, E., "Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs)",
draft-ietf-hubmib-rfc3636bis-00 (work in progress),
October 2004.
[IANAifType-MIB]
Internet Assigned Numbers Authority (IANA), "IANAifType
Textual Convention definition",
http://www.iana.org/assignments/ianaiftype-mib.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table [RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table
Extension to the Interfaces Group MIB", RFC 2864, June Extension to the Interfaces Group MIB", RFC 2864, June
2000. 2000.
[RFC3635] Flick, J., "Definitions of Managed Objects for the [RFC3635] Flick, J., "Definitions of Managed Objects for the
Ethernet-like Interface Types", RFC 3635, September 2003. Ethernet-like Interface Types", RFC 3635, September 2003.
[RFC3636] Flick, J., "Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs)", RFC 3636, September 2003.
Author's Address Author's Address
Edward Beili Edward Beili
Actelis Networks Actelis Networks
Bazel 25 Bazel 25
Petach-Tikva Petach-Tikva
Israel Israel
Phone: +972-3-924-3491 Phone: +972-3-924-3491
 End of changes. 

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