draft-ietf-hubmib-efm-cu-mib-05.txt   draft-ietf-hubmib-efm-cu-mib-06.txt 
Network Working Group E. Beili Network Working Group E. Beili
Internet-Draft Actelis Networks Internet-Draft Actelis Networks
Expires: December 19, 2006 June 17, 2006 Expires: April 15, 2007 October 12, 2006
Ethernet in the First Mile Copper (EFMCu) Interfaces MIB Ethernet in the First Mile Copper (EFMCu) Interfaces MIB
draft-ietf-hubmib-efm-cu-mib-05.txt draft-ietf-hubmib-efm-cu-mib-06.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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 December 19, 2006. This Internet-Draft will expire on April 15, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
This document defines a Management Information Base (MIB) module for This document defines Management Information Base (MIB) modules for
use with network management protocols in TCP/IP based internets. use with network management protocols in TCP/IP based internets.
This document proposes an extension to the Ethernet-like Interfaces This document proposes an extension to the Ethernet-like Interfaces
MIB and MAU MIB modules with a set of objects for managing an MIB and MAU MIB modules with a set of objects for managing Ethernet
Ethernet in the First Mile Copper (EFMCu) interfaces 10PASS-TS and in the First Mile Copper (EFMCu) interfaces 10PASS-TS and 2BASE-TL,
2BASE-TL, defined in IEEE Std 802.3ah-2004. defined in IEEE Std 802.3ah-2004. In addition a set of objects is
defined, describing cross-connect capability of a managed device with
multi-layer (stacked) interfaces, extending the stack management
objects in the Interfaces Group MIB and the Inverted Stack Table MIB
modules.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Relation to other MIB modules . . . . . . . . . . . . . . . . 4 3. Relation to other MIB modules . . . . . . . . . . . . . . . . 4
3.1. Relation to Interfaces Group MIB module . . . . . . . . . 4 3.1. Relation to Interfaces Group MIB module . . . . . . . . . 4
3.1.1. Layering Model . . . . . . . . . . . . . . . . . . . . 4 3.1.1. Layering Model . . . . . . . . . . . . . . . . . . . . 4
3.1.2. PME Aggregation Function (PAF) . . . . . . . . . . . . 6 3.1.2. PME Aggregation Function (PAF) . . . . . . . . . . . . 6
3.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 6 3.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 7
3.1.4. EFMCu ports initialization . . . . . . . . . . . . . . 8 3.1.4. EFMCu ports initialization . . . . . . . . . . . . . . 9
3.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 8 3.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 9
3.2. Relation to SHDSL MIB module . . . . . . . . . . . . . . . 9 3.2. Relation to SHDSL MIB module . . . . . . . . . . . . . . . 10
3.3. Relation to VDSL MIB module . . . . . . . . . . . . . . . 10 3.3. Relation to VDSL MIB module . . . . . . . . . . . . . . . 10
3.4. Relation to Ethernet-Like and MAU MIB modules . . . . . . 10 3.4. Relation to Ethernet-Like and MAU MIB modules . . . . . . 11
4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 11 4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1. EFM Copper MIB Overview . . . . . . . . . . . . . . . . . 12
4.2. PME Profiles . . . . . . . . . . . . . . . . . . . . . . . 11 4.2. Interface stack capability MIB Overview . . . . . . . . . 12
4.3. Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 12 4.3. PME Profiles . . . . . . . . . . . . . . . . . . . . . . . 13
5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.4. Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 13
6. Security Considerations . . . . . . . . . . . . . . . . . . . 75 5. Interface Stack Capability MIB Definitions . . . . . . . . . . 14
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 77 6. EFM Copper MIB Definitions . . . . . . . . . . . . . . . . . . 21
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 77 7. Security Considerations . . . . . . . . . . . . . . . . . . . 82
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 77 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 83
9.1. Normative References . . . . . . . . . . . . . . . . . . . 77 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 83
9.2. Informative References . . . . . . . . . . . . . . . . . . 78 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 80 10.1. Normative References . . . . . . . . . . . . . . . . . . . 84
Intellectual Property and Copyright Statements . . . . . . . . . . 81 10.2. Informative References . . . . . . . . . . . . . . . . . . 85
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 87
Intellectual Property and Copyright Statements . . . . . . . . . . 88
1. Introduction 1. Introduction
New Ethernet-like interfaces have been defined in the Institute of New Ethernet-like interfaces have been defined in the Institute of
Electrical and Electronics Engineers (IEEE) Standard 802.3ah-2004 Electrical and Electronics Engineers (IEEE) Standard 802.3ah-2004
[802.3ah], a.k.a. Ethernet in the First Mile (EFM), which is now a [802.3ah], a.k.a. Ethernet in the First Mile (EFM), which is now a
part of the base IEEE Standard 802.3-2005 [802.3]. In particular part of the base IEEE Standard 802.3-2005 [802.3]. In particular
2BASE-TL and 10PASS-TS physical interfaces (PHYs), defined over 2BASE-TL and 10PASS-TS physical interfaces (PHYs), defined over
voice-grade copper pairs, have been specified for the long and short voice-grade copper pairs, have been specified for the long and short
reach respectively. These interfaces, collectively called EFMCu, are reach respectively. These interfaces, collectively called EFMCu, are
skipping to change at page 3, line 28 skipping to change at page 3, line 28
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 Management Information Base (MIB) module for use This memo defines a Management Information Base (MIB) module for use
with network management protocols in the Internet community to manage with network management protocols in the Internet community to manage
EFMCu interfaces. EFMCu interfaces. In addition a MIB module is defined describing
cross-connect capability of a stacked interface.
Note that managed objects for Operation, Administration and Note that managed objects for Operation, Administration and
Management (OAM) and Ethernet over Passive Optical Networks (EPON) Management (OAM) and Ethernet over Passive Optical Networks (EPON)
clauses of IEEE 802.3ah are defined in EFM-COMMON-MIB [I-D.ietf- clauses of IEEE 802.3ah are defined in EFM-COMMON-MIB [I-D.ietf-
hubmib-efm-mib] and EFM-EPON-MIB [I-D.ietf-hubmib-efm-epon-mib] hubmib-efm-mib] and EFM-EPON-MIB [I-D.ietf-hubmib-efm-epon-mib]
respectively. respectively.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
skipping to change at page 4, line 9 skipping to change at page 4, line 11
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. Relation to other MIB modules 3. Relation to other MIB modules
This section outlines the relationship of this MIB with other MIB This section outlines the relationship of the MIB modules defined in
modules described in the relevant RFCs. Specifically, Interfaces this document with other MIB modules described in the relevant RFCs.
Group MIB (IF-MIB), Ethernet-Like (EtherLike-MIB), MAU (MAU-MIB), Specifically, Interfaces Group MIB (IF-MIB), Ethernet-Like
SHDSL (HDSL2-SHDSL-LINE-MIB) and VDSL (VDSL-LINE-EXT-MCM-MIB) are (EtherLike-MIB), MAU (MAU-MIB), SHDSL (HDSL2-SHDSL-LINE-MIB) and VDSL
discussed. (VDSL-LINE-EXT-MCM-MIB) are discussed.
3.1. Relation to Interfaces Group MIB module 3.1. Relation to Interfaces Group MIB module
2BASE-TL and 10PASS-TS PHY's specified in this MIB module are stacked 2BASE-TL and 10PASS-TS PHY's specified in the EFM-CU-MIB module are
Ethernet interfaces and as such are managed using generic interface stacked (a.k.a. aggregated or bonded) Ethernet interfaces and as such
management objects defined in the IF-MIB [RFC2863]. The stack are managed using generic interface management objects defined in the
management is done via the ifStackTable, as defined in the IF-MIB IF-MIB [RFC2863].
[RFC2863] and ifInvStackTable, as defined in the IF-INVERTED-STACK-
MIB [RFC2864]. The stack management, i.e. actual connection of the sub-layers to the
top layer interface, is done via the ifStackTable, as defined in the
IF-MIB [RFC2863] and its inverse ifInvStackTable, as defined in the
IF-INVERTED-STACK-MIB [RFC2864].
The new tables ifCapStackTable and its inverse ifInvCapStackTable
defined in the IF-CAP-STACK-MIB module below, extend the stack
management with an ability to describe possible connections or cross-
connect capability, when a flexible cross-connect matrix is present
between the interface layers.
3.1.1. Layering Model 3.1.1. Layering Model
An EFMCu interface can aggregate up to 32 Physical Medium Entity An EFMCu interface can aggregate up to 32 Physical Medium Entity
(PME) sub-layer devices (modems), using so called PME Aggregation (PME) sub-layer devices (modems), using so called PME Aggregation
Function (PAF). Function (PAF).
A generic EFMCu device can have a number of Physical Coding Sublayer A generic EFMCu device can have a number of Physical Coding Sublayer
(PCS) ports, each connected to a MAC via Medium Independent Interface (PCS) ports, each connected to a MAC via 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
skipping to change at page 5, line 49 skipping to change at page 6, line 9
The ifStackTable is indexed by the ifIndex values of the aggregated The ifStackTable is indexed by the ifIndex values of the aggregated
EFMCu port (PCS) and the PMEs connected to it. ifStackTable allows a EFMCu port (PCS) and the PMEs connected to it. ifStackTable allows a
Network Management application to determine which PMEs are connected Network Management application to determine which PMEs are connected
to a particular PCS and change connections (if supported by the to a particular PCS and change connections (if supported by the
application). The ifInvStackTable, being an inverted version of the application). The ifInvStackTable, being an inverted version of the
ifStackTable, provides an efficient means for a Network Management ifStackTable, provides an efficient means for a Network Management
application to read a subset of the ifStackTable and thereby application to read a subset of the ifStackTable and thereby
determine which PCS runs on top of a particular PME. determine which PCS runs on top of a particular PME.
A new table ifAvailableStackTable defined in this MIB module, A new table ifCapStackTable defined in the IF-CAP-STACK-MIB module,
specifies for each PCS a list of PMEs, which can possibly be cross- specifies for each higher-layer interface (e.g. PCS port) a list of
connected to that PCS, determined by the cross-connect capability of lower-layer interfaces (e.g. PMEs), which can possibly be cross-
the device. This table, modeled after ifStackTable, is read only, connected to that higher-layer interface, determined by the cross-
reflecting current cross-connect capability, which can be dynamic in connect capability of the device. This table, modeled after
some implementations (e.g. if PMEs are located on a pluggable module ifStackTable, is read only, reflecting current cross-connect
and the module is pulled out). Note that PME availability per PCS, capability of a stacked interface, which can be dynamic in some
described by ifAvailableStackTable, can be constrained by other implementations (e.g. if PMEs are located on a pluggable module and
parameters, for example by aggregation capacity of a PCS or by the the module is pulled out). Note that PME availability per PCS,
PME in question being already connected to another PCS. So, in order described by ifCapStackTable, can be constrained by other parameters,
to ensure that a particular PME can be connected to the PCS, all for example by aggregation capacity of a PCS or by the PME in
respective parameters (e.g. ifAvailableStackTable, ifStackTable and question being already connected to another PCS. So, in order to
ensure that a particular PME can be connected to the PCS, all
respective parameters (e.g. ifCapStackTable, ifStackTable and
efmCuPAFCapacity) SHALL be inspected. efmCuPAFCapacity) SHALL be inspected.
The ifInvCapStackTable, also defined in the IF-CAP-STACK-MIB module,
describes which higher-layer interfaces (e.g. PCS ports) can
possibly be connected to a particular lower-layer interface (e.g.
PME), providing inverted mapping of ifCapStackTable. While it
contains no additional information beyond that already contained in
the ifCapStackTable, the ifInvCapStackTable has the ifIndex values in
its INDEX clause in the reverse order, i.e., the lower-layer
interface first, and the higher-layer interface second, providing an
efficient means for a Network Management application to read a subset
of the ifCapStackTable and thereby determine which interfaces can be
connected to run on top of a particular interface.
3.1.2. PME Aggregation Function (PAF) 3.1.2. PME Aggregation Function (PAF)
The PME Aggregation Function (PAF) allows a number of PMEs to be The PME Aggregation Function (PAF) allows a number of PMEs to be
aggregated onto a PCS port, by fragmenting the Ethernet frames, aggregated onto a PCS port, by fragmenting the Ethernet frames,
transmitting the fragments over multiple PMEs and assembling the transmitting the fragments over multiple PMEs and assembling the
original frames at the remote port. PAF is OPTIONAL, meaning that a original frames at the remote port. PAF is OPTIONAL, meaning that a
device with a single PME MAY perform fragmentation and re-assembly if device with a single PME MAY perform fragmentation and re-assembly if
this function is supported by the device. Note however that the this function is supported by the device. Note however that the
agent is REQUIRED to report on the PAF capability for all EFMCu ports agent is REQUIRED to report on the PAF capability for all EFMCu ports
(2BASE-TL and 10PASS-TS). (2BASE-TL and 10PASS-TS).
This MIB module allows a Network Management application to query PAF The EFM-CU-MIB module allows a Network Management application to
capability and enable/disable it if supported. Note that enabling query PAF capability and enable/disable it if supported. Note that
PAF effectively turns on fragmentation and re-assembly, even on a enabling PAF effectively turns on fragmentation and re-assembly, even
single-PME port. on a single-PME port.
3.1.3. Discovery Operation 3.1.3. Discovery Operation
The EFMCu ports may optionally support discovery operation, whereby The EFMCu ports may optionally support discovery operation, whereby
PMEs, during initialization, exchange information about their PMEs, during initialization, exchange information about their
respective aggregation groups (PCS). This information can then be respective aggregation groups (PCS). This information can then be
used to detect copper misconnections or for an automatic assignment used to detect copper misconnections or for an automatic assignment
of the local PMEs into aggregation groups instead of fixed pre- of the local PMEs into aggregation groups instead of a fixed pre-
configuration. configuration.
This MIB module allows a Network Management application to control The MIB modules defined in this document allow a Network Management
EFM Discovery mechanism and query its results. Note that the application to control EFM Discovery mechanism and query its results.
Discovery mechanism can work only if PAF is supported and enabled. Note that the Discovery mechanism can work only if PAF is supported
and enabled.
Two tables are used by Discovery mechanism: ifStackTable and Two tables are used by the EFM Discovery mechanism: ifStackTable and
ifAvailableStackTable defined. The following pseudo-code defines an ifCapStackTable. The following pseudo-code gives an example of the
example of Discovery and automatic PME assignment for a generic PAF Discovery and automatic PME assignment for a generic PAF enabled
enabled multi-PCS EFMCu device, located at Central Office (CO), using multi-PCS EFMCu device, located at Central Office (CO), using objects
objects defined in this MIB module. [Note that automatic PME defined in these MIB modules and in IF-MIB [Note that automatic PME
assignment is only shown here for the purposes of the example. Fixed assignment is only shown here for the purposes of the example. Fixed
PME pre-assignment, manual assignment or auto-assignment by an PME pre-assignment, manual assignment or auto-assignment using an
alternative internal algorithm may be chosen by a particular alternative internal algorithm may be chosen by a particular
implementation]: implementation]:
FOREACH pcs[i] IN co_device // Go over all PCS ports in the CO device
{ // Discover only on PAF enabled ports with room for more PMEs FOREACH pcs[i] IN CO_device
{ // Perform discovery and auto-assignment only on PAF enabled ports
// with room for more PMEs
IF ( pcs[i].PAFSupported AND pcs[i].NumPMEs < pcs[i].PAFCapacity ) 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 disconnected PMEs, which can
// pottentially be connected to PCS[i] // pottentially be connected to the PCS
FOREACH pme[j] IN ifAvailableStackTable[pcs[i]] AND FOREACH pme[j] IN ifCapStackTable[pcs[i]] AND
NOT IN ifInvStackTable[pme[j]] // unassigned NOT ifInvStackTable[pme[j]] // not connected
{ pme[j].RemoteDiscoveryCode = dc; // Set if Clear { // Try to grab the remote RT_device, by writing the value
// of the local 6 Byte discovery code to the remote
// discovery code register (via handshake mechanism).
// This operation is atomic Set-if-Clear action, i.e. it
// would succeed only if the remote discovery register was
// zero. Read the remote discovery code register via Get
// operation to see if the RT_device, attached via the PME
// is indeed marked as being the CO_device peer.
pme[j].RemoteDiscoveryCode = dc; // Set-if-Clear
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 RT_device connected via PME[j] is/was a peer
// PCS[i]. Connect this PME to the PCS (there's room) // for PCS[i] and there room for another PME in the
// PCS[i] aggregation group (max. PAF capacity is not
// reached yet).
// Connect this PME to the PCS (via ifStackTable,
// ifInvStackTable being inverse of ifStackTable is
// updated automatically)
ADD pme[j] TO ifStackTable[pcs[i]]; ADD pme[j] TO ifStackTable[pcs[i]];
// pcs[i] is auto-added to ifInvStackTable[pme[j]]
pcs[i].NumPMEs = pcs[i].NumPMEs + 1; pcs[i].NumPMEs = pcs[i].NumPMEs + 1;
// Discover all other currently disconnected PMEs, // Discover all other disconnected PMEs,
// attached to the same CPE and connect them to the PCS // attached to the same RT_device and connect them to
// provided there is enough room for more PMEs. // the PCS provided there is enough room for more PMEs.
FOREACH pme[k] IN ifAvailableStackTable[pcs[i]] and FOREACH pme[k] IN ifCapStackTable[pcs[i]] and
NOT IN ifInvStackTable[pme[k]] NOT 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] is added TO ifInvStackTable[pme[k]]
pcs[i].NumPMEs = pcs[i].NumPMEs + 1; pcs[i].NumPMEs = pcs[i].NumPMEs + 1;
} }
} }
} }
// Discovered all PMEs which lead to the same CPE and // At this point we have discovered all local PMEs which
// connected them to PCS[i]. Go to the next PCS. // are physically connected to the same remote RT_device
// and connected them to PCS[i]. Go to the next PCS.
BREAK; BREAK;
} }
} }
} }
The SNMP Agent builds efmCuStackTable according to the information An SNMP Agent for a EFMCu device builds ifCapStackTable and its
contained in the Clause 45 PME_Available_register (see [802.3ah] inverse ifInvCapStackTable according to the information contained in
61.1.5.3 and 45.2.3.20). the Clause 45 PME_Available_register (see [802.3ah] 61.1.5.3 and
45.2.3.20).
Adding a PME to the ifStackTable row for a specific PCS, involves Adding a PME to the ifStackTable row for a specific PCS, involves
actual connection of the PME to the PCS, which can be done by actual connection of the PME to the PCS, which can be done by
modifying Clause 45 PME_Aggregate_register (see [802.3ah] 61.1.5.3 modifying Clause 45 PME_Aggregate_register (see [802.3ah] 61.1.5.3
and 45.2.3.21). and 45.2.3.21).
Note that PCS port does not have to be operationally 'down' for the Note that 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 with an available PME being initialized first (by MAY be implemented with 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 (and respective
ifInvStackTable) entry.
It is RECOMMENDED that a removal of the last operationally 'up' PME It is RECOMMENDED that a removal of the last operationally 'up' PME
from an operationally 'up' PCS would be rejected by the from an operationally 'up' PCS would be rejected by the
implementation, as this action would completely drop the link. implementation, as this action would completely drop the link.
3.1.4. EFMCu ports initialization 3.1.4. EFMCu ports initialization
EFMCu ports being built on top of xDSL technology, require a lengthy EFMCu ports being built on top of xDSL technology, require a lengthy
initialization or 'training' process, before any data can pass. initialization or 'training' process, before any data can pass.
During this initialization both ends of a link (peers) work During this initialization both ends of a link (peers) work
skipping to change at page 8, line 27 skipping to change at page 9, line 23
the line is too high, that 'training' process may fail to achieve a the line is too high, that 'training' process may fail to achieve a
specific target rate with required characteristics. specific target rate with required characteristics.
The ifAdminStatus object from the IF-MIB, controls the desired state The ifAdminStatus object from the IF-MIB, controls the desired state
of a PCS with all the PMEs connected to it or of an individual PME of a PCS with all the PMEs connected to it or of an individual PME
port. Setting this object to 'up' instructs a particular PCS or PME port. Setting this object to 'up' instructs a particular PCS or PME
to start initialization process, which may take tens of seconds for to start initialization process, which may take tens of seconds for
EFMCu ports, especially if PAF is involved. The ifOperStatus object EFMCu ports, especially if PAF is involved. The ifOperStatus object
shows the operational state of an interface (extended by shows the operational state of an interface (extended by
ifMauMediaAvailable object from MAU-MIB for PCS and ifMauMediaAvailable object from MAU-MIB for PCS and
efmCuPmeOperStatus defined in this MIB module for PME interfaces). efmCuPmeOperStatus defined in the EFM-CU-MIB module for PME
interfaces).
A disconnected PME may be initialized by changing the ifAdminState A disconnected PME may be initialized by changing the ifAdminState
from 'down' to 'up'. Changing the ifAdminState to 'up' on the PCS from 'down' to 'up'. Changing the ifAdminState to 'up' on the PCS
initializes all PMEs connected to that particular PCS. Note that in initializes all PMEs connected to that particular PCS. Note that in
case of PAF some interfaces may fail to initialize while others case of PAF some interfaces may fail to initialize while others
succeed. The PCS is considered operationally 'up' if at least one succeed. The PCS is considered operationally 'up' if at least one
PME aggregated by its PAF is operationally 'up'. When all PMEs PME aggregated by its PAF is operationally 'up'. When all PMEs
connected to the PCS are 'down' the PCS SHALL be considered connected to the PCS are 'down' the PCS SHALL be considered
operationally 'lowerLayerDown'. The PCS SHALL be considered operationally 'lowerLayerDown'. The PCS SHALL be considered
operationally 'notPresent' if it is not connected to any PME. The operationally 'notPresent' if it is not connected to any PME. The
PCS/PME interface SHALL remain operationally 'down' during PCS/PME interface SHALL remain operationally 'down' during
initialization. initialization.
The efmCuPmeOperStatus defined in this MIB module expands PME's The efmCuPmeOperStatus defined in the EFM-CU-MIB module expands PME's
ifOperStatus value of 'down' to 'downReady', 'downNotReady' and ifOperStatus value of 'down' to 'downReady', 'downNotReady' and
'init' values, indicating various EFMCu PME specific states. 'init' values, indicating various EFMCu PME specific states.
3.1.5. Usage of ifTable 3.1.5. Usage of ifTable
Both PME and PCS interfaces of the EFMCu PHY are managed using Both PME and PCS interfaces of the EFMCu PHY are managed using
interface specific management objects defined in this MIB module and interface specific management objects defined in the EFM-CU-MIB
generic interface objects from the ifTable of IF-MIB, with all module and generic interface objects from the ifTable of IF-MIB, with
management table entries referenced by the interface index ifIndex. all management table entries referenced by the interface index
ifIndex.
The following table summarizes EFMCu specific interpretations for The following table summarizes EFMCu specific interpretations for
some of the ifTable objects specified by the mandatory some of the ifTable objects specified by the mandatory
ifGeneralInformationGroup: ifGeneralInformationGroup:
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
| IF-MIB object | EFMCu interpretation | | IF-MIB object | EFMCu interpretation |
+---------------+---------------------------------------------------+ +---------------+---------------------------------------------------+
| ifIndex | Interface index. Note that each PME and each PCS | | ifIndex | Interface index. Note that each PME and each PCS |
| | in the EFMCu PHY MUST have a unique index, as | | | in the EFMCu PHY MUST have a unique index, as |
skipping to change at page 9, line 45 skipping to change at page 10, line 42
described in HDSL2-SHDSL-LINE-MIB [RFC4319]. Note that not all described in HDSL2-SHDSL-LINE-MIB [RFC4319]. Note that not all
attributes of G.SHDSL modems reflected in HDSL2-SHDSL-LINE-MIB have attributes of G.SHDSL modems reflected in HDSL2-SHDSL-LINE-MIB have
adequate management objects (Clause 30 attributes and Clause 45 adequate management objects (Clause 30 attributes and Clause 45
registers) in the EFM standard. registers) in the EFM standard.
Because of these differences and for the purposes of simplicity, Because of these differences and for the purposes of simplicity,
unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs
and name consistency (e.g. prefixing the 2BASE-TL PME related objects and name consistency (e.g. prefixing the 2BASE-TL PME related objects
with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided not to with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided not to
reference HDSL2-SHDSL-LINE-MIB objects, but define all the relevant reference HDSL2-SHDSL-LINE-MIB objects, but define all the relevant
objects in this MIB module. objects in the EFM-CU-MIB module.
However, if some functionality, not available in this MIB module, is However, if some functionality, not available in the EFM-CU-MIB
required and supported by the PME, e.g. performance monitoring, module, is required and supported by the PME, e.g. performance
relevant HDSL2-SHDSL-LINE-MIB groups MAY be included and applied for monitoring, relevant HDSL2-SHDSL-LINE-MIB groups MAY be included and
PMEs of 2BASE-TL subtype. applied for PMEs of 2BASE-TL subtype.
3.3. Relation to VDSL MIB module 3.3. Relation to VDSL MIB module
VDSL (DMT) modems, similar to the PME(s) comprising a 10PASS-TS port, VDSL (DMT) modems, similar to the PME(s) comprising a 10PASS-TS port,
are described in VDSL-LINE-EXT-MCM-MIB [RFC4070]. Note that not all are described in VDSL-LINE-EXT-MCM-MIB [RFC4070]. Note that not all
attributes of VDSL modems reflected in VDSL-LINE-EXT-MCM-MIB have attributes of VDSL modems reflected in VDSL-LINE-EXT-MCM-MIB have
adequate management objects (Clause 30 attributes and Clause 45 adequate management objects (Clause 30 attributes and Clause 45
registers) in the EFM standard. registers) in the EFM standard.
Because of these differences and for the purposes of simplicity, Because of these differences and for the purposes of simplicity,
unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs
and name consistency, it was decided not to reference VDSL-LINE-EXT- and name consistency, it was decided not to reference VDSL-LINE-EXT-
MCM-MIB objects, but define all the relevant objects in this MIB MCM-MIB objects, but define all the relevant objects in the EFM-CU-
module. MIB module.
However, if some functionality, not available in this MIB module, is However, if some functionality, not available in the EFM-CU-MIB
required and supported by the PME, relevant VDSL-LINE-EXT-MCM-MIB module, is required and supported by the PME, relevant VDSL-LINE-EXT-
groups MAY be included and applied for PMEs of 10PASS-TS subtype. MCM-MIB groups MAY be included and applied for PMEs of 10PASS-TS
subtype.
3.4. Relation to Ethernet-Like and MAU MIB modules 3.4. Relation to Ethernet-Like and MAU MIB modules
The implementation of EtherLike-MIB [RFC3635] and MAU-MIB [I-D.ietf- The implementation of EtherLike-MIB [RFC3635] and MAU-MIB [I-D.ietf-
hubmib-rfc3636bis] is REQUIRED for the EFMCu interfaces. hubmib-rfc3636bis] is REQUIRED for the EFMCu interfaces.
Two new values of ifMauType (OBJECT-IDENTITIES of dot3MauType) and Two new values of ifMauType (OBJECT-IDENTITIES of dot3MauType) and
corresponding bit definitions of ifMauTypeListBits corresponding bit definitions of ifMauTypeListBits
(IANAifMauTypeListBits) have been defined in the IANA-MAU-MIB (IANAifMauTypeListBits) have been defined in the IANA-MAU-MIB
[I-D.ietf-hubmib-rfc3636bis] for the EFMCu MAUs: [I-D.ietf-hubmib-rfc3636bis] for the EFMCu MAUs:
skipping to change at page 11, line 20 skipping to change at page 12, line 17
o pmdLinkFault - a link fault is detected at the receive direction o pmdLinkFault - a link fault is detected at the receive direction
by all PMEs in the aggregation group by all PMEs in the aggregation group
As an EtherLike interface every EFMCu port (an ifEntry representing a As an EtherLike interface every EFMCu port (an ifEntry representing a
consolidation of LLC, MAC and PCS (sub)layers) SHALL return an ifType consolidation of LLC, MAC and PCS (sub)layers) SHALL return an ifType
of ethernetCsmacd(6). While most of the MAU characteristics are not of ethernetCsmacd(6). While most of the MAU characteristics are not
applicable to the EFMCu ports (no auto-negotiation, false carriers or applicable to the EFMCu ports (no auto-negotiation, false carriers or
jabber), they SHALL return an appropriate ifMauType jabber), they SHALL return an appropriate ifMauType
(dot3MauType2BaseTL or dot3mauType10PassTS) in order to direct the (dot3MauType2BaseTL or dot3mauType10PassTS) in order to direct the
management software to look in the EFM-CU-MIB for the desired management software to look in the EFM-CU-MIB module for the desired
information. For example the information on the particular EFMCu information. For example the information on the particular EFMCu
flavor that an EFMCu port is running is available from flavor that an EFMCu port is running is available from
efmCuOperSubType, defined in this MIB module. efmCuOperSubType, defined in the EFM-CU-MIB module.
Since EFMCu PMEs are not EtherLike interfaces, they cannot be Since EFMCu PMEs are not EtherLike interfaces, they cannot be
instantiated as MAU interface objects. instantiated as MAU interface objects.
4. MIB Structure 4. MIB Structure
4.1. Overview 4.1. EFM Copper MIB Overview
The main management objects defined in this MIB module are split into The main management objects defined in the EFM-CU-MIB module are
2 groups: split into 2 groups:
o efmCuPort - containing objects for configuration, capabilities, o efmCuPort - containing objects for configuration, capabilities,
status and notifications, common to all EFMCu PHYs. status and notifications, common to all EFMCu PHYs.
o efmCuPme - containing objects for configuration, capabilities, o efmCuPme - containing objects for configuration, capabilities,
status and notifications of EFMCu PMEs. status and notifications of EFMCu PMEs.
In addition the ifAvailableStackTable is defined at the same level.
The efmCuPme group in turn contains efmCuPme2B and efmCuPme10P The efmCuPme group in turn contains efmCuPme2B and efmCuPme10P
groups, which define PME Profiles specific to 2BASE-TL and 10PASS-TS groups, which define PME Profiles specific to 2BASE-TL and 10PASS-TS
PMEs respectively, as well as PME specific status information. PMEs respectively, as well as PME specific status information.
4.2. PME Profiles 4.2. Interface stack capability MIB Overview
The IF-CAP-STACK-MIB module contains 2 tables:
o ifCapStackTable - containing objects that define possible
relationships among the sub-layers of an interface with flexible
cross-connect (cross-connect capability).
o ifInvCapStackTable - an inverse of the ifCapstackTable.
4.3. PME Profiles
Since a managed node can have a large number of EFMCu PHYs, 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, the
MIB module makes use of configuration profiles, similar to HDSL2- EFM-CU-MIB module makes use of configuration profiles, similar to
SHDSL-LINE-MIB and VDSL-LINE-EXT-MCM-MIB. A profile is a set of HDSL2-SHDSL-LINE-MIB and VDSL-LINE-EXT-MCM-MIB. A profile is a set
parameters, used either for configuration or representation of a PME. of parameters, used either for configuration or representation of a
The same profile can be shared by multiple PME ports, using the same PME. The same profile can be shared by multiple PME ports, using the
configuration. same configuration.
The PME profiles are defined in efmCuPme2BProfileTable and The PME profiles are defined in efmCuPme2BProfileTable and
efmCu10PProfileTable for 2BASE-TL and 10PASS-TS PMEs respectively. efmCu10PProfileTable for 2BASE-TL and 10PASS-TS PMEs respectively.
There are 12 predefined standard profiles for 2BASE-TL and 22 There are 12 predefined standard profiles for 2BASE-TL and 22
standard profiles for 10PASS-TS, defined in 802.3ah and dedicated for standard profiles for 10PASS-TS, defined in 802.3ah and dedicated for
rapid provisioning of EFMCu PHYs in most scenarios. In addition this rapid provisioning of EFMCu PHYs in most scenarios. In addition the
MIB defines two additional predefined profiles for "best-effort" EFM-CU-MIB defines two additional predefined profiles for "best-
provisioning of 2BASE-TL PMEs. An ability to define new effort" provisioning of 2BASE-TL PMEs. An ability to define new
configuration profiles is also provided to allow for EFMCu deployment configuration profiles is also provided to allow for EFMCu deployment
tailored to specific copper environment and spectral regulations. tailored to specific copper environment and spectral regulations.
A specific configuration or administrative profile is assigned to a A specific configuration or administrative profile is assigned to a
specific PME via efmCuPmeAdminProfile object. If specific PME via efmCuPmeAdminProfile object. If
efmCuPmeAdminProfile is zero, then efmCuAdminProfile object of the efmCuPmeAdminProfile is zero, then efmCuAdminProfile object of the
PCS port, connected to the PME, determines the configuration profile PCS port, connected to the PME, determines the configuration profile
(or a list of possible profiles) for that PME. This mechanism allows (or a list of possible profiles) for that PME. This mechanism allows
to specify a common profile(s) for all PMEs connected to the PCS to specify a common profile(s) for all PMEs connected to the PCS
port, with an ability to change individual PME profiles by setting port, with an ability to change individual PME profiles by setting
efmCuPmeAdminProfile object, which overwrites profile set by efmCuPmeAdminProfile object, which overwrites profile set by
efmCuAdminProfile. efmCuAdminProfile.
A current operating PME profile is pointed to by efmCuPmeOperProfile A current operating PME profile is pointed to by efmCuPmeOperProfile
object. Note that this profile entry, can be created automatically, object. Note that this profile entry, can be created automatically,
to reflect achieved parameters in adaptive (not fixed) to reflect achieved parameters in adaptive (not fixed)
initialization. initialization.
4.3. Mapping of IEEE 802.3ah Managed Objects 4.4. Mapping of IEEE 802.3ah Managed Objects
This section contains the mapping between relevant managed objects This section contains the mapping between relevant managed objects
(attributes) defined in [802.3ah] Clause 30, and managed objects (attributes) defined in [802.3ah] Clause 30, and managed objects
defined in this document and in associated MIB modules, i.e., the IF- defined in this document and in associated MIB modules, i.e., the IF-
MIB [RFC2863]. MIB [RFC2863].
Note that majority of the objects defined in this MIB module do not Note that majority of the objects defined in the EFM-CU-MIB module do
have direct counterparts in Clause 30 and instead refer to Clause 45 not have direct counterparts in Clause 30 and instead refer to Clause
registers. 45 registers.
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| IEEE 802.3 Managed Object | Corresponding SNMP Object | | IEEE 802.3 Managed Object | Corresponding SNMP Object |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| oMAU - Basic Package | | | oMAU - Basic Package | |
| (Mandatory) | | | (Mandatory) | |
| aMAUType | ifMauType (MAU-MIB) | | aMAUType | ifMauType (MAU-MIB) |
| aMAUTypeList | ifMauTypeListBits (MAU-MIB) | | aMAUTypeList | ifMauTypeListBits (MAU-MIB) |
| aMediaAvailable | ifMediaAvailable (MAU-MIB) | | aMediaAvailable | ifMediaAvailable (MAU-MIB) |
| oPAF - Basic Package | | | oPAF - Basic Package | |
| (Mandatory) | | | (Mandatory) | |
| aPAFID | ifIndex (IF-MIB) | | aPAFID | ifIndex (IF-MIB) |
| aPhyEnd | efmCuPhySide | | aPhyEnd | efmCuPhySide |
| aPHYCurrentStatus | efmCuStatus | | aPHYCurrentStatus | efmCuStatus |
| aPAFSupported | efmCuPAFSupported | | aPAFSupported | efmCuPAFSupported |
| oPAF - PME Aggregation Package | | | oPAF - PME Aggregation Package | |
| (Optional) | | | (Optional) | |
| aPAFAdminState | efmCuPAFAdminState | | aPAFAdminState | efmCuPAFAdminState |
| aLocalPAFCapacity | efmCuPAFCapacity | | aLocalPAFCapacity | efmCuPAFCapacity |
| aLocalPMEAvailable | ifAvailableStackTable | | aLocalPMEAvailable | ifCapStackTable |
| aLocalPMEAggregate | ifStackTable (IF-MIB) | | aLocalPMEAggregate | ifStackTable (IF-MIB) |
| aRemotePAFSupported | efmCuRemotePAFSupported | | aRemotePAFSupported | efmCuRemotePAFSupported |
| aRemotePAFCapacity | efmCuRemotePAFCapacity | | aRemotePAFCapacity | efmCuRemotePAFCapacity |
| 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 |
skipping to change at page 13, line 45 skipping to change at page 14, line 46
| aTCCRCErrors | efmCuPmeTCCrcErrors | | aTCCRCErrors | efmCuPmeTCCrcErrors |
| aProfileSelect | efmCuAdminProfile, | | aProfileSelect | efmCuAdminProfile, |
| | efmCuPmeAdminProfile | | | efmCuPmeAdminProfile |
| aOperatingProfile | efmCuPmeOperProfile | | aOperatingProfile | efmCuPmeOperProfile |
| aPMEFECCorrectedBlocks | efmCuPme10PFECCorrectedBlocks | | aPMEFECCorrectedBlocks | efmCuPme10PFECCorrectedBlocks |
| aPMEFECUncorrectableBlocks | efmCuPme10PFECUncorrectedBlocks | | aPMEFECUncorrectableBlocks | efmCuPme10PFECUncorrectedBlocks |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
Table 2 Table 2
5. Definitions 5. Interface Stack Capability MIB Definitions
IF-CAP-STACK-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2
FROM SNMPv2-SMI -- RFC 2578
RowStatus
FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- RFC 2580
ifStackGroup2, ifStackHigherLayer, ifStackLowerLayer
FROM IF-MIB -- RFC 2863
;
ifCapStackMIB MODULE-IDENTITY
LAST-UPDATED "200610120000Z" -- October 12, 2006
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group"
CONTACT-INFO
"WG charter:
http://www.ietf.org/html.charters/hubmib-charter.html
Mailing Lists:
General Discussion: hubmib@ietf.org
To Subscribe: hubmib-request@ietf.org
In Body: subscribe your_email_address
Chair: Dan Romascanu
Postal: Avaya
Atidim Technology Park, Bldg. 3
Tel Aviv 61131
Israel
Tel: +972 3 645 8414
E-mail: dromasca@avaya.com
Editor: Edward Beili
Postal: Actelis Networks Inc.
25 Bazel St., P.O.B. 10173
Petach-Tikva 10173
Israel
Tel: +972-3-924-3491
E-mail: edward.beili@actelis.com"
DESCRIPTION
"The objects in this MIB module are used to describe
cross-connect capabilities of stacked (layered) interfaces,
complementing ifStackTable and ifInvStackTable defined in
IF-MIB and IF-INVERTED-STACK-MIB respectively.
Copyright (C) The Internet Society (2006). This version
of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices."
REVISION "200610120000Z" -- October 12, 2006
DESCRIPTION "Initial version, published as RFC XXXX."
-- EdNote: Replace XXXX with the actual RFC number &
-- remove this note
::= { mib-2 ZZZ }
-- EdNote: Replace ZZZ with a real OID once it is
-- allocated & remove this note.
-- Sections of the module
ifCapStackObjects OBJECT IDENTIFIER ::= { ifCapStackMIB 1 }
-- Groups in the module
--
-- ifCapStackTable group
--
ifCapStackTable OBJECT-TYPE
SYNTAX SEQUENCE OF IfCapStackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table, modeled after ifStackTable from IF-MIB,
contains information on the possible 'on-top-of'
relationships between the multiple sub-layers of network
interfaces (as opposed to actual relationships described in
ifStackTable). In particular, it contains information on
which sub-layers MAY possibly run 'on top of' which other
sub-layers, as determined by cross-connect capability of the
device, where each sub-layer corresponds to a conceptual row
in the ifTable. For example, when the sub-layer with ifIndex
value x can be connected to run on top of the sub-layer with
ifIndex value y, then this table contains:
ifCapStackStatus.x.y=active
Note that for most stacked interfaces (e.g. 2BASE-TL)
there's always at least one higher-level interface (e.g. PCS
port) for each lower-level interface (e.g. PME) and at
least one lower-level interface for each higher-level
interface, that is, there is at least a single 'active' row
for any existing value of x or y.
This table is read only as it describes device capability"
REFERENCE
"IF-MIB, ifStackTable"
::= { ifCapStackObjects 1 }
ifCapStackEntry OBJECT-TYPE
SYNTAX IfCapStackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information on a particular relationship between two
sub-layers, specifying that one sub-layer runs on 'top' of the
other sub-layer. Each sub-layer corresponds to a conceptual
row in the ifTable (interface index for lower- and
higher-layer respectively)."
INDEX {
ifStackHigherLayer,
ifStackLowerLayer
}
::= { ifCapStackTable 1 }
IfCapStackEntry ::= SEQUENCE {
ifCapStackStatus RowStatus
}
ifCapStackStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The status of the 'cross-connect capability' relationship
between two sub-layers. The following values can be returned:
active(1) - indicates that the sub-layer interface,
identified by the ifStackLowerLayer MAY
be connected to run 'below' the sub-layer
interface, identified by the
ifStackHigherLayer index.
notInService(2) - the sub-layer interfaces cannot be
connected temporarily due to
unavailability of the interface(s), e.g.
one of the interfaces is located on a
pluggable module which is absent.
Note that lower-layer interface availability per higher-layer,
indicated by the value of 'active', can be constrained by
other parameters, for example by the aggregation capacity of
a higher-layer interface or by the lower-layer interface in
question being already connected to another higher-layer
interface. In order to ensure that a particular sub-layer can
be connected to another sub-layer, all respective objects
(e.g. ifCapStackTable, ifStackTable and efmCuPAFCapacity for
for EFMCu interfaces) SHALL be inspected.
This object is read only, unlike ifStackStatus, as it
describes a cross-connect capability."
::= { ifCapStackEntry 1 }
ifInvCapStackTable OBJECT-TYPE
SYNTAX SEQUENCE OF IfInvCapStackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing information on the possible relationships
between the multiple sub-layers of network interfaces. This
table, modeled after ifInvStackTable from
IF-INVERTED-STACK-MIB, is an inverse of the ifCapStackTable
defined in this MIB module.
In particular, this table contains information on which
sub-layers MAY run 'underneath' which other sub-layers, where
each sub-layer corresponds to a conceptual row in the ifTable.
For example, when the sub-layer with ifIndex value x MAY be
connected to run underneath the sub-layer with ifIndex value
y, then this table contains:
ifInvCapStackStatus.x.y=active
This table contains exactly the same number of rows as the
ifCapStackTable, but the rows appear in a different order.
This table is read only as it describes a cross-connect
capability."
REFERENCE
"IF-INVERTED-STACK-MIB, ifInvStackTable"
::= { ifCapStackObjects 2 }
ifInvCapStackEntry OBJECT-TYPE
SYNTAX IfInvCapStackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information on a particular relationship between two sub-
layers, specifying that one sub-layer MAY run underneath the
other sub-layer. Each sub-layer corresponds to a conceptual
row in the ifTable."
INDEX { ifStackLowerLayer, ifStackHigherLayer }
::= { ifInvCapStackTable 1 }
IfInvCapStackEntry ::= SEQUENCE {
ifInvCapStackStatus RowStatus
}
ifInvCapStackStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The status of the possible relationship between two
sub-layers.
An instance of this object exists for each instance of the
ifCapStackStatus object, and vice versa. For example, if the
variable ifCapStackStatus.H.L exists, then the variable
ifInvStackStatus.L.H must also exist, and vice versa. In
addition, the two variables always have the same value.
The ifInvStackStatus object is read-only, as it describes
a cross-connect capability."
::= { ifInvCapStackEntry 1 }
--
-- ifCapStackConformance group
--
ifCapStackConformance OBJECT IDENTIFIER
::= { ifCapStackObjects 3 }
-- Conformance Statements
ifCapStackGroups OBJECT IDENTIFIER ::=
{ ifCapStackConformance 1 }
ifCapStackCompliances OBJECT IDENTIFIER ::=
{ ifCapStackConformance 2 }
-- Units of Conformance
ifCapStackGroup OBJECT-GROUP
OBJECTS {
ifCapStackStatus,
ifInvCapStackStatus
}
STATUS current
DESCRIPTION
"A collection of objects providing information on the
cross-connect capability of multi-layer (stacked) network
interfaces."
::= { ifCapStackGroups 1 }
-- Compliance Statements
ifCapStackCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities, which provide
information on the cross-connect capability of multi-layer
(stacked) network interfaces, with flexible cross-connect
between the sub-layers.
Compliance with the following external compliance statements
is REQUIRED:
MIB Module Compliance Statement
---------- --------------------
IF-MIB ifCompliance3
IF-INVERTED-STACK-MIB ifInvCompliance"
MODULE -- this module
MANDATORY-GROUPS {
ifCapStackGroup
}
OBJECT ifCapStackStatus
SYNTAX INTEGER { active(1) }
DESCRIPTION
"Support for the notInService(2) value is OPTIONAL for
implementations supporting pluggable interfaces."
OBJECT ifInvCapStackStatus
SYNTAX INTEGER { active(1) }
DESCRIPTION
"Support for the notInService(2) value is OPTIONAL for
implementations supporting pluggable interfaces."
MODULE IF-MIB
MANDATORY-GROUPS {
ifStackGroup2
}
MODULE IF-INVERTED-STACK-MIB
MANDATORY-GROUPS {
ifInvStackGroup
}
::= { ifCapStackCompliances 1 }
END
6. EFM Copper MIB 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 -- RFC 2578 FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress
FROM SNMPv2-TC -- RFC 2579 FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- RFC 2580
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC 3411 FROM SNMP-FRAMEWORK-MIB -- RFC 3411
ifIndex, ifSpeed, InterfaceIndex ifIndex, ifSpeed
FROM IF-MIB -- RFC 2863 FROM IF-MIB -- RFC 2863
; ;
efmCuMIB MODULE-IDENTITY efmCuMIB MODULE-IDENTITY
LAST-UPDATED "200606170000Z" -- June 17, 2006 LAST-UPDATED "200610120000Z" -- October 12, 2006
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 16, line 4 skipping to change at page 23, line 18
PCS - Physical Coding Sublayer PCS - Physical Coding Sublayer
PMD - Physical Medium Dependent PMD - Physical Medium Dependent
PME - Physical Medium Entity PME - Physical Medium Entity
PSD - Power Spectral Density PSD - Power Spectral Density
SNR - Signal to Noise Ratio SNR - Signal to Noise Ratio
TCPAM - Trellis Coded Pulse Amplitude Modulation TCPAM - Trellis Coded Pulse Amplitude Modulation
Copyright (C) The Internet Society (2006). This version Copyright (C) The Internet Society (2006). This version
of this MIB module is part of RFC XXXX; see the RFC of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices." itself for full legal notices."
REVISION "200606170000Z" -- June 17, 2006
REVISION "200610120000Z" -- October 12, 2006
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
-- EdNote: Replace XXXX with the actual RFC number & -- EdNote: Replace XXXX with the actual RFC number &
-- remove this note -- remove this note
::= { mib-2 YYY } ::= { mib-2 YYY }
-- EdNote: Replace YYY with a real OID once it is -- EdNote: Replace YYY with a real OID once it is
-- allocated & remove this note. -- allocated & remove this note.
skipping to change at page 29, line 36 skipping to change at page 36, line 50
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of fragments that have been received across the "A number of fragments that have been received across the
gamma interface with RxErr asserted and discarded. gamma interface with RxErr asserted and discarded.
This read-only counter is inactive (not incremented) when the This read-only counter is inactive (not incremented) when the
PAF is unsupported or disabled. Upon disabling the PAF, the PAF is unsupported or disabled. Upon disabling the PAF, the
counter retains its previous value. counter retains its previous value.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the 10P/2B PAF RX error register." this object maps to the 10P/2B PAF RX error register.
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.21" "[802.3ah] 45.2.3.21"
::= { efmCuPortStatusEntry 4 } ::= { efmCuPortStatusEntry 4 }
efmCuPAFInSmallFragments OBJECT-TYPE efmCuPAFInSmallFragments OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of fragments smaller than minFragmentSize "A number of fragments smaller than minFragmentSize
(64 Bytes), which have been received across the gamma (64 Bytes), which have been received across the gamma
interface and discarded. interface and discarded.
This read-only counter is inactive when the PAF is This read-only counter is inactive when the PAF is
unsupported or disabled. Upon disabling the PAF, the counter unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value. retains its previous value.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the 10P/2B PAF small fragments this object maps to the 10P/2B PAF small fragments
register." register.
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.22" "[802.3ah] 45.2.3.22"
::= { efmCuPortStatusEntry 5 } ::= { efmCuPortStatusEntry 5 }
efmCuPAFInLargeFragments OBJECT-TYPE efmCuPAFInLargeFragments OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of fragments larger than maxFragmentSize "A number of fragments larger than maxFragmentSize
(512 Bytes), which have been received across the gamma (512 Bytes), which have been received across the gamma
interface and discarded. interface and discarded.
This read-only counter is inactive when the PAF is This read-only counter is inactive when the PAF is
unsupported or disabled. Upon disabling the PAF, the counter unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value. retains its previous value.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the 10P/2B PAF large fragments this object maps to the 10P/2B PAF large fragments
register." register.
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.23" "[802.3ah] 45.2.3.23"
::= { efmCuPortStatusEntry 6 } ::= { efmCuPortStatusEntry 6 }
efmCuPAFInBadFragments OBJECT-TYPE efmCuPAFInBadFragments OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of fragments which do not fit into the sequence "A number of fragments which do not fit into the sequence
expected by the frame assembly function, that have been expected by the frame assembly function, that have been
received across the gamma interface and discarded (the received across the gamma interface and discarded (the
frame buffer is flushed to the next valid frame start). frame buffer is flushed to the next valid frame start).
This read-only counter is inactive when the PAF is This read-only counter is inactive when the PAF is
unsupported or disabled. Upon disabling the PAF, the counter unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value. retains its previous value.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the 10P/2B PAF bad fragments this object maps to the 10P/2B PAF bad fragments
register." register.
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.25" "[802.3ah] 45.2.3.25"
::= { efmCuPortStatusEntry 7 } ::= { efmCuPortStatusEntry 7 }
efmCuPAFInLostFragments OBJECT-TYPE efmCuPAFInLostFragments OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of gaps in the sequence of fragments, which have "A number of gaps in the sequence of fragments, which have
been received across the gamma interface (the frame buffer is been received across the gamma interface (the frame buffer is
flushed to the next valid frame start, when fragment/fragments flushed to the next valid frame start, when fragment/fragments
expected by the frame assembly function is/are not received). expected by the frame assembly function is/are not received).
This read-only counter is inactive when the PAF is This read-only counter is inactive when the PAF is
unsupported or disabled. Upon disabling the PAF, the counter unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value. retains its previous value.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the 10P/2B PAF lost fragment this object maps to the 10P/2B PAF lost fragment
register." register.
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.26" "[802.3ah] 45.2.3.26"
::= { efmCuPortStatusEntry 8 } ::= { efmCuPortStatusEntry 8 }
efmCuPAFInLostStarts OBJECT-TYPE efmCuPAFInLostStarts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of missing StartOfPacket indicators expected by the "A number of missing StartOfPacket indicators expected by the
frame assembly function. frame assembly function.
This read-only counter is inactive when the PAF is This read-only counter is inactive when the PAF is
unsupported or disabled. Upon disabling the PAF, the counter unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value. retains its previous value.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the 10P/2B PAF lost start of fragment this object maps to the 10P/2B PAF lost start of fragment
register." register.
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.27" "[802.3ah] 45.2.3.27"
::= { efmCuPortStatusEntry 9 } ::= { efmCuPortStatusEntry 9 }
efmCuPAFInLostEnds OBJECT-TYPE efmCuPAFInLostEnds OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of missing EndOfPacket indicators expected by the "A number of missing EndOfPacket indicators expected by the
frame assembly function. frame assembly function.
This read-only counter is inactive when the PAF is This read-only counter is inactive when the PAF is
unsupported or disabled. Upon disabling the PAF, the counter unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value. retains its previous value.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the 10P/2B PAF lost start of fragment this object maps to the 10P/2B PAF lost start of fragment
register." register.
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.28" "[802.3ah] 45.2.3.28"
::= { efmCuPortStatusEntry 10 } ::= { efmCuPortStatusEntry 10 }
efmCuPAFInOverflows OBJECT-TYPE efmCuPAFInOverflows OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of fragments, received across the gamma interface "A number of fragments, received across the gamma interface
and discarded, which would have caused the frame assembly and discarded, which would have caused the frame assembly
buffer to overflow. buffer to overflow.
This read-only counter is inactive when the PAF is This read-only counter is inactive when the PAF is
unsupported or disabled. Upon disabling the PAF, the counter unsupported or disabled. Upon disabling the PAF, the counter
retains its previous value. retains its previous value.
If a Clause 45 MDIO Interface to the PCS is present, then If a Clause 45 MDIO Interface to the PCS is present, then
this object maps to the 10P/2B PAF overflow register." this object maps to the 10P/2B PAF overflow register.
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 45.2.3.24" "[802.3ah] 45.2.3.24"
::= { efmCuPortStatusEntry 11 } ::= { efmCuPortStatusEntry 11 }
-- PME Notifications Group -- PME Notifications Group
efmCuPmeNotifications OBJECT IDENTIFIER ::= { efmCuPme 0 } efmCuPmeNotifications OBJECT IDENTIFIER ::= { efmCuPme 0 }
efmCuPmeLineAtnCrossing NOTIFICATION-TYPE efmCuPmeLineAtnCrossing NOTIFICATION-TYPE
OBJECTS { OBJECTS {
skipping to change at page 48, line 5 skipping to change at page 56, line 10
::= { efmCuPmeStatusEntry 9 } ::= { efmCuPmeStatusEntry 9 }
efmCuPmeTCCodingErrors OBJECT-TYPE efmCuPmeTCCodingErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of 64/65-octet encapsulation errors. This counter is "A number of 64/65-octet encapsulation errors. This counter is
incremented for each 64/65-octet encapsulation error detected incremented for each 64/65-octet encapsulation error detected
by the 64/65-octet receive function. by the 64/65-octet receive function.
The value of zero SHALL be returned when PME is down or
initializing. This object maps to aTCCodingViolations attribute in
clause 30.
If a Clause 45 MDIO Interface to the PME TC is present, then If a Clause 45 MDIO Interface to the PME TC is present, then
this object maps to the TC coding violations register this object maps to the TC coding violations register
(see 45.2.6.12)." (see 45.2.6.12).
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 61.3.3.1, 45.2.6.12" "[802.3ah] 61.3.3.1, 30.11.2.1.5, 45.2.6.12"
::= { efmCuPmeStatusEntry 10 } ::= { efmCuPmeStatusEntry 10 }
efmCuPmeTCCrcErrors OBJECT-TYPE efmCuPmeTCCrcErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number of TC-CRC errors. This counter is incremented for "A number of TC-CRC errors. This counter is incremented for
each TC-CRC error detected by the 64/65-octet receive function each TC-CRC error detected by the 64/65-octet receive function
(see 61.3.3.3 and Figure 61-19). (see 61.3.3.3 and Figure 61-19).
The value of zero SHALL be returned when PME is down or
initializing. This object maps to aTCCRCErrors attribute in
clause 30.
If a Clause 45 MDIO Interface to the PCME TC is present, then If a Clause 45 MDIO Interface to the PCME TC is present, then
this object maps to the TC CRC error register this object maps to the TC CRC error register
(see 45.2.6.11)." (see 45.2.6.11).
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 61.3.3.3, 45.2.6.11" "[802.3ah] 61.3.3.3, 30.11.2.1.10, 45.2.6.11"
::= { efmCuPmeStatusEntry 11 } ::= { efmCuPmeStatusEntry 11 }
-- 2BASE-TL specific PME group -- 2BASE-TL specific PME group
efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 } efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 }
efmCuPme2BProfileTable OBJECT-TYPE efmCuPme2BProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme2BProfileEntry SYNTAX SEQUENCE OF EfmCuPme2BProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table supports definitions of administrative and "This table supports definitions of administrative and
operating Profiles for 2BASE-TL PMEs. operating Profiles for 2BASE-TL PMEs.
First 14 entries in this table SHALL always be defined as First 14 entries in this table SHALL always be defined as
skipping to change at page 57, line 35 skipping to change at page 66, line 5
- maximum data rate for a given encoding specified in the - maximum data rate for a given encoding specified in the
efmCuPme2BsModeEntry, corresponding to the equivalent loop efmCuPme2BsModeEntry, corresponding to the equivalent loop
length, estimated by the PME. length, estimated by the PME.
It is RECOMMENDED that the efmCuPme2BEquivalentLength values It is RECOMMENDED that the efmCuPme2BEquivalentLength values
are assigned in the increasing order, starting from the are assigned in the increasing order, starting from the
minimum value. minimum value.
Entries may be created/deleted using the row creation/ Entries may be created/deleted using the row creation/
deletion mechanism via efmCuPme2ReachRateRowStatus." deletion mechanism via efmCuPme2ReachRateRowStatus."
INDEX { efmCuPme2BsModeIndex, efmCuPme2BEquivalentLength } INDEX { efmCuPme2BsModeIndex, efmCuPme2BReachRateIndex }
::= { efmCuPme2BReachRateTable 1 } ::= { efmCuPme2BReachRateTable 1 }
EfmCuPme2BReachRateEntry ::= EfmCuPme2BReachRateEntry ::=
SEQUENCE { SEQUENCE {
efmCuPme2BReachRateIndex ProfileIndex,
efmCuPme2BEquivalentLength Unsigned32, efmCuPme2BEquivalentLength Unsigned32,
efmCuPme2BMaxDataRatePam16 Unsigned32, efmCuPme2BMaxDataRatePam16 Unsigned32,
efmCuPme2BMaxDataRatePam32 Unsigned32, efmCuPme2BMaxDataRatePam32 Unsigned32,
efmCuPme2BReachRateRowStatus RowStatus efmCuPme2BReachRateRowStatus RowStatus
} }
efmCuPme2BReachRateIndex OBJECT-TYPE
SYNTAX ProfileIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"2BASE-TL custom spectral mode Reach-Rate table index.
This object is the unique index associated with each enry."
::= { efmCuPme2BReachRateEntry 1 }
efmCuPme2BEquivalentLength OBJECT-TYPE efmCuPme2BEquivalentLength OBJECT-TYPE
SYNTAX Unsigned32(0..8192) SYNTAX Unsigned32(0..8192)
UNITS "m" UNITS "m"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Maximum allowed Equivalent loop's Physical Length in meters "Maximum allowed Equivalent loop's Physical Length in meters
for the specified data rates. for the specified data rates.
An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a
perfect square root attenuation characteristic, without any perfect square root attenuation characteristic, without any
bridged taps." bridged taps."
REFERENCE ::= { efmCuPme2BReachRateEntry 2 }
""
::= { efmCuPme2BReachRateEntry 1 }
efmCuPme2BMaxDataRatePam16 OBJECT-TYPE efmCuPme2BMaxDataRatePam16 OBJECT-TYPE
SYNTAX Unsigned32(0|192..5696) SYNTAX Unsigned32(0|192..5696)
UNITS "Kbps" UNITS "Kbps"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Maximum data rate for 2BASE-TL PME at the specified "Maximum data rate for 2BASE-TL PME at the specified
Equivalent loop's Length using TC-PAM16 encoding. Equivalent loop's Length using TC-PAM16 encoding.
The value of zero means that TC-PAM16 encoding should not be The value of zero means that TC-PAM16 encoding should not be
used at this distance." used at this distance."
REFERENCE ::= { efmCuPme2BReachRateEntry 3 }
""
::= { efmCuPme2BReachRateEntry 2 }
efmCuPme2BMaxDataRatePam32 OBJECT-TYPE efmCuPme2BMaxDataRatePam32 OBJECT-TYPE
SYNTAX Unsigned32(0|192..5696) SYNTAX Unsigned32(0|192..5696)
UNITS "Kbps" UNITS "Kbps"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Maximum data rate for 2BASE-TL PME at the specified "Maximum data rate for 2BASE-TL PME at the specified
Equivalent loop's Length using TC-PAM32 encoding. Equivalent loop's Length using TC-PAM32 encoding.
The value of zero means that TC-PAM32 encoding should not be The value of zero means that TC-PAM32 encoding should not be
used at this distance." used at this distance."
REFERENCE ::= { efmCuPme2BReachRateEntry 4 }
""
::= { efmCuPme2BReachRateEntry 3 }
efmCuPme2BReachRateRowStatus OBJECT-TYPE efmCuPme2BReachRateRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object controls creation/deletion of the associated "This object controls creation/deletion of the associated
entry in efmCuPme2BReachRateTable per the semantics of entry in efmCuPme2BReachRateTable per the semantics of
RowStatus. RowStatus.
If an 'active' entry is referenced via efmCuPme2BsMode, the If an 'active' entry is referenced via efmCuPme2BsMode, the
entry MUST remain 'active' until all references are removed." entry MUST remain 'active' until all references are removed."
::= { efmCuPme2BReachRateEntry 4 } ::= { efmCuPme2BReachRateEntry 5 }
-- 10PASS-TS specific PME group -- 10PASS-TS specific PME group
efmCuPme10P OBJECT IDENTIFIER ::= { efmCuPme 6 } efmCuPme10P OBJECT IDENTIFIER ::= { efmCuPme 6 }
efmCuPme10PProfileTable OBJECT-TYPE efmCuPme10PProfileTable OBJECT-TYPE
SYNTAX SEQUENCE OF EfmCuPme10PProfileEntry SYNTAX SEQUENCE OF EfmCuPme10PProfileEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table supports definitions of configuration profiles for "This table supports definitions of configuration profiles for
skipping to change at page 67, line 17 skipping to change at page 75, line 40
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
Discontinuities in the value of this counter can occur at
re-initialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime,
defined in IF-MIB."
REFERENCE REFERENCE
"[802.3ah] 45.2.1.22" "[802.3ah] 45.2.1.22, 30.11.2.1.8"
::= { efmCuPme10PStatusEntry 1 } ::= { efmCuPme10PStatusEntry 1 }
efmCuPme10PFECUncorrectedBlocks OBJECT-TYPE efmCuPme10PFECUncorrectedBlocks OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of received FEC codewords in 10PASS-TS PME, which are "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
"[802.3ah] 45.2.1.23"
::= { efmCuPme10PStatusEntry 2 }
-- ifAvailableStackTable for use in Discovery
ifAvailableStackTable OBJECT-TYPE
SYNTAX SEQUENCE OF IfAvailableStackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table, modeled after ifStackTable from IF-MIB,
contains information on the possible 'on-top-of'
relationships between the multiple sub-layers of network
interfaces (as opposed to actual relationships in
ifStackTable). In particular, it contains information on
which PCS ports (sublayers) can possibly run 'on top of'
which PMEs (sublayers), as determined by cross-connect
capability of the EFMCu device, where each sub-layer
corresponds to a conceptual row in the ifTable. For example,
when the PCS port with ifIndex value x can be connected
to run on top of the PME with ifIndex value y, then this table
contains:
ifAvailableStackStatus.x.y=capable
Note that there's always at least on PCS for each PME and at Discontinuities in the value of this counter can occur at
least one PME for each PCS in the EFMCu devices, with re-initialization of the management system, and at other times
efmCuPAFCapacity and efmCuPeerPAFCapacity indicating as indicated by the value of ifCounterDiscontinuityTime,
maximum number of PMEs which can be aggregated by local and defined in IF-MIB."
remote PCS port respectively.
This table is read only as it describes device capability"
REFERENCE REFERENCE
"IF-MIB, ifStackTable" "[802.3ah] 45.2.1.23, 30.11.2.1.9"
::= { efmCuObjects 3 } ::= { efmCuPme10PStatusEntry 2 }
ifAvailableStackEntry OBJECT-TYPE
SYNTAX IfAvailableStackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information on a particular relationship between two
sub-layers, specifying that one sub-layer (PCS) runs on 'top'
of the other sub-layer (PME). Each sub-layer corresponds to a
conceptual row in the ifTable (interface index for PCS and
PME respectively)."
INDEX {
ifAvailableStackHigherLayer,
ifAvailableStackLowerLayer
}
::= { ifAvailableStackTable 1 }
IfAvailableStackEntry ::=
SEQUENCE {
ifAvailableStackHigherLayer InterfaceIndex,
ifAvailableStackLowerLayer InterfaceIndex,
ifAvailableStackStatus INTEGER
}
ifAvailableStackHigherLayer OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The value of ifIndex corresponding to the higher sub-layer
of the 'cross-connect capability' relationship, i.e., the
PCS sub-layer which MAY run on 'top' of the PME sub-layer
identified by the corresponding instance of
ifAvailableStackLowerLayer."
::= { ifAvailableStackEntry 1 }
ifAvailableStackLowerLayer OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The value of ifIndex corresponding to the lower sub-layer
of the 'cross-connect capability' relationship, i.e., the
PME sub-layer which MAY run 'below' the PCS sub-layer
identified by the corresponding instance of
ifAvailableStackHigherLayer."
::= { ifAvailableStackEntry 2 }
ifAvailableStackStatus OBJECT-TYPE
SYNTAX INTEGER {
capable(1),
outOfService(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The status of the 'cross-connect capability' relationship
between two sub-layers. The following values are defined:
capable(1) - the PME sub-layer interface, identified by
the ifAvailableStackLowerLayer MAY be
connected to run 'below' the PCS sub-layer
interface, identified by the
ifAvailableStackLowerLayer.
outOfService(2) - the PME sub-layer interface cannot be
connected due to unavailability of the
interface.
Note that PME availability per PCS, indicated by 'capable'
value, can be constrained by other parameters,
for example by aggregation capacity of a PCS or by the PME in
question being already connected to another PCS. So, in
order to ensure that a particular PME can be connected to the
PCS, all respective parameters (e.g. ifAvailableStackTable,
ifStackTable and efmCuPAFCapacity) SHALL be inspected.
This object is read only, unlike ifStackStatus, as it
describes the device capability."
::= { 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 70, line 40 skipping to change at page 77, line 10
::= { efmCuGroups 1 } ::= { efmCuGroups 1 }
efmCuPAFGroup OBJECT-GROUP efmCuPAFGroup OBJECT-GROUP
OBJECTS { OBJECTS {
efmCuPeerPAFSupported, efmCuPeerPAFSupported,
efmCuPAFCapacity, efmCuPAFCapacity,
efmCuPeerPAFCapacity, efmCuPeerPAFCapacity,
efmCuPAFAdminState, efmCuPAFAdminState,
efmCuPAFDiscoveryCode, efmCuPAFDiscoveryCode,
efmCuPAFRemoteDiscoveryCode, efmCuPAFRemoteDiscoveryCode,
efmCuNumPMEs, efmCuNumPMEs
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 4 } ::= { efmCuGroups 3 }
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 72, line 5 skipping to change at page 78, line 11
efmCuPmeEquivalentLength, efmCuPmeEquivalentLength,
efmCuPmeTCCodingErrors, efmCuPmeTCCodingErrors,
efmCuPmeTCCrcErrors, efmCuPmeTCCrcErrors,
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 2BASE-TL/10PASS-TS PME." a 2BASE-TL/10PASS-TS PME."
::= { efmCuGroups 5 } ::= { efmCuGroups 4 }
efmCuAlarmConfGroup OBJECT-GROUP efmCuAlarmConfGroup OBJECT-GROUP
OBJECTS { OBJECTS {
efmCuThreshLowRate, efmCuThreshLowRate,
efmCuLowRateCrossingEnable, efmCuLowRateCrossingEnable,
efmCuPmeThreshLineAtn, efmCuPmeThreshLineAtn,
efmCuPmeLineAtnCrossingEnable, efmCuPmeLineAtnCrossingEnable,
efmCuPmeThreshSnrMgn, efmCuPmeThreshSnrMgn,
efmCuPmeSnrMgnCrossingEnable, efmCuPmeSnrMgnCrossingEnable,
efmCuPmeDeviceFaultEnable, efmCuPmeDeviceFaultEnable,
efmCuPmeConfigInitFailEnable, efmCuPmeConfigInitFailEnable,
efmCuPmeProtocolInitFailEnable efmCuPmeProtocolInitFailEnable
} }
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 6 } ::= { efmCuGroups 5 }
efmCuNotificationGroup NOTIFICATION-GROUP efmCuNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
efmCuLowRateCrossing, efmCuLowRateCrossing,
efmCuPmeLineAtnCrossing, efmCuPmeLineAtnCrossing,
efmCuPmeSnrMgnCrossing, efmCuPmeSnrMgnCrossing,
efmCuPmeDeviceFault, efmCuPmeDeviceFault,
efmCuPmeConfigInitFailure, efmCuPmeConfigInitFailure,
efmCuPmeProtocolInitFailure efmCuPmeProtocolInitFailure
-- 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 7 } ::= { efmCuGroups 6 }
efmCuPme2BProfileGroup OBJECT-GROUP efmCuPme2BProfileGroup OBJECT-GROUP
OBJECTS { OBJECTS {
efmCuPme2BProfileDescr, efmCuPme2BProfileDescr,
efmCuPme2BRegion, efmCuPme2BRegion,
efmCuPme2BsMode, efmCuPme2BsMode,
efmCuPme2BMinDataRate, efmCuPme2BMinDataRate,
efmCuPme2BMaxDataRate, efmCuPme2BMaxDataRate,
efmCuPme2BPower, efmCuPme2BPower,
efmCuPme2BConstellation, efmCuPme2BConstellation,
efmCuPme2BProfileRowStatus efmCuPme2BProfileRowStatus,
efmCuPme2BsModeDescr,
efmCuPme2BsModeRowStatus,
efmCuPme2BEquivalentLength,
efmCuPme2BMaxDataRatePam16,
efmCuPme2BMaxDataRatePam32,
efmCuPme2BReachRateRowStatus
} }
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 2BASE-TL ports." profile for configuration of 2BASE-TL ports."
::= { efmCuGroups 8 } ::= { efmCuGroups 7}
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 10PASS-TS ports." profile for configuration of 10PASS-TS ports."
::= { efmCuGroups 9 } ::= { efmCuGroups 8 }
efmCuPme10PStatusGroup OBJECT-GROUP efmCuPme10PStatusGroup OBJECT-GROUP
OBJECTS { OBJECTS {
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 10PASS-TS PMEs." specific to 10PASS-TS PMEs."
::= { efmCuGroups 10 } ::= { efmCuGroups 9 }
-- Compliance Statements -- Compliance Statements
efmCuCompliance MODULE-COMPLIANCE efmCuCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for 2BASE-TL/10PASS-TS 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 REQUIRED: is REQUIRED:
MIB Module Compliance Statement MIB Module Compliance Statement
---------- -------------------- ---------- --------------------
IF-MIB ifCompliance3 IF-MIB ifCompliance3
skipping to change at page 73, line 50 skipping to change at page 80, line 14
efmCuCompliance MODULE-COMPLIANCE efmCuCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for 2BASE-TL/10PASS-TS 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 REQUIRED: is REQUIRED:
MIB Module Compliance Statement MIB Module Compliance Statement
---------- -------------------- ---------- --------------------
IF-MIB ifCompliance3 IF-MIB ifCompliance3
IF-INVERTED-STACK-MIB ifInvCompliance
EtherLike-MIB dot3Compliance2 EtherLike-MIB dot3Compliance2
MAU-MIB mauModIfCompl3" MAU-MIB mauModIfCompl3
Compliance with the following external compliance statements
is OPTIONAL for implementations supporting PME Aggregation
Function (PAF) with flexible cross-connect between the PCS
and PME ports:
MIB Module Compliance Statement
---------- --------------------
IF-INVERTED-STACK-MIB ifInvCompliance
IF-CAP-STACK-MIB ifCapStackCompliance"
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
efmCuBasicGroup, efmCuBasicGroup,
efmCuPmeGroup, efmCuPmeGroup,
efmCuAlarmConfGroup, efmCuAlarmConfGroup,
efmCuNotificationGroup efmCuNotificationGroup
} }
GROUP efmCuPme2BProfileGroup GROUP efmCuPme2BProfileGroup
skipping to change at page 74, line 29 skipping to change at page 80, line 50
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 "Support for this group is only required for
implementations 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."
skipping to change at page 75, line 32 skipping to change at page 82, line 5
OBJECT efmCuAdaptiveSpectra OBJECT efmCuAdaptiveSpectra
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 default value SHOULD be false." the default value SHOULD be false."
::= { efmCuCompliances 1 } ::= { efmCuCompliances 1 }
END END
6. Security Considerations 7. Security Considerations
There is a number of managed objects defined in this MIB module that There is a number of managed objects defined in the EFM-CU-MIB module
have a MAX-ACCESS clause of read-write or read-create. Most objects that have a MAX-ACCESS clause of read-write or read-create. Most
are writeable only when the link is Down. Writing to these objects objects are writeable only when the link is Down. Writing to these
can have potentially disruptive effects on network operation, for objects can have potentially disruptive effects on network operation,
example: for example:
o Changing of efmCuPmeAdminSubType MAY lead to a potential locking o Changing of efmCuPmeAdminSubType MAY lead to a potential locking
of the link, as peer PMEs of the same sub-type cannot exchange of the link, as peer PMEs of the same sub-type cannot exchange
handshake messages. handshake messages.
o Changing of efmCuPAFAdminState to enabled MAY lead to a potential o Changing of efmCuPAFAdminState to enabled MAY lead to a potential
locking of the link, if the peer Phy does not support PAF. locking of the link, if the peer Phy does not support PAF.
o Changing of efmCuPAFDiscoveryCode, before the discovery operation, o Changing of efmCuPAFDiscoveryCode, before the discovery operation,
MAY lead to a wrongful discovery, for example when two -O ports MAY lead to a wrongful discovery, for example when two -O ports
skipping to change at page 76, line 21 skipping to change at page 82, line 39
support a particular configuration depends on the copper support a particular configuration depends on the copper
environment. environment.
o Activation of a PME can cause a severe degradation of service for o Activation of a PME can cause a severe degradation of service for
another EFMCu Phy, whose PME(s) MAY be affected by the cross-talk another EFMCu Phy, whose PME(s) MAY be affected by the cross-talk
from the newly activated PME. from the newly activated PME.
o Removal of a PME from an operationally 'up' EFMCu port, o Removal of a PME from an operationally 'up' EFMCu port,
aggregating several PMEs, MAY cause port's rate degradation aggregating several PMEs, MAY cause port's rate degradation
The user of this MIB module must therefore be aware that support for The user of the EFM-CU-MIB module must therefore be aware that
SET operations in a non-secure environment without proper protection support for SET operations in a non-secure environment without proper
can have a negative effect on network operations. protection can have a negative effect on network operations.
The readable objects in this MIB module (i.e., those with MAX-ACCESS The readable objects in the EFM-CU-MIB module (i.e., those with MAX-
other than not-accessible) may be considered sensitive in some ACCESS other than not-accessible) may be considered sensitive in some
environments since, collectively, they provide information about the environments since, collectively, they provide information about the
performance of network interfaces and can reveal some aspects of performance of network interfaces and can reveal some aspects of
their configuration. In particular since EFMCu can be carried over their configuration. In particular since EFMCu can be carried over
Unshielded Twisted Pair (UTP) voice grade copper in a bundle with Unshielded Twisted Pair (UTP) voice grade copper in a bundle with
other pairs belonging to another operator/customer, it is other pairs belonging to another operator/customer, it is
theoretically possible to evasdrop to an EFMCu transmission simply by theoretically possible to evasdrop to an EFMCu transmission simply by
"listening" to a cross-talk from an EFMCu pair, especially if the "listening" to a cross-talk from an EFMCu pair, especially if the
parameters of the EFMCu link in question are known. In such parameters of the EFMCu link in question are known. In such
environments it is important to control even GET and NOTIFY access to environments it is important to control even GET and NOTIFY access to
these objects and possibly even to encrypt their values when sending these objects and possibly even to encrypt their values when sending
them over the network via SNMP. them over the network via SNMP.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in these MIB modules.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of these MIB modules is properly configured to give access
the objects only to those principals (users) that have legitimate to the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
7. IANA Considerations 8. IANA Considerations
The two new values of dot3MauType (dot3MauType2BaseTL and The two new values of dot3MauType (dot3MauType2BaseTL and
dot3MauType10PassTS) and corresponding IANAifMauTypeListBits bit dot3MauType10PassTS) and corresponding IANAifMauTypeListBits bit
definitions (b2BaseTL and b10PassTS), as well as the new values for definitions (b2BaseTL and b10PassTS), as well as the new values for
IANAifMauMediaAvailable (availableReduced and ready) SHALL be defined IANAifMauMediaAvailable (availableReduced and ready) SHALL be defined
by the IANA in the IANA-MAU-MIB module (see [I-D.ietf-hubmib- by the IANA in the IANA-MAU-MIB module (see [I-D.ietf-hubmib-
rfc3636bis]) before this document is published as an RFC. rfc3636bis]) before this document is published as an RFC.
8. Acknowledgments 9. Acknowledgments
This document was produced by the IETF Ethernet Interfaces and Hub This document was produced by the IETF Ethernet Interfaces and Hub
MIB Working Group, whose efforts were greatly advanced by the MIB Working Group, whose efforts were greatly advanced by the
contributions of the following people (in alphabetical order): contributions of the following people (in alphabetical order):
Dan Romascanu Dan Romascanu
Marina Popilov Marina Popilov
Mathias Riess Mathias Riess
skipping to change at page 77, line 32 skipping to change at page 84, line 4
MIB Working Group, whose efforts were greatly advanced by the MIB Working Group, whose efforts were greatly advanced by the
contributions of the following people (in alphabetical order): contributions of the following people (in alphabetical order):
Dan Romascanu Dan Romascanu
Marina Popilov Marina Popilov
Mathias Riess Mathias Riess
Matt Squire Matt Squire
Mike Heard Mike Heard
Udi Ashkenazi Udi Ashkenazi
9. References 10. References
9.1. Normative References 10.1. Normative References
[802.3] IEEE, "IEEE Standard for Information technology - [802.3] IEEE, "IEEE Standard for Information technology -
Telecommunications and information exchange between Telecommunications and information exchange between
systems - Local and metropolitan area networks - Specific systems - Local and metropolitan area networks - Specific
requirements - Part 3: Carrier Sense Multiple Access with requirements - Part 3: Carrier Sense Multiple Access with
Collision Detection (CSMA/CD) Access Method and Physical Collision Detection (CSMA/CD) Access Method and Physical
Layer Specifications", IEEE Std 802.3-2005, December 2005. Layer Specifications", IEEE Std 802.3-2005, December 2005.
[802.3ah] IEEE, "IEEE Standard for Information technology - [802.3ah] IEEE, "IEEE Standard for Information technology -
Telecommunications and information exchange between Telecommunications and information exchange between
skipping to change at page 78, line 33 skipping to change at page 85, line 5
Conventions for SMIv2", STD 58, RFC 2579, April 1999. Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
9.2. Informative References 10.2. Informative References
[ANFP] Network Interoperability Consultative Committee (NICC), [ANFP] Network Interoperability Consultative Committee (NICC),
"Specification of the Access Network Frequency Plan (ANFP) "Specification of the Access Network Frequency Plan (ANFP)
applicable to transmission systems used on the BT Access applicable to transmission systems used on the BT Access
Network", NICC Document ND1602:2005/08, August 2005. Network", NICC Document ND1602:2005/08, August 2005.
[G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber Line [G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber Line
(SHDSL) transceivers", ITU-T Recommendation G.991.2, (SHDSL) transceivers", ITU-T Recommendation G.991.2,
December 2003. December 2003.
[G.993.1] ITU-T, "Very High speed Digital Subscriber Line [G.993.1] ITU-T, "Very High speed Digital Subscriber Line
transceivers", ITU-T Recommendation G.993.1, June 2004. transceivers", ITU-T Recommendation G.993.1, June 2004.
[I-D.ietf-hubmib-efm-epon-mib] [I-D.ietf-hubmib-efm-epon-mib]
Khermosh, L., "Managed Objects of EPON", Khermosh, L., "Managed Objects of EPON",
draft-ietf-hubmib-efm-epon-mib-04 (work in progress), draft-ietf-hubmib-efm-epon-mib-05 (work in progress),
February 2006. July 2006.
[I-D.ietf-hubmib-efm-mib] [I-D.ietf-hubmib-efm-mib]
Squire, M., "Definitions and Managed Objects for OAM Squire, M., "Definitions and Managed Objects for OAM
Functions on Ethernet Like Interfaces", Functions on Ethernet Like Interfaces",
draft-ietf-hubmib-efm-mib-04 (work in progress), draft-ietf-hubmib-efm-mib-04 (work in progress),
March 2006. March 2006.
[I-D.ietf-hubmib-rfc3636bis] [I-D.ietf-hubmib-rfc3636bis]
Beili, E., "Definitions of Managed Objects for IEEE 802.3 Beili, E., "Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs)", Medium Attachment Units (MAUs)",
draft-ietf-hubmib-rfc3636bis-03 (work in progress), draft-ietf-hubmib-rfc3636bis-05 (work in progress),
June 2006. July 2006.
[IANAifType-MIB] [IANAifType-MIB]
Internet Assigned Numbers Authority (IANA), "IANAifType Internet Assigned Numbers Authority (IANA), "IANAifType
Textual Convention definition", Textual Convention definition",
http://www.iana.org/assignments/ianaiftype-mib. http://www.iana.org/assignments/ianaiftype-mib.
[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
 End of changes. 103 change blocks. 
319 lines changed or deleted 625 lines changed or added

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