--- 1/draft-ietf-hubmib-efm-cu-mib-01.txt 2006-02-04 23:25:43.000000000 +0100 +++ 2/draft-ietf-hubmib-efm-cu-mib-02.txt 2006-02-04 23:25:43.000000000 +0100 @@ -1,96 +1,98 @@ Network Working Group E. Beili Internet-Draft Actelis Networks -Expires: January 14, 2005 July 16, 2004 +Expires: January 30, 2005 Aug 2004 Ethernet in the First Mile Copper (EFMCu) Interfaces MIB - draft-ietf-hubmib-efm-cu-mib-01.txt + draft-ietf-hubmib-efm-cu-mib-02.txt Status of this Memo - By submitting this Internet-Draft, I certify that any applicable - patent or other IPR claims of which I am aware have been disclosed, - and any of which I become aware will be disclosed, in accordance with + This document is an Internet-Draft and is subject to all provisions + of section 3 of RFC 3667. By submitting this Internet-Draft, each + author represents that any applicable patent or other IPR claims of + which he or she is aware have been or will be disclosed, and any of + which he or she become aware will be disclosed, in accordance with RFC 3668. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. - This Internet-Draft will expire on January 14, 2005. + This Internet-Draft will expire on January 30, 2005. Copyright Notice - Copyright (C) The Internet Society (2004). All Rights Reserved. + Copyright (C) The Internet Society (2004). Abstract This document defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based - nternets. This document proposes an extension to the Ethernet-like + internets. This document proposes an extension to the Ethernet-like Interfaces MIB and MAU MIB with a set of objects for managing an - Ethernet in the First Mile Copper (EFMCu) interfaces 10Pass-TS and - 2Base-TL, defined in IEEE standard 802.3ah. + Ethernet in the First Mile Copper (EFMCu) interfaces 10PASS-TS and + 2BASE-TL, defined in IEEE Std 802.3ah-2004. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3 3. Relation to other MIBs . . . . . . . . . . . . . . . . . . . . 4 3.1 Relation to Interfaces Group MIB . . . . . . . . . . . . . 4 3.1.1 Layering Model . . . . . . . . . . . . . . . . . . . . 4 - 3.1.2 PME Aggregation Function (PAF) . . . . . . . . . . . . 5 - 3.1.3 Discovery Operation . . . . . . . . . . . . . . . . . 5 - 3.1.4 EFMCu ports initialization . . . . . . . . . . . . . . 7 - 3.1.5 Usage of ifTable . . . . . . . . . . . . . . . . . . . 7 - 3.2 Relation to SHDSL MIB . . . . . . . . . . . . . . . . . . 8 - 3.3 Relation to VDSL MIB . . . . . . . . . . . . . . . . . . . 9 - 3.4 Relation to Ethernet-Like and MAU MIBs . . . . . . . . . . 9 - 4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 9 - 4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 9 - 4.2 Configuration Profiles . . . . . . . . . . . . . . . . . . 10 - 4.3 Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 10 - 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11 - 6. Security Considerations . . . . . . . . . . . . . . . . . . . 63 - 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 64 - 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 65 - 8.1 Normative References . . . . . . . . . . . . . . . . . . . . 65 - 8.2 Informative References . . . . . . . . . . . . . . . . . . . 65 - Author's Address . . . . . . . . . . . . . . . . . . . . . . . 66 - Intellectual Property and Copyright Statements . . . . . . . . 67 + 3.1.2 PME Aggregation Function (PAF) . . . . . . . . . . . . 6 + 3.1.3 Discovery Operation . . . . . . . . . . . . . . . . . 6 + 3.1.4 EFMCu ports initialization . . . . . . . . . . . . . . 8 + 3.1.5 Usage of ifTable . . . . . . . . . . . . . . . . . . . 8 + 3.2 Relation to SHDSL MIB . . . . . . . . . . . . . . . . . . 9 + 3.3 Relation to VDSL MIB . . . . . . . . . . . . . . . . . . . 10 + 3.4 Relation to Ethernet-Like and MAU MIBs . . . . . . . . . . 10 + 4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 11 + 4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 11 + 4.2 Configuration Profiles . . . . . . . . . . . . . . . . . . 11 + 4.3 Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 12 + 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 13 + 6. Security Considerations . . . . . . . . . . . . . . . . . . . 65 + 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 66 + 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 66 + 8.1 Normative References . . . . . . . . . . . . . . . . . . . . 66 + 8.2 Informative References . . . . . . . . . . . . . . . . . . . 67 + Author's Address . . . . . . . . . . . . . . . . . . . . . . . 68 + Intellectual Property and Copyright Statements . . . . . . . . 69 1. Introduction New Ethernet like interfaces have been defined in the Institute of Electrical and Electronics Engineers (IEEE) 802.3ah project a.k.a. - Ethernet in the First Mile (EFM) [802.3ah]. In particular 2Base-TL - and 10Pass-TS physical interfaces (PHYs), defined over voice-grade + Ethernet in the First Mile (EFM) [802.3ah]. In particular 2BASE-TL + and 10PASS-TS physical interfaces (PHYs), defined over voice-grade copper pairs, have been specified for the long and short reach respectively. These interfaces, collectively called EFMCu, are based on ITU-T G.SHDSL and VDSL specifications and support variable rates and optional Physical Medium Entity (PME) aggregation (a.k.a. multi-pair bonding). - 2Base-TL PHY is capable of providing at least 2Mbps over 2700 m long + 2BASE-TL PHY is capable of providing at least 2Mbps over 2700 m long single copper pair with a mean Bit Error Rate (BER) of 10^-7 (using 5dB target noise margin). 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 margin). This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community to manage EFMCu interfaces. @@ -116,123 +118,168 @@ RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. A detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [RFC2570]. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 3. Relation to other MIBs - This section outlines the relationship of this MIB with other MIBs - described in the relevant RFCs. Specifically, Interfaces Group MIB - (IF-MIB), Ethernet-Like (EtherLike-MIB), MAU (MAU-MIB), SHDSL - (HDSL2-SHDSL-LINE-MIB) and VDSL (VDSL-LINE-EXT-MCM-MIB) are + This section outlines the relationship of this MIB with other MIB + modules described in the relevant RFCs. Specifically, Interfaces + Group MIB (IF-MIB), Ethernet-Like (EtherLike-MIB), MAU (MAU-MIB), + SHDSL (HDSL2-SHDSL-LINE-MIB) and VDSL (VDSL-LINE-EXT-MCM-MIB) are discussed. 3.1 Relation to Interfaces Group MIB - 2Base-TL and 10Pass-TS PHY's specified in this MIB are stacked + 2BASE-TL and 10PASS-TS PHY's specified in this MIB are stacked Ethernet interfaces and as such are managed using generic interface management objects defined in the IF-MIB [RFC2863]. The stack - management in done via the ifStackTable, as defined in the IF-MIB + management is done via the ifStackTable, as defined in the IF-MIB [RFC2863] and ifInvStackTable, as defined in the IF-INVERTED-STACK-MIB [RFC2864]. 3.1.1 Layering Model An EFMCu interface can aggregate up to 32 Physical Medium Entity - (PME) sublayer devices (modems), using so called PME Aggregation + (PME) sub-layer devices (modems), using so called PME Aggregation Function (PAF). - An generic EFMCu device can have a number of Physical Coding Sublayer + A generic EFMCu device can have a number of Physical Coding Sublayer (PCS) ports, connected to a MAC via Medium Independent Interface (MII) at the upper layer, and cross-connected to a number of underlying PMEs, with a single PCS per PME relationship, see clause 61.1 of [802.3ah] for more details. - Each PME comprising an aggregated EFMCu port is represented in the - Interface table as a separate port with ifType of shdsl(169) for - 2Base-TL or vdsl(97) for 10Pass-TS. The ifType values are defined in - IANAifType-MIB. ifSpeed for each PME shall return an actual bitrate - of the active PME or a configured bitrate for pre-activated modems - (note that unassigned PME has its default bitrate). + Each PME in the aggregated EFMCu port is represented in the Interface + table (ifTable) as a separate port with ifType of shdsl(169) for + 2BASE-TL or vdsl(97) for 10PASS-TS. The ifType values are defined in + [IANAifType-MIB]. + + ifSpeed for each PME shall return the actual data bitrate of the + active PME or a configured bitrate for pre-activated modems (e.g. + for 2BaseTL PMEs it is a multiple of 64Kbps). The ifSpeed of the PCS + is the sum of the current operating data rates of all modems in the + aggregation group, without the 64/65B encapsulation overhead and PAF + overhead, but acounting for the Inter-Frame Gaps (IFG). + + The following configuration shall have no frame loss (the test-sets + are configured to generate 100% of back to back traffic, i.e. + minimal IFG, at 10Mbps; the EFM interfaces are obviously aggregated) + ): + + [testset]--10BaseT--[CO]--2BaseTL--[CPE]--10BaseT--[testset] + ifSpeed=10Mbps ifSpeed=10Mbps ifSpeed=10Mbps + + [testset]--100BaseT--[CO]--10PassTS--[CPE]--100BaseT--[testset] + ifSpeed=100Mbps ifSpeed=100Mbps ifSpeed=100Mbps + + Figure 1: Example configuration with no frame loss + + The following figure shows the layering diagram and corresponding use + of ifTable and ifMauTable: + + _________________________ _ + | LLC | | + +-------------------------+ | 1 ifEntry + | MAC | | ifType: ethernetCsmacd(6) + +-------------------------+ > ifMauEntry + | Reconsiliation | | ifMauType: dot3MauType2BaseTL or + +-------------------------+ | dot3MauType10PassTS + | PCS | | + +-------------+---+-------+ + + | TC \ | | | | + +-----\ | | | | + | PMA > PME 1 |...| PME N | > N ifEntry (N=1..32) + +-----/ | | | | ifType: shdsl(169) or vdsl(97) + | PMD/ | | | | + -------------+---+------- - + + Figure 2: Use of ifTable and ifMauTable for EFMCu ports The ifStackTable is indexed by the ifIndex values of the aggregated EFMCu port (PCS) and the PMEs connected to it. ifStackTable allows a Network Management application to determine which PMEs are connected to a particular PCS and change connections (if supported by the application). The ifInvStackTable, being an inverted version of the ifStackTable, provides an efficient means for a Network Management application to read a subset of the ifStackTable and thereby determine which PCS runs on top of a particular PME. - A new table efmCuAvailableStackTable defined in this MIB, specifies - for each PCS a list of PMEs, which can possibly be cross-connected to + A new table ifAvailableStackTable defined in this MIB, specifies for + each PCS a list of PMEs, which can possibly be cross-connected to that PCS, determined by the cross-connect capability of the device. This table, modeled after ifStackTable, is read only, reflecting current cross-connect capability, which can be dynamic in some implementations (e.g. if PMEs are located on a pluggable module and - the card is pulled out). Note that PME availability per PCS, - described by efmCuAvailableStackTable, can be constrained by other + the module is pulled out). Note that PME availability per PCS, + described by ifAvailableStackTable, 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. efmCuAvailableStackTable, ifStackTable - and efmCuPAFCapacity) SHALL be inspected. - - The efmCuAvailableStackTable allows to define new entries + respective parameters (e.g. ifAvailableStackTable, ifStackTable and + efmCuPAFCapacity) SHALL be inspected. - *EdNote: Add efmCuInvAvailableStackTable describing which PCS ports - can be connected to a particular PME. Possibly move these 2 tables to - a separate MIB to make cross-connect capability available to other - MIBs for import (changing the prefix of course from 'efmCu' to say - 'if'). * + *EdNote: Add ifInvAvailableStackTable describing which PCS ports can + be connected to a particular PME. Add it to the + ifStackCapabilityGroup conformance statement. * 3.1.2 PME Aggregation Function (PAF) - The PME Aggregation Function (PAF) is OPTIONAL and MAY not be - supported. Note however that the agent is REQUIRED to report on the - PAF capability for all EFMCu ports (2Base-TL and 10Pass-TS). + The PME Aggregation Function (PAF) is OPTIONAL. Note however that + the agent is REQUIRED to report on the PAF capability for all EFMCu + ports (2BASE-TL and 10PASS-TS). *EdNote: Add more info.* 3.1.3 Discovery Operation + The EFMCu ports may optionally support discovery operation, whereby + PMEs, during initialization, exchange information about their + respective aggregation groups (PCS). This information can then be + used to detect copper missconnections or for an automatic assignment + of the local PMEs into aggregation groups instead of fixed + pre-configuration. + This MIB allows a Network Management application to control EFM Discovery mechanism and query its results. Note that the Discovery mechanism can work only if PAF is supported and enabled. Two tables are used by Discovery mechanism: ifStackTable and - efmCuAvailableStackTable defined. The following pseudo-code defines - an example of Discovery and automatic PME assignment for a generic - PAF enabled multi-PCS EFMCu device, located at Central Office (CO): + ifAvailableStackTable defined. The following pseudo-code defines an + example of Discovery and automatic PME assignment for a generic PAF + enabled multi-PCS EFMCu device, located at Central Office (CO) [Note + that automatic PME assignment is only shown here for the purposes of + the example. Fixed PME pre-assignment or manual assignment may be + chosen by a particular implementation]: FOREACH pcs[i] IN co_device { // Discover only on PAF enabled ports with room for more PMEs IF ( pcs[i].PAFSupported AND pcs[i].NumPMEs < pcs[i].PAFCapacity ) { dc = pcs[i].DiscoveryCode = MAC[i]; // unique 6 Byte per PCS // go over all currently disconnected PMEs, which can // pottentially be connected to PCS[i] - FOREACH pme[j] IN efmCuAvailableStackTable[pcs[i]] AND + FOREACH pme[j] IN ifAvailableStackTable[pcs[i]] AND NOT IN ifInvStackTable[pme[j]] // unassigned { pme[j].RemoteDiscoveryCode = dc; // Set if Clear r = pme[j].RemoteDiscoveryCode; // Get IF ( r == dc AND pcs[i].NumPMEs < pcs[i].PAFCapacity) { // Remote CPE connected via PME[j] is/was a peer for // PCS[i]. Connect this PME to the PCS (there's room) ADD pme[j] TO ifStackTable[pcs[i]]; pcs[i].NumPMEs = pcs[i].NumPMEs + 1; // Discover all other currently disconnected PMEs, // attached to the same CPE and connect them to the PCS // provided there is enough room for more PMEs. - FOREACH pme[k] IN efmCuAvailableStackTable[pcs[i]] and + FOREACH pme[k] IN ifAvailableStackTable[pcs[i]] and NOT IN ifInvStackTable[pme[k]] { r = pme[k].RemoteDiscoveryCode; // Get IF ( r == dc AND pcs[i].NumPMEs < pcs[i].PAFCapacity) { ADD pme[k] TO ifStackTable[pcs[i]]; pcs[i].NumPMEs = pcs[i].NumPMEs + 1; } } } // Discovered all PMEs which lead to the same CPE and @@ -252,21 +299,21 @@ and 45.2.3.21). Note that PCS port does not have to be operationally 'down' for the connection to succeed. In fact, a dynamic PME addition (and removal) MAY be implemented whith an available PME being initialized first (by setting its ifAdminStatus to 'up') and then added to an operationally 'up' PCS port, by modifying a respective ifStackTable entry. It is RECOMMENDED that a removal of the last operationally 'up' PME from an operationally 'up' PCS would be rejected by the - implementation, as this action would completetly drop the link. + implementation, as this action would completely drop the link. 3.1.4 EFMCu ports initialization EFMCu ports being built on top of xDSL technology, require a lengthy initialization or 'training' process, before any data can pass. During this initialization both ends of a link (peers) work cooperatively to achieve required data rate on a particular copper pair. Sometimes, when the copper line is too long or the noise environment on the line is too high, that 'training' process may fail to achieve a specific target rate with required characteristics. @@ -276,26 +323,27 @@ particular PCS or PME to start initialization process, which may take tens of seconds for EFMCu ports, especially if PAF is involved. The ifOperStatus object shows the operational state of an interface (extended by efmCuPmeOperStatus defined in this MIB for PME interfaces). A disconnected PME may be initialized by changing the ifAdminState from 'down' to 'up'. Changing the ifAdminState to 'up' on the PCS initializes all PMEs connected to that particular PCS. Note that in case of PAF some interfaces may fail to initialize while others - suceed. The PCS is considered operationally 'up' if at least one PME - aggregated by its PAF is operationally 'up'. When all PMEs connected - to the PCS are 'down' the PCS SHALL be considered operationally - 'lowerLayerDown'. The PCS SHALL be considered operationally - 'notPresent' if it is not connected to any PME. The PCS/PME - interface SHALL remain operationally 'down' during initialization. + succeed. The PCS is considered operationally 'up' if at least one + PME aggregated by its PAF is operationally 'up'. When all PMEs + connected to the PCS are 'down' the PCS SHALL be considered + operationally 'lowerLayerDown'. The PCS SHALL be considered + operationally 'notPresent' if it is not connected to any PME. The + PCS/PME interface SHALL remain operationally 'down' during + initialization. The efmCuPmeOperStatus defined in this MIB expands PME's ifOperStatus value of 'down' to 'downReady', 'downNotReady' and 'init' values, indicating various EFMCu PME specific states. 3.1.5 Usage of ifTable Both PME and PCS interfaces of the EFMCu PHY are managed using interface specific management objects defined in this MIB and generic interface objects from the ifTable of IF-MIB, with all management @@ -308,176 +356,181 @@ +---------------------------------+---------------------------------+ | IF-MIB object | EFMCu interpretation | +---------------------------------+---------------------------------+ | ifIndex | Interface index. Note that each | | | PME and each PCS in the EFMCu | | | PHY MUST have a unique index, | | | as there some PCS and PME | | | specific attributes accessible | | | only on the PCS or PME level. | | ifType | ethernetCsmacd(6) for PCS, | - | | shdsl(169) for 2Base-TL PME, | - | | vdsl(97) for 10Pass-TS PME | + | | shdsl(169) for 2BASE-TL PME, | + | | vdsl(97) for 10PASS-TS PME | | ifSpeed | Actual 'net' data rate as seen | | | across MII | | ifAdminStatus | Setting this object to 'up' | | | instructs a particular PCS | | | (with all PMEs connected to it) | | | or PME to start initialization | | | process | | ifOperStatus | efmCuPmeOperStatus supplements | | | the 'down' value of | | | ifOperStatus for PMEs. | +---------------------------------+---------------------------------+ Table 1 3.2 Relation to SHDSL MIB - G.SHDSL.bis modems, similar to PME(s) comprising a 2BaseTL port, are + G.SHDSL.bis modems, similar to PME(s) comprising a 2BASE-TL port, are described in HDSL2-SHDSL-LINE-MIB [I-D.ietf-adslmib-gshdslbis]. Note that not all attributes of G.SHDSL modems reflected in HDSL2-SHDSL-LINE-MIB have adequate management objects (Clause 30 attributes and Clause 45 registers) in the EFM standard. Because of these differences and for the purposes of simplicity, - unification of attributes common to both 2Base-TL and 10Pass-TS PMES - and name consistency (e.g. prefixing the 2BaseTL PME related objects - with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided not to - reference HDSL2-SHDSL-LINE-MIB objects, but define all the relevant - objects in this MIB. + unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs + and name consistency (e.g. prefixing the 2BASE-TL PME related + objects with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided + not to reference HDSL2-SHDSL-LINE-MIB objects, but define all the + relevant objects in this MIB. However, if some functionality, not available in this MIB, is required and supported by the PME, e.g. performance monitoring, relevant HDSL2-SHDSL-LINE-MIB groups MAY be included and aplied for - PMEs of 2Base-TL subtype. + PMEs of 2BASE-TL subtype. 3.3 Relation to VDSL MIB - VDSL (DMT) modems, similar to the PME(s) comprising a 10PassTS port, + VDSL (DMT) modems, similar to the PME(s) comprising a 10PASS-TS port, are described in VDSL-LINE-EXT-MCM-MIB [I-D.ietf-adslmib-vdsl-ext-mcm]. Note that not all attributes of VDSL modems reflected in VDSL-LINE-EXT-MCM-MIB have adequate management objects (Clause 30 attributes and Clause 45 registers) in the EFM standard. 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-MCM-MIB objects, but define all the relevant objects in this MIB. However, if some functionality, not available in this MIB, is required and supported by the PME, relevant VDSL-LINE-EXT-MCM-MIB - groups MAY be included and applied for PMEs of 10Pass-TS subtype. + groups MAY be included and applied for PMEs of 10PASS-TS subtype. 3.4 Relation to Ethernet-Like and MAU MIBs - The implementation of EtherLike-MIB [RFC3635] and MAU-MIB [RFC3636] - is REQUIRED for the EFMCu interfaces. As such EFMCu interfaces - 2Base-TL/10Pass-TS SHALL return an ifType of ethernetCsmacd(6). - Information on the particular flavor of EFMCu that an interface is - running is available from ifSpeed in the IF-MIB [RFC2863], and - ifMauType in the MAU-MIB. + The implementation of EtherLike-MIB [RFC3635] and MAU-MIB + [I-D.ietf-hubmib-rfc3636bis] is REQUIRED for the EFMCu interfaces. - The MAU-MIB shall be augmented to include the following new values - for ifMauType (instances of dot2MauType): + Two new values of ifMauType (OBJECT-IDENTITIES of dot3MauType) and + corresponding bit definitions of ifMauTypeListBits + (IANAifMauTypeListBits) have been defined in the IANA-MAU-TC-MIB + [I-D.ietf-hubmib-rfc3636bis] for the EFMCu MAUs: - o dot3MauType2BaseTL - voice grade UTP Phy specified in Clause 61 - and 63 + o dot3MauType2BaseTL and b2BaseTL - for 2BASE-TL MAU - o dot3MauType10PassTS - voice grade UTP Phy specified in Clause 61 - and 62 + o dot3MauType10PassTS and b10PassTS - for 10PASS-TS MAU - *EdNote: Should we also include -O/-R subtypes?* + As an EtherLike interface every EFMCu port (an ifEntry representing a + consolidation of LLC, MAC and PCS (sub)layers) SHALL return an ifType + of ethernetCsmacd(6). While most of the MAU characteristics is not + applicable to the EFMCu ports (no auto-negotiation, media available, + false carriers or jabber), they SHALL return an appropriate ifMauType + (dot3MauType2BaseTL or dot3mauType10PassTS) in order to direct the + management software to look in the EFM-CU-MIB for the desired + information. For example the information on the particular EFMCu + flavor that an EFMCu port is running is available from + efmCuOperSubType, defined in this MIB module. + + Since EFMCu PMEs are not EtherLike interfaces, they cannot be + instantiated as MAU interface objects. 4. MIB Structure 4.1 Overview The main management objects defined in this MIB are split into 2 groups: o efmCuPort - containing objects for configuration, capabilities, status and notifications, common to all EFMCu PHYs. o efmCuPme - containing objects for configuration, capabilities, status and notifications of EFMCu PMEs. - In addition the efmCuAvailableStackTable is defined at the same - level. + In addition the ifAvailableStackTable is defined at the same level. The efmCuPme group in turn contains efmCuPme2B and efmCuPme10P - groups, which define configuration profiles specific to 2BaseTL and - 10PassTS PMEs respectively as well as PME specific status + groups, which define configuration profiles specific to 2BASE-TL and + 10PASS-TS PMEs respectively as well as PME specific status information. 4.2 Configuration Profiles Since a managed node can have a large number of EFMCu PHYs, provisioning every parameter on every EFMCu PHY may become burdensome. Moreover, most PMEs are provisioned identically with the same set of parameters. To simplify the provisioning process, this MIB makes use of configuration profiles, similar to HDSL2-SHDSL-LINE-MIB and VDSL-LINE-EXT-MCM-MIB. A profile is a set of parameters that can be shared by multiple PME ports using the same configuration. The configuration profiles are defined in efmCuPme2BConfProfileTable - and efmCu10PConfProfileTable for 2Base-TL and 10Pass-TS PMEs - respectively. There are 12 predefined standard profiles for 2Base-TL - and 22 standard profiles for 10Pass-TS, defined in 802.3ah and + and efmCu10PConfProfileTable for 2BASE-TL and 10PASS-TS PMEs + respectively. There are 12 predefined standard profiles for 2BASE-TL + and 22 standard profiles for 10PASS-TS, defined in 802.3ah and dedicated for rapid provisioning of EFMCu PHYs in most scenarios. An ability to define new configuration profiles is also provided to allow for EFMCu deployment tailored to specific copper environment and spectral regulations. A specific configuration profile is assigned to a specific PME via efmCuPmeAdminProfile object. Alternatively, by assigning a non-empty profile to a PCS port via efmCuAdminProfile, all PMEs connected to - the PCS port are made to share that profile, which comes handy during - configuration of aggregated ports. + the PCS port are made to share that profile, which comes in handy + during configuration of aggregated ports. 4.3 Mapping of IEEE 802.3ah Managed Objects This section contains the mapping between 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-MIB [RFC2863]. Note that majority of the objects defined in this MIB do not have direct counterparts in Clause 30 and instead refer to Clause 45 registers. *EdNote: It would be a good idea to update Clause 30 of 802.3ah after this MIB is approved. I guess this should be done via a maintanence request. * +---------------------------------+---------------------------------+ | IEEE 802.3 Managed Object | Corresponding SNMP Object | +---------------------------------+---------------------------------+ - | oPAF - PME Basic Package | | + | oPAF - Basic Package | | | (Mandatory) | | | aPAFID | ifIndex (IF-MIB) | | aPhyEnd | efmCuPhySide | | aPHYCurrentStatus | efmCuStatus | | aPAFSupported | efmCuPAFSupported | | oPAF - PME Aggregation Package | | | (Optional) | | | aPAFAdminState | efmCuPAFAdminState | - | aPAFID | ifIndex (IF-MIB) | | aLocalPAFCapacity | efmCuPAFCapacity | - | aLocalPMEAvailable | efmCuAvailableStackTable | + | aLocalPMEAvailable | ifAvailableStackTable | | aLocalPMEAggregate | ifStackTable (IF-MIB) | | aRemotePAFSupported | efmCuRemotePAFSupported | | aRemotePAFCapacity | efmCuRemotePAFCapacity | - | aRemotePMEAvailable | | | aRemotePMEAggregate | | | oPME - 10P/2B Package | | | (Mandatory) | | | aPMEID | ifIndex (IF-MIB) | | aPMEAdminState | ifAdminState (IF-MIB) | | aPMEStatus | efmCuPmeStatus | | aPMESNRMgn | efmCuPmeSnrMgn | | aTCCodingViolations | efmCuPmeTCCodingErrors | | aProfileSelect | efmCuAdminProfile, | | | efmCuPmeAdminProfile | @@ -491,30 +544,30 @@ 5. Definitions EFM-CU-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32, Unsigned32, Counter32, mib-2 FROM SNMPv2-SMI -- [RFC2578] TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress FROM SNMPv2-TC -- [RFC2579] + MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP + FROM SNMPv2-CONF -- [RFC2580] SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- [RFC3411] ifIndex, ifSpeed, InterfaceIndex FROM IF-MIB -- [RFC2863] - MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP - FROM SNMPv2-CONF -- [RFC2580] ; efmCuMIB MODULE-IDENTITY - LAST-UPDATED "200407150000Z" -- July 15, 2004 + LAST-UPDATED "200410240000Z" -- October 24, 2004 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 @@ -547,22 +600,24 @@ information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications - Media Access Control Parameters, Physical Layers and Management Parameters for subscriber access networks', 19 April 2003. Of particular interest are Clause 61, 'Physical Coding Sublayer (PCS) and common specifications, type 10PASS-TS and - type 2BASE-TL', Clause 30, 'Management', and Clause 45, - 'Management Data Input/Output (MDIO) Interface'. + type 2BASE-TL', Clause 30, 'Management', Clause 45, + 'Management Data Input/Output (MDIO) Interface', Annex 62A, + 'PMD profiles for 10PASS-TS' and Annex 63A, 'PMD profiles for + 2BASE-TL'. Naming Conventions: Atn - Attenuation CO - Central Office CPE - Customer Premises Equipment EFM - Ethernet in the First Mile EFMCu - EFM Copper MDIO - Management Data Input/Output Mgn - Margin PAF - PME Aggregation Function @@ -573,31 +628,31 @@ SNR - Signal to Noise Ratio TCPAM - Trellis Coded Pulse Amplitude Modulation Copyright (C) The Internet Society (2004). This version of this MIB module is part of RFC XXXX; see the RFC itself for full legal notices." -- EdNote: Replace XXXX with the actual RFC number & -- remove this note - REVISION "200407150000Z" -- July 15, 2004 + REVISION "200410240000Z" -- October 24, 2004 DESCRIPTION "Initial version, published as RFC XXXX." - ::= { mib-2 YYY } -- EdNote: Replace YYY with a real OID once it is -- allocated & remove this note. -- Sections of the module efmCuObjects OBJECT IDENTIFIER ::= { efmCuMIB 1 } + efmCuConformance OBJECT IDENTIFIER ::= { efmCuMIB 2 } -- Groups in the module efmCuPort OBJECT IDENTIFIER ::= { efmCuObjects 1 } efmCuPme OBJECT IDENTIFIER ::= { efmCuObjects 2 } -- Textual Conventions @@ -645,41 +700,41 @@ or when no common profile(s) need to be referenced and sub-interface profile shall take precedence." SYNTAX OCTET STRING (SIZE(0..6)) -- Port Notifications Group efmCuPortNotifications OBJECT IDENTIFIER ::= { efmCuPort 0 } efmCuLowBandwidth NOTIFICATION-TYPE OBJECTS { - -- ifINdex is not needed here since we are under specific PCS + -- ifIndex is not needed here since we are under specific PCS ifSpeed, efmCuThreshLowBandwidth } STATUS current DESCRIPTION "This notification indicates that EFMCu port's data rate - reached or droped below a Low Bandwidth Threshold + reached or dropped below a Low Bandwidth Threshold (i.e. bandwidth degradation happening in case of PAF when one or more PMEs drop)." -- EdNote: add throttling limitations here ::= { efmCuPortNotifications 1 } -- PCS Port group efmCuPortConfTable OBJECT-TYPE SYNTAX SEQUENCE OF EfmCuPortConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "Table for Configuration of EFMCu 2BaseTL/10PassTS (PCS) + "Table for Configuration of EFMCu 2BASE-TL/10PASS-TS (PCS) Ports. Entries in this table MUST be maintained in a persistent manner" ::= { efmCuPort 1 } efmCuPortConfEntry OBJECT-TYPE SYNTAX EfmCuPortConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the EFMCu Port Configuration table. @@ -714,21 +769,21 @@ PCS. No more than a single PME can be assigned to this PCS in this case. When 'enabled', PAF will be performed by the PCS when the link is Up, even on a single attached PME, if PAF is supported. PCS ports incapable of supporting PAF SHALL return a value of 'disabled'. Attempts to 'enable' such ports SHALL be ignored. PAF 'enabled' port with multiple PMEs assigned cannot be 'disabled'. Attempts to 'disable' such port SHALL be rejected, - untill at most one PME is left assigned. + until at most one PME is left assigned. Changing PAFAdminState is a traffic disruptive operation and as such SHALL be done when the link is Down. Attempts to change this object SHALL be ignored if the link is Up or Initializing. This object maps to the Clause 30 attribute aPAFAdminState. If a Clause 45 MDIO Interface to the PCS is present, then this object maps to the PAF enable bit in the 10P/2B PCS control @@ -825,21 +880,21 @@ shall allow lossless transmission of full-duplex 10Mbps Ethernet frame stream with minimal inter-frame gap). The value is limited above by 100Mbps as this is the max burst rate across MII for EFMCu ports. The value between 1 and 100000 indicates that the total data rate (ifSpeed) of the EFMCu port after initialization should be equal to the target data rate or less, if the target data rate cannot be achieved under spectral restrictions specified - by efmCuAdminProfile/efmCiPmeAdminProfile and with desired SNR + by efmCuAdminProfile/efmCuPmeAdminProfile and with desired SNR margin. In case the copper environment allows to achieve higher total data rate than specified by the target, the excess capability SHALL be converted to additional SNR margin and spread evenly across all active PMEs assigned to the (PCS) port. The value of 999999 means that the target data rate is not fixed and should be set to the maximum attainable rate during initialization (Best Effort), under specified spectral restrictions and with desired SNR Margin. @@ -860,21 +915,21 @@ SYNTAX Unsigned32(0..21) UNITS "dB" MAX-ACCESS read-write STATUS current DESCRIPTION "Desired EFMCu port SNR Margin to be achieved on all PMEs assigned to the port, during initializiation. (The SNR margin is the difference between the desired SNR and the actual SNR). Note that 802.3ah recommends using default Target SNR Margin - of 5dB for 2BaseTL ports and 6dB for 10PassTS ports in order + of 5dB for 2BASE-TL ports and 6dB for 10PASS-TS ports in order to achieve mean Bit Error Rate (BER) of 10^-7 at the PMA service interface. This object is read-write for the -O subtype EFMCu ports (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. Changing of the Target SNR Margin MUST be performed when the link is Down. Attempts to change this object MUST be rejected with the error inconsistentValue, if the link is Up or Initializing. @@ -915,24 +970,25 @@ Value of truth(1) indicates that efmCuLowBandwidth notification is enabled. Value of false(0) indicates the it is disabled." ::= { efmCuPortConfEntry 7 } efmCuPortCapabilityTable OBJECT-TYPE SYNTAX SEQUENCE OF EfmCuPortCapabilityEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "Table for Capabilities of EFMCu 2BaseTL/10PassTS (PCS) + "Table for Capabilities of EFMCu 2BASE-TL/10PASS-TS (PCS) Ports. Entries in this table MUST be maintained in a persistent manner" ::= { efmCuPort 2 } + efmCuPortCapabilityEntry OBJECT-TYPE SYNTAX EfmCuPortCapabilityEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the EFMCu Port Capability table. Each entry represents an EFMCu port indexed by the ifIndex. Note that an EFMCu PCS port runs on top of a single or multiple PME port(s), which are also indexed by ifIndex." INDEX { ifIndex } @@ -987,21 +1042,21 @@ REFERENCE "[802.3ah] 61.2.2, 30.11.1.1.9, 45.2.3.17.2" ::= { efmCuPortCapabilityEntry 2 } efmCuPAFCapacity OBJECT-TYPE SYNTAX Unsigned32 (1..32) MAX-ACCESS read-only STATUS current DESCRIPTION "Number of PMEs that can be aggregated by the local PAF. - The number of PMEs currently assigned to a particluar + The number of PMEs currently assigned to a particular EFMCu port (efmCuNumPMEs) is never greater than efmCuPAFCapacity. This object maps to the Clause 30 attribute aLocalPAFCapacity." REFERENCE "[802.3ah] 61.2.2, 30.11.1.1.6" ::= { efmCuPortCapabilityEntry 3 } efmCuPeerPAFCapacity OBJECT-TYPE @@ -1019,21 +1074,21 @@ REFERENCE "[802.3ah] 61.2.2, 30.11.1.1.10" ::= { efmCuPortCapabilityEntry 4 } efmCuPortStatusTable OBJECT-TYPE SYNTAX SEQUENCE OF EfmCuPortStatusEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides overall status information of EFMCu - 2BaseTL/10PassTS ports. This table contains live data from + 2BASE-TL/10PASS-TS ports. This table contains live data from the equipment. As such, it is NOT persistent." ::= { efmCuPort 3 } efmCuPortStatusEntry OBJECT-TYPE SYNTAX EfmCuPortStatusEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the EFMCu Port Status table. Each entry represents an EFMCu port indexed by the ifIndex. @@ -1062,27 +1117,27 @@ noPeer(0), -- peer Phy cannot be reached pmeSubTypeMismatch(1), -- Assigned PMEs Sub-type Mismatch lowBandwidth(2) -- Low Bandwidth } MAX-ACCESS read-only STATUS current DESCRIPTION "EFMCu (PCS) port Fault Status. This is a bitmap of possible conditions. The various bit positions are: noPeer - peer PHY cannot be reached (e.g. - no PMEs attached, all PMEs are Down etc.) More info is available in efmCuPmeFltStatus. - pmeSubTypeMismatch - PMEs in the aggregation group are not - of the same sub-type, e.g. PMEs with - -O and -R subtype + pmeSubTypeMismatch - local PMEs in the aggregation group + are not of the same sub-type, e.g. + some PMEs in the local device are -O + while others are -R subtype. lowBandwidth - ifSpeed of the port reached or droped below efmCuThreshLowBandwidth This object is intended to supplement ifOperStatus object in IF-MIB. Additional information is available via efmCuPmeFltStatus object for each PME in the aggregation group (single PME if PAF is disabled)." REFERENCE "ifOperStatus in IF-MIB; efmCuPmeFltStatus" @@ -1296,35 +1350,35 @@ efmCuPmeLineAtnCrossing NOTIFICATION-TYPE OBJECTS { efmCuPmeLineAtn, efmCuPmeThreshLineAtn } STATUS current DESCRIPTION "This notification indicates that the loop attenuation threshold (as per the efmCuPmeThreshLineAtn - value) has been reached/exceeded for the 2Base-TL/10Pass-TS + value) has been reached/exceeded for the 2BASE-TL/10PASS-TS PME." -- EdNote: add throttling limitations here ::= { efmCuPmeNotifications 1 } efmCuPmeSnrMgnCrossing NOTIFICATION-TYPE OBJECTS { efmCuPmeSnrMgn, efmCuPmeThreshSnrMgn } STATUS current DESCRIPTION "This notification indicates that the SNR margin threshold (as per the efmCuPmeThreshSnrMgn value) has been - reached/exceeded for the 2Base-TL/10Pass-TS PME." + reached/exceeded for the 2BASE-TL/10PASS-TS PME." -- EdNote: add throttling limitations here ::= { efmCuPmeNotifications 2 } efmCuPmeDeviceFault NOTIFICATION-TYPE OBJECTS { efmCuPmeFltStatus } STATUS current DESCRIPTION "This notification indicates that a fault in the PME has been @@ -1350,31 +1404,33 @@ OBJECTS { efmCuPmeFltStatus, efmCuPmeOperSubType } STATUS current DESCRIPTION "This notification indicates that peer PME was using incompatible protocol during initialization." -- EdNote: add throttling limitations here ::= { efmCuPmeNotifications 5 } + -- The PME group efmCuPmeConfTable OBJECT-TYPE SYNTAX SEQUENCE OF EfmCuPmeConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table for Configuration of common aspects for EFMCu - 2BaseTL/10PassTS PME ports (modems). Configuration of aspects - specific to 2BaseTL or 10PassTS PME types is represented in - efmCuPme2BConfTable and efmCuPme10PConfTable respectively. + 2BASE-TL/10PASS-TS PME ports (modems). Configuration of + aspects specific to 2BASE-TL or 10PASS-TS PME types is + represented in efmCuPme2BConfTable and efmCuPme10PConfTable + respectively. Entries in this table MUST be maintained in a persistent manner." ::= { efmCuPme 1 } efmCuPmeConfEntry OBJECT-TYPE SYNTAX EfmCuPmeConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION @@ -1638,40 +1695,42 @@ MAX-ACCESS read-write STATUS current DESCRIPTION "Indicates whether efmCuPmeProtocolInitFailure notifications should be generated for this interface. Value of truth(1) indicates that efmCuPmeProtocolInitFailure notification is enabled. Value of false(0) indicates the it is disabled." ::= { efmCuPmeConfEntry 10 } + efmCuPmeCapabilityTable OBJECT-TYPE SYNTAX SEQUENCE OF EfmCuPmeCapabilityEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table for Configuration of common aspects for EFMCu - 2BaseTL/10PassTS PME ports (modems). Configuration of aspects - specific to 2BaseTL or 10PassTS PME types is represented in - efmCuPme2BConfTable and efmCuPme10PConfTable respectively. + 2BASE-TL/10PASS-TS PME ports (modems). Configuration of + aspects specific to 2BASE-TL or 10PASS-TS PME types is + represented in efmCuPme2BConfTable and efmCuPme10PConfTable + respectively. Entries in this table MUST be maintained in a persistent manner." ::= { efmCuPme 2 } efmCuPmeCapabilityEntry OBJECT-TYPE SYNTAX EfmCuPmeCapabilityEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "An entry in the EFMCu PME Configuration table. + "An entry in the EFMCu PME Capability table. Each entry represents common aspects of an EFMCu PME port indexed by the ifIndex. Note that an EFMCu PME port can be stacked below a single PCS port, also indexed by ifIndex, possibly together with other PME ports if PAF is enabled." INDEX { ifIndex } ::= { efmCuPmeCapabilityTable 1 } EfmCuPmeCapabilityEntry ::= SEQUENCE { efmCuPmeSubTypesSupported BITS @@ -1686,53 +1745,57 @@ } MAX-ACCESS read-only STATUS current DESCRIPTION "PME supported sub-types. This is a bitmap of possible sub-types. The various bit positions are: ieee2BaseTLO - PME is capable of operating as 2BaseTL-O ieee2BaseTLR - PME is capable of operating as 2BaseTL-R ieee10PassTSO - PME is capable of operating as 10PassTS-O ieee10PassTSR - PME is capable of operating as 10PassTS-R - An actual mode of operation is determined by - efmCuPmeAdminSubType. + + An desired mode of operation is determined by + efmCuPmeAdminSubType, while efmCuPmeOperSubType relects the + current operating mode. If a Clause 45 MDIO Interface to the PCS is present, then this object combines the 10PASS-TS capable and 2BASE-TL capable bits in the 10P/2B PMA/PMD speed ability register and the CO supported and CPE supported bits in the 10P/2B PMA/PMD status register" REFERENCE "[802.3ah] 61.1, 45.2.1.4.1, 45.2.1.4.2, 45.2.1.12.2, 45.2.1.12.3" ::= { efmCuPmeCapabilityEntry 1 } efmCuPmeStatusTable OBJECT-TYPE SYNTAX SEQUENCE OF EfmCuPmeStatusEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table for Configuration of common aspects for EFMCu - 2BaseTL/10PassTS PME ports (modems). Configuration of aspects - specific to 2BaseTL or 10PassTS PME types is represented in - efmCuPme2BConfTable and efmCuPme10PConfTable respectively. + 2BASE-TL/10PASS-TS PME ports (modems). Configuration of + aspects specific to 2BASE-TL or 10PASS-TS PME types is + represented in efmCuPme2BConfTable and efmCuPme10PConfTable + respectively. Entries in this table MUST be maintained in a persistent manner." ::= { efmCuPme 3 } efmCuPmeStatusEntry OBJECT-TYPE SYNTAX EfmCuPmeStatusEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "An entry in the EFMCu PME Configuration table. + "An entry in the EFMCu PME Status table. + Each entry represents common aspects of an EFMCu PME port indexed by the ifIndex. Note that an EFMCu PME port can be stacked below a single PCS port, also indexed by ifIndex, possibly together with other PME ports if PAF is enabled." INDEX { ifIndex } ::= { efmCuPmeStatusTable 1 } EfmCuPmeStatusEntry ::= SEQUENCE { efmCuPmeOperStatus INTEGER, @@ -1808,21 +1871,21 @@ diagnostic or self-test fault has been detected. configInitFailure - Configuration initialization failure, due to inability of the PME link to support configuration profile, requested during initialization. protocolInitFailure - Protocol initialization failure, due to incompatible protocol used by the Peer PME during init (that could happen if a peer PMD is G.SDHSL/VDSL - modem for 2BaseTL/10PassTS PME + modem for 2BASE-TL/10PASS-TS PME respectively). This object is intended to supplement ifOperStatus in IF-MIB. This object partially maps to the Clause 30 attribute aPMEStatus. If a Clause 45 MDIO Interface to the PME is present, then this object consolidates information from various PMA/PMD registers, namely: Fault bit in PMA/PMD status 1 register, @@ -1958,31 +2022,30 @@ incremented for each 64/65-octet encapsulation error detected by the 64/65-octet receive function. If a Clause 45 MDIO Interface to the PME TC is present, then this object maps to the TC coding violations register (see 45.2.6.12)." REFERENCE "[802.3ah] 61.3.3.1, 45.2.6.12" ::= { efmCuPmeStatusEntry 9 } - -- 2BaseTL specific PME group - + -- 2BASE-TL specific PME group efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 } efmCuPme2BConfProfileTable OBJECT-TYPE SYNTAX SEQUENCE OF EfmCuPme2BConfProfileEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table supports definitions of configuration profiles for - 2BaseTL PMEs. + 2BASE-TL PMEs. First 12 entries in this table SHALL always be defined as follows (see 802.3ah Annex 63A): -------+------+-----+--------+------------------ Profile Rate Power Region Constellation index (Kbps) (dBm) (G.991.2) -------+------+-----+--------+------------------ 1 5696 13.5 Annex A 32-TCPAM 2 3072 13.5 Annex A 32-TCPAM 3 2048 13.5 Annex A 16-TCPAM 4 1024 13.5 Annex A 16-TCPAM @@ -2004,24 +2067,24 @@ This table MUST be maintained in a persistent manner." REFERENCE "[802.3ah] Annex 63A, 30.11.2.1.6" ::= { efmCuPme2B 2 } efmCuPme2BConfProfileEntry OBJECT-TYPE SYNTAX EfmCuPme2BConfProfileEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "Each entry corresponds to a single 2BaseTL PME configuration + "Each entry corresponds to a single 2BASE-TL PME configuration profile. Each profile contains a set of configuration parameters, which are applied to all 2BaseTL-O PMEs - assigned to the 2BaseTL (PCS) port, referencing that profile + assigned to the 2BASE-TL (PCS) port, referencing that profile via efmCuAdminProfile object or, if efmCuAdminProfile is zero, all 2BaseTL-O PMEs, referencing that profile via efmCuPmeAdminProfile. Profiles may be created/deleted using the row creation/ deletion mechanism via efmCuPme2BProfileRowStatus. If an active entry is referenced, the entry MUST remain 'active' until all references are removed. Default entries (first 12) MUST not be removed." INDEX { efmCuPme2BProfileIndex } @@ -2035,32 +2099,32 @@ efmCuPme2BPower Unsigned32, efmCuPme2BConstellation INTEGER, efmCuPme2BProfileRowStatus RowStatus } efmCuPme2BProfileIndex OBJECT-TYPE SYNTAX ProfileIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION - "2BaseTL PME Profile index. + "2BASE-TL PME Profile index. This object is the unique index associated with this profile. Entries in this table are referenced via efmCuAdminProfile or efmCuPmeAdminProfile objects." ::= { efmCuPme2BConfProfileEntry 1 } efmCuPme2BProfileDescr OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..255)) MAX-ACCESS read-create STATUS current DESCRIPTION - "A textual string containing information about 2BaseTL PME + "A textual string containing information about 2BASE-TL PME Profile. The string MAY include information about data rate and spectral limitations of this particular profile." ::= { efmCuPme2BConfProfileEntry 2 } efmCuPme2BRegion OBJECT-TYPE SYNTAX INTEGER { regionA(1), -- Annex A regionB(2), -- Annex B regionC(3) -- Annex C } @@ -2087,21 +2151,21 @@ REFERENCE "[802.3ah] 45.2.1.42" ::= { efmCuPme2BConfProfileEntry 3 } efmCuPme2BDataRate OBJECT-TYPE SYNTAX Unsigned32(0..5696) UNITS "Kbps" MAX-ACCESS read-create STATUS current DESCRIPTION - "Desired 2BaseTL PME Data Rate. + "Desired 2BASE-TL PME Data Rate. The rate is fixed when the value of this object is n x 64Kbps, where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM. The value of 0 means that data rate is not fixed but is adaptive and should be set to the maximum attainable rate during line probing. If a Clause 45 MDIO Interface to the PME is present, then this object maps to the Min/Max Data Rate1 bits in the 2B PMD parameters register." REFERENCE @@ -2129,21 +2193,21 @@ ::= { efmCuPme2BConfProfileEntry 5 } efmCuPme2BConstellation OBJECT-TYPE SYNTAX INTEGER { tcpam16(1), -- 16-TCPAM tcpam32(2) -- 32-TCPAM } MAX-ACCESS read-create STATUS current DESCRIPTION - "Desired TCPAM Constellation of the 2BaseTL PME. The possible + "Desired TCPAM Constellation of the 2BASE-TL PME. The possible values are: tcpam16(1) - 16-TCPAM tcpam32(2) - 32-TCPAM If a Clause 45 MDIO Interface to the PME is present, then this object map to the Constellation1 bits in the 2B general parameter register." REFERENCE "[802.3ah] 45.2.1.43" ::= { efmCuPme2BConfProfileEntry 6 } @@ -2154,21 +2218,21 @@ STATUS current DESCRIPTION "This object controls creation/deletion of the associated entry in efmCuPme2BConfProfileTable per the semantics of RowStatus. If an 'active' entry is referenced via efmCuAdminProfile or efmCuPmeAdminProfile, the entry MUST remain 'active' until all references are removed." ::= { efmCuPme2BConfProfileEntry 7 } - -- 10PassTS specific PME group + -- 10PASS-TS specific PME group efmCuPme10P OBJECT IDENTIFIER ::= { efmCuPme 6 } efmCuPme10PConfProfileTable OBJECT-TYPE SYNTAX SEQUENCE OF EfmCuPme10PConfProfileEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table supports definitions of configuration profiles for 10PassTL PMEs. @@ -2210,26 +2274,27 @@ This table MUST be maintained in a persistent manner." REFERENCE "[802.3ah] Annex 62B.3, 30.11.2.1.6" ::= { efmCuPme10P 1 } efmCuPme10PConfProfileEntry OBJECT-TYPE SYNTAX EfmCuPme10PConfProfileEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "Each entry corresponds to a single 10PassTS PME configuration - profile. Each profile contains a set of configuration - parameters, which are applied to all PMEs assigned to the - 10PassTS (PCS) port, referencing that profile via - efmCuAdminProfile object, or, if efmCuAdminProfile is zero, - to all PMEs referencing that profile via efmCuPmeAdminProfile. + "Each entry corresponds to a single 10PASS-TS PME + configuration profile. Each profile contains a set of + configuration parameters, which are applied to all PMEs + assigned to the 10PASS-TS (PCS) port, referencing that profile + via efmCuAdminProfile object, or, if efmCuAdminProfile is + zero, to all PMEs referencing that profile via + efmCuPmeAdminProfile. Profiles may be created/deleted using the row creation/ deletion mechanism via efmCuPme10PProfileRowStatus. If an 'active' entry is referenced, the entry MUST remain 'active' until all references are removed. Default entries (first 22) MUST not be removed." INDEX { efmCuPme10PProfileIndex } ::= { efmCuPme10PConfProfileTable 1 } EfmCuPme10PConfProfileEntry ::= SEQUENCE { @@ -2241,32 +2306,31 @@ efmCuPme10PPayloadURateProfile INTEGER, efmCuPme10PPayloadDRateProfile INTEGER, efmCuPme10PProfileRowStatus RowStatus } efmCuPme10PProfileIndex OBJECT-TYPE SYNTAX ProfileIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION - "10PassTS PME Profile Index. + "10PASS-TS PME Profile Index. This object is the unique index associated with this profile. Entries in this table are referenced via efmCuAdminProfile or efmCuPmeAdminProfile." ::= { efmCuPme10PConfProfileEntry 1 } - efmCuPme10PProfileDescr OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..255)) MAX-ACCESS read-create STATUS current DESCRIPTION - "A textual string containing information about 10PassTS PME + "A textual string containing information about 10PASS-TS PME Profile. The string MAY include information about data rate and spectral limitations of this particular profile." ::= { efmCuPme10PConfProfileEntry 2 } efmCuPme10PBandplanPSDMskProfile OBJECT-TYPE SYNTAX INTEGER {-- PSD Mask Bands Bandplan profile1(1), -- T1.424/T-U P1 FTTCab.M1 x/D/U/D/U A profile2(2), -- T1.424/T-U P1 FTTEx.M1 profile3(3), -- T1.424/T-U P1 FTTCab.M2 profile4(4), -- T1.424/T-U P1 FTTEx.M2 @@ -2292,21 +2356,21 @@ profile24(24), -- TS1 101 270-1 Pcab.M2 profile25(25), -- TS1 101 270-1 Pex.P1.M2 profile26(26), -- TS1 101 270-1 Pex.P2.M2 profile27(27), -- G.993.1 F.1.2.1 (VDSLoPOTS) x/D/U/D/U F profile28(28), -- G.993.1 F.1.2.2 (VDSLoTCM-ISDN) profile29(29) -- G.993.1 F.1.2.3 (PSD reduction) } MAX-ACCESS read-create STATUS current DESCRIPTION - "10PassTS PME Bandplan and PSD Mask profile, + "10PASS-TS PME Bandplan and PSD Mask profile, as specified in 802.3ah Annex 62A. Possible values are: --------------+------------------------+-----------+--------- Profile Name PSD Mask Bands Bandplan --------------+------------------------+-----------+--------- profile1(1) - T1.424/T-U P1 FTTCab.M1 x/D/U/D/U A profile2(2) - T1.424/T-U P1 FTTEx.M1 profile3(3) - T1.424/T-U P1 FTTCab.M2 profile4(4) - T1.424/T-U P1 FTTEx.M2 profile5(5) - T1.424/T-U P1 FTTCab.M1 D/D/U/D/U profile6(6) - T1.424/T-U P1 FTTEx.M1 @@ -2348,21 +2412,21 @@ profile4(4), -- T1.424/T-U Noise F M2 profile5(5), -- ETSI TS 101 270-1 Noise A&B profile6(6), -- ETSI TS 101 270-1 Noise C profile7(7), -- ETSI TS 101 270-1 Noise D profile8(8), -- ETSI TS 101 270-1 Noise E profile9(9) -- ETSI TS 101 270-1 Noise F } MAX-ACCESS read-create STATUS current DESCRIPTION - "10PassTS PME Upstream Power Back-Off (UPBO) Reference PSD + "10PASS-TS PME Upstream Power Back-Off (UPBO) Reference PSD Profile, as specified in 802.3ah Annex 62A. Possible values are: profile1(1) - T1.424/T-U Noise A M1 profile2(2) - T1.424/T-U Noise A M2 profile3(3) - T1.424/T-U Noise F M1 profile4(4) - T1.424/T-U Noise F M2 profile5(5) - ETSI TS 101 270-1 Noise A&B profile6(6) - ETSI TS 101 270-1 Noise C profile7(7) - ETSI TS 101 270-1 Noise D profile8(8) - ETSI TS 101 270-1 Noise E @@ -2386,21 +2450,21 @@ profile6(6), -- - 15-1 - 3.500 4.000 profile7(7), -- F-5 #04 - - 3.747 3.754 profile8(8), -- F-5 #05 - - 3.791 3.805 profile9(9), -- 6-2 - 17 7.000 7.100 profile10(10),-- F-5 #06 15-1 - 7.000 7.300 profile11(11) -- 6-2 15-1 1 10.100 10.150 } MAX-ACCESS read-create STATUS current DESCRIPTION - "10PassTS PME Egress Control Band Notch Profile bitmap, + "10PASS-TS PME Egress Control Band Notch Profile bitmap, as specified in 802.3ah Annex 62A. Possible values are: --------------+---------+----------+-----------+------+----- Profile Name G.991.3 T1.424/T-U TS101 270-1 StartF EndF Table Table Table (MHz) (MHz) --------------+---------+----------+-----------+------+----- profile0(0) - no profile profile1(1) - F-5 #01 - - 1.810 1.825 profile2(2) - 6-2 15-1 17 1.810 2.000 profile3(3) - F-5 #02 - - 1.907 1.912 profile4(4) - F-5 #03 - - 3.500 3.575 @@ -2430,21 +2494,21 @@ profile20(20), -- 10 profile25(25), -- 12.5 profile30(30), -- 15 profile50(50), -- 25 profile70(70), -- 35 profile100(100) -- 50 } MAX-ACCESS read-create STATUS current DESCRIPTION - "10PassTS PME Upstream Payload Rate Profile, + "10PASS-TS PME Upstream Payload Rate Profile, as specified in 802.3ah Annex 62A. Possible values are: profile5(5) - 2.5 Mbps profile10(10) - 5 Mbps profile15(15) - 7.5 Mbps profile20(20) - 10 Mbps profile25(25) - 12.5 Mbps profile30(30) - 15 Mbps profile50(50) - 25 Mbps profile70(70) - 35 Mbps profile100(100) - 50 Mbps @@ -2471,21 +2535,21 @@ profile30(30), -- 15 profile50(50), -- 25 profile70(70), -- 35 profile100(100), -- 50 profile140(140), -- 70 profile200(200) -- 100 } MAX-ACCESS read-create STATUS current DESCRIPTION - "10PassTS PME Downstream Payload Rate Profile, + "10PASS-TS PME Downstream Payload Rate Profile, as specified in 802.3ah Annex 62A. Possible values are: profile5(5) - 2.5 Mbps profile10(10) - 5 Mbps profile15(15) - 7.5 Mbps profile20(20) - 10 Mbps profile25(25) - 12.5 Mbps profile30(30) - 15 Mbps profile50(50) - 25 Mbps profile70(70) - 35 Mbps profile100(100) - 50 Mbps @@ -2515,29 +2579,29 @@ If an active entry is referenced via efmCuAdminProfile or efmCuPmeAdminProfile, the entry MUST remain 'active' until all references are removed." ::= { efmCuPme10PConfProfileEntry 8 } efmCuPme10PStatusTable OBJECT-TYPE SYNTAX SEQUENCE OF EfmCuPme10PStatusEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "Table reflecting status of EFMCu 10PassTS PMEs (modems)." + "Table reflecting status of EFMCu 10PASS-TS PMEs (modems)." ::= { efmCuPme10P 2 } efmCuPme10PStatusEntry OBJECT-TYPE SYNTAX EfmCuPme10PStatusEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "An entry in the EFMCu 10PassTS PME Status table." + "An entry in the EFMCu 10PASS-TS PME Status table." AUGMENTS { efmCuPmeStatusEntry } ::= { efmCuPme10PStatusTable 1 } EfmCuPme10PStatusEntry ::= SEQUENCE { efmCuPme10PElectricalLength Integer32, efmCuPme10PFECCorrectedBlocks Counter32, efmCuPme10PFECUncorrectedBlocks Counter32 -- EdNote: To be continued } @@ -2534,183 +2598,184 @@ AUGMENTS { efmCuPmeStatusEntry } ::= { efmCuPme10PStatusTable 1 } EfmCuPme10PStatusEntry ::= SEQUENCE { efmCuPme10PElectricalLength Integer32, efmCuPme10PFECCorrectedBlocks Counter32, efmCuPme10PFECUncorrectedBlocks Counter32 -- EdNote: To be continued } - efmCuPme10PElectricalLength OBJECT-TYPE SYNTAX Integer32(0..8192|65535) UNITS "m" MAX-ACCESS read-only STATUS current DESCRIPTION - "Electrical Length in meters as perceived by the 10PassTS PME + "Electrical Length in meters as perceived by the 10PASS-TS PME after the link is established. The value of 65535 is returned if the link is Down or Initializing or the PME is unable to estimate the Electrical Length. If a Clause 45 MDIO Interface to the PME is present, then this object maps to the 10P Electrical Length register" REFERENCE "[802.3ah] 45.2.1.21" ::= { efmCuPme10PStatusEntry 1 } efmCuPme10PFECCorrectedBlocks OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION - "A count of received and corrected FEC codewords in 10Pass-TS + "A count of received and corrected FEC codewords in 10PASS-TS PME. This object maps to aPMEFECCorrectedBlocks attribute in clause 30. If a Clause 45 MDIO Interface to the PMA/PMD is present, then this object maps to the 10P FEC correctable errors register" REFERENCE "[802.3ah] 45.2.1.22" ::= { efmCuPme10PStatusEntry 2 } efmCuPme10PFECUncorrectedBlocks OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current 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. This object maps to aPMEFECUncorrectableBlocks attribute in clause 30. If a Clause 45 MDIO Interface to the PMA/PMD is present, then this object maps to the 10P FEC uncorrectable errors register" REFERENCE "[802.3ah] 45.2.1.23" ::= { efmCuPme10PStatusEntry 3 } - -- efmCuAvailableStackTable for use in Discovery + -- ifAvailableStackTable for use in Discovery - efmCuAvailableStackTable OBJECT-TYPE - SYNTAX SEQUENCE OF EfmCuAvailableStackEntry + 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: - efmCuAvailableStackStatus.x.y=capable + ifAvailableStackStatus.x.y=capable Note that there's always at least on PCS for each PME and at least one PME for each PCS in the EFMCu devices, with efmCuPAFCapacity and efmCuPeerPAFCapacity indicating maximum number of PMEs which can be aggregated by local and remote PCS port respectively. This table is read only as it describes device capability" REFERENCE "ifStackTable of RFC 2863" ::= { efmCuObjects 3 } - efmCuAvailableStackEntry OBJECT-TYPE - SYNTAX EfmCuAvailableStackEntry + 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 { - efmCuAvailableStackHigherLayer, - efmCuAvailableStackLowerLayer + ifAvailableStackHigherLayer, + ifAvailableStackLowerLayer } - ::= { efmCuAvailableStackTable 1 } + ::= { ifAvailableStackTable 1 } - EfmCuAvailableStackEntry ::= + IfAvailableStackEntry ::= SEQUENCE { - efmCuAvailableStackHigherLayer InterfaceIndex, - efmCuAvailableStackLowerLayer InterfaceIndex, - efmCuAvailableStackStatus INTEGER + ifAvailableStackHigherLayer InterfaceIndex, + ifAvailableStackLowerLayer InterfaceIndex, + ifAvailableStackStatus INTEGER } - efmCuAvailableStackHigherLayer OBJECT-TYPE + + 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 - efmCuAvailableStackLowerLayer." - ::= { efmCuAvailableStackEntry 1 } + ifAvailableStackLowerLayer." + ::= { ifAvailableStackEntry 1 } - efmCuAvailableStackLowerLayer OBJECT-TYPE + 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 - efmCuAvailableStackHigherLayer." - ::= { efmCuAvailableStackEntry 2 } + ifAvailableStackHigherLayer." + ::= { ifAvailableStackEntry 2 } - efmCuAvailableStackStatus OBJECT-TYPE + 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 efmCuAvailableStackLowerLayer MAY be + the ifAvailableStackLowerLayer MAY be connected to run 'below' the PCS sub-layer interface, identified by the - efmCuAvailableStackLowerLayer. + 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. efmCuAvailableStackTable, + 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." - ::= { efmCuAvailableStackEntry 3 } + ::= { ifAvailableStackEntry 3 } -- -- Conformance Statements -- efmCuGroups OBJECT IDENTIFIER ::= { efmCuConformance 1 } efmCuCompliances OBJECT IDENTIFIER ::= { efmCuConformance 2 } -- Object Groups @@ -2731,44 +2796,54 @@ efmCuPAFGroup OBJECT-GROUP OBJECTS { efmCuPeerPAFSupported, efmCuPAFCapacity, efmCuPeerPAFCapacity, efmCuPAFAdminState, efmCuPAFDiscoveryCode, efmCuPAFRemoteDiscoveryCode, efmCuNumPMEs, - efmCuAvailableStackStatus + ifAvailableStackStatus } STATUS current DESCRIPTION "A collection of objects required for optional PME Aggregation Function (PAF) and PAF discovery in EFMCu ports." ::= { 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 OBJECTS { efmCuPAFInErrors, efmCuPAFInSmallFragments, efmCuPAFInLargeFragments, efmCuPAFInBadFragments, efmCuPAFInLostFragments, efmCuPAFInLostStarts, efmCuPAFInLostEnds, efmCuPAFInOverflows } STATUS current DESCRIPTION "A collection of objects supporting optional error counters of PAF on EFMCu ports." - ::= { efmCuGroups 3 } + ::= { efmCuGroups 4 } efmCuPmeGroup OBJECT-GROUP OBJECTS { efmCuPmeAdminProfile, efmCuPmeOperStatus, efmCuPmeFltStatus, efmCuPmeSubTypesSupported, efmCuPmeAdminSubType, efmCuPmeOperSubType, efmCuPAFRemoteDiscoveryCode, @@ -2777,22 +2852,22 @@ efmCuPmePeerSnrMgn, efmCuPmeLineAtn, efmCuPmePeerLineAtn, efmCuPmeTCCodingErrors, efmCuPmeThreshLineAtn, efmCuPmeThreshSnrMgn } STATUS current DESCRIPTION "A collection of objects providing information about - a 2BaseTL/10PassTS PME." - ::= { efmCuGroups 4 } + a 2BASE-TL/10PASS-TS PME." + ::= { efmCuGroups 5 } efmCuAlarmConfGroup OBJECT-GROUP OBJECTS { efmCuThreshLowBandwidth, efmCuLowBandwidthEnable, efmCuPmeThreshLineAtn, efmCuPmeLineAtnCrossingEnable, efmCuPmeThreshSnrMgn, efmCuPmeSnrMgnCrossingEnable, efmCuPmeLineAtnCrossingEnable, @@ -2802,21 +2877,21 @@ -- efmCuPmeThreshES, -- efmCuPmethreshSES, -- efmCuPmeThreshCRCanomalies, -- efmCuPmeThreshLOSWS, -- efmCuPmeThreshUAS } STATUS current DESCRIPTION "A collection of objects required for configuration of alarm thresholds and notifications in EFMCu ports." - ::= { efmCuGroups 5 } + ::= { efmCuGroups 6 } efmCuNotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { efmCuLowBandwidth, efmCuPmeLineAtnCrossing, efmCuPmeSnrMgnCrossing, efmCuPmeDeviceFault, efmCuPmeConfigInitFailure, efmCuPmeProtocolInitFailure -- efmCuPmePerfES, @@ -2824,71 +2899,71 @@ -- efmCuPmePerfCRCanomalies, -- efmCuPmePerfLOSWS, -- efmCuPmePerfUAS, -- efmCuPmeDeviceFault, -- efmCuPmeLocalPowerLoss } STATUS current DESCRIPTION "This group supports notifications of significant conditions associated with EFMCu ports." - ::= { efmCuGroups 6 } + ::= { efmCuGroups 7 } efmCuPme2BProfileGroup OBJECT-GROUP OBJECTS { efmCuPme2BProfileDescr, efmCuPme2BRegion, efmCuPme2BDataRate, efmCuPme2BPower, efmCuPme2BConstellation, efmCuPme2BProfileRowStatus } STATUS current DESCRIPTION "A collection of objects that constitute a configuration - profile for configuration of 2BaseTL ports." - ::= { efmCuGroups 7 } + profile for configuration of 2BASE-TL ports." + ::= { efmCuGroups 8 } efmCuPme10PProfileGroup OBJECT-GROUP OBJECTS { efmCuPme10PProfileDescr, efmCuPme10PBandplanPSDMskProfile, efmCuPme10PUPBOReferenceProfile, efmCuPme10PBandNotchProfiles, efmCuPme10PPayloadURateProfile, efmCuPme10PPayloadDRateProfile, efmCuPme10PProfileRowStatus } STATUS current DESCRIPTION "A collection of objects that constitute a configuration - profile for configuration of 10PassTS ports." - ::= { efmCuGroups 8 } + profile for configuration of 10PASS-TS ports." + ::= { efmCuGroups 9 } efmCuPme10PStatusGroup OBJECT-GROUP OBJECTS { efmCuPme10PElectricalLength, efmCuPme10PFECCorrectedBlocks, efmCuPme10PFECUncorrectedBlocks } STATUS current DESCRIPTION "A collection of objects providing status information - specific to 10PassTS PMEs." - ::= { efmCuGroups 9 } + specific to 10PASS-TS PMEs." + ::= { efmCuGroups 10 } -- Compliance Statements efmCuCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION - "The compliance statement for 2BaseTL/10PassTS interfaces. + "The compliance statement for 2BASE-TL/10PASS-TS interfaces. Compliance with the following external compliance statements is prerequisite: MIB Module Compliance Statement ---------- -------------------- IF-MIB ifCompliance3 IF-INVERTED-STACK-MIB ifInvCompliance EtherLike-MIB dot3Compliance2 MAU-MIB mauModIfCompl3" @@ -2896,41 +2971,47 @@ MANDATORY-GROUPS { efmCuBasicGroup, efmCuPmeGroup, efmCuAlarmConfGroup, efmCuNotificationGroup } GROUP efmCuPme2BProfileGroup DESCRIPTION "Support for this group is only required for implementations - supporting 2Base-TL Phy." + supporting 2BASE-TL Phy." GROUP efmCuPme10PProfileGroup DESCRIPTION "Support for this group is only required for implementations - supporting 10Pass-TS Phy." + supporting 10PASS-TS Phy." GROUP efmCuPAFGroup DESCRIPTION - "Support for this group is only required for implementations - supporting PME Aggregation Function (PAF)." + "Support for this group is only required for + 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 DESCRIPTION "Support for this group is optional for implementations supporting PME Aggregation Function (PAF)." GROUP efmCuPme10PStatusGroup DESCRIPTION "Support for this group is optional for implementations - supporting 10Pass-TS Phy." + supporting 10PASS-TS Phy." OBJECT efmCuPmeSubTypesSupported SYNTAX BITS { ieee2BaseTLO(0), ieee2BaseTLR(1), ieee10PassTSO(2), ieee10PassTSR(3) } DESCRIPTION "Support for all subtypes is not required. However at least @@ -2940,22 +3022,22 @@ DESCRIPTION "Write access is not required (needed only for PMEs supporting more than a single subtype, e.g. ieee2BaseTLO and ieee2BaseTSR or ieee2BaseTLR and ieee10PassTSR)" OBJECT efmCuTargetSnrMgn MIN-ACCESS read-only DESCRIPTION "Write access is optional. For PHYs without write access - the target SNR margin SHALL be fixed at 5dB for 2BaseTL - and 6dB for 10PassTS." + the target SNR margin SHALL be fixed at 5dB for 2BASE-TL + and 6dB for 10PASS-TS." -- EdNote: To be Continued ::= { efmCuCompliances 1 } END 6. Security Considerations There is a number of managed objects defined in this MIB module that have a MAX-ACCESS clause of read-write or read-create. Most objects @@ -3021,34 +3103,46 @@ Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. 7. Acknowledgments - Not yet. + This document was produced by the IETF Ethernet Interfaces and Hub + MIB Working Group, whose efforts were greatly advanced by the + contributions of the following people (in alphabetical order): + + Dan Romascanu + + Mathias Riess + + Matt Squire + + Mike Heard + + Udi Ashkenazi 8. References 8.1 Normative References [802.3ah] IEEE, "Draft amendment to - Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications - Media Access Control Parameters, - Physical Layers and Management Parameters for subscriber - access networks", IEEE Draft P802.3ah/D3.3, April 2004. + Physical Layers and Management Parameters for Subscriber + Access Networks", IEEE Std 802.3ah-2004, September 2004. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of @@ -3078,41 +3172,49 @@ [I-D.ietf-adslmib-vdsl-ext-mcm] Dodge, M. and B. Ray, "Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Multiple Carrier Modulation (MCM) Line Coding", draft-ietf-adslmib-vdsl-ext-mcm-04 (work in progress), May 2004. [I-D.ietf-hubmib-efm-epon-mib] Khermosh, L., "Managed Objects for the Ethernet Passive - Optical Networks", draft-ietf-hubmib-efm-epon-mib-01 (work - in progress), April 2004. + Optical Networks", draft-ietf-hubmib-efm-epon-mib-02 (work + in progress), September 2004. [I-D.ietf-hubmib-efm-mib] Squire, M., "Ethernet in the First Mile (EFM) Common MIB", draft-ietf-hubmib-efm-mib-01 (work in progress), June 2004. + [I-D.ietf-hubmib-rfc3636bis] + Beili, E., "Definitions of Managed Objects for IEEE 802.3 + Medium Attachment Units (MAUs)", + draft-ietf-hubmib-rfc3636bis-00 (work in progress), + October 2004. + + [IANAifType-MIB] + Internet Assigned Numbers Authority (IANA), "IANAifType + Textual Convention definition", + http://www.iana.org/assignments/ianaiftype-mib. + [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. [RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table Extension to the Interfaces Group MIB", RFC 2864, June 2000. [RFC3635] Flick, J., "Definitions of Managed Objects for the Ethernet-like Interface Types", RFC 3635, September 2003. - [RFC3636] Flick, J., "Definitions of Managed Objects for IEEE 802.3 - Medium Attachment Units (MAUs)", RFC 3636, September 2003. - Author's Address Edward Beili Actelis Networks Bazel 25 Petach-Tikva Israel Phone: +972-3-924-3491 EMail: edward.beili@actelis.com