idnits 2.17.1 draft-ietf-hubmib-efm-cu-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3667, Section 5.1 on line 14. -- Found old boilerplate from RFC 3978, Section 5.5 on line 3163. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 3140. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 3147. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 3153. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 3169), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 36. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, or will be disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) == There are 26 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: These default entries SHALL be created by default and MUST not be deleted. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 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 } ::= { efmCuPme2BConfProfileTable 1 } == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: These default entries SHALL be created by default and MUST not be deleted. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: 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. 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 } -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 16, 2004) is 7223 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC3411' is mentioned on line 502, but not defined == Missing Reference: 'ITU-T G.991.2' is mentioned on line 2079, but not defined == Missing Reference: 'IF-MIB' is mentioned on line 2614, but not defined ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Downref: Normative reference to an Informational RFC: RFC 3410 == Outdated reference: A later version (-11) exists of draft-ietf-adslmib-gshdslbis-02 == Outdated reference: A later version (-06) exists of draft-ietf-adslmib-vdsl-ext-mcm-04 == Outdated reference: A later version (-06) exists of draft-ietf-hubmib-efm-epon-mib-01 == Outdated reference: A later version (-06) exists of draft-ietf-hubmib-efm-mib-01 -- Obsolete informational reference (is this intentional?): RFC 3636 (Obsoleted by RFC 4836) Summary: 9 errors (**), 0 flaws (~~), 15 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group E. Beili 3 Internet-Draft Actelis Networks 4 Expires: January 14, 2005 July 16, 2004 6 Ethernet in the First Mile Copper (EFMCu) Interfaces MIB 7 draft-ietf-hubmib-efm-cu-mib-01.txt 9 Status of this Memo 11 By submitting this Internet-Draft, I certify that any applicable 12 patent or other IPR claims of which I am aware have been disclosed, 13 and any of which I become aware will be disclosed, in accordance with 14 RFC 3668. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as 19 Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on January 14, 2005. 34 Copyright Notice 36 Copyright (C) The Internet Society (2004). All Rights Reserved. 38 Abstract 40 This document defines a portion of the Management Information Base 41 (MIB) for use with network management protocols in TCP/IP based 42 nternets. This document proposes an extension to the Ethernet-like 43 Interfaces MIB and MAU MIB with a set of objects for managing an 44 Ethernet in the First Mile Copper (EFMCu) interfaces 10Pass-TS and 45 2Base-TL, defined in IEEE standard 802.3ah. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 50 2. The Internet-Standard Management Framework . . . . . . . . . . 3 51 3. Relation to other MIBs . . . . . . . . . . . . . . . . . . . . 4 52 3.1 Relation to Interfaces Group MIB . . . . . . . . . . . . . 4 53 3.1.1 Layering Model . . . . . . . . . . . . . . . . . . . . 4 54 3.1.2 PME Aggregation Function (PAF) . . . . . . . . . . . . 5 55 3.1.3 Discovery Operation . . . . . . . . . . . . . . . . . 5 56 3.1.4 EFMCu ports initialization . . . . . . . . . . . . . . 7 57 3.1.5 Usage of ifTable . . . . . . . . . . . . . . . . . . . 7 58 3.2 Relation to SHDSL MIB . . . . . . . . . . . . . . . . . . 8 59 3.3 Relation to VDSL MIB . . . . . . . . . . . . . . . . . . . 9 60 3.4 Relation to Ethernet-Like and MAU MIBs . . . . . . . . . . 9 61 4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 9 62 4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 9 63 4.2 Configuration Profiles . . . . . . . . . . . . . . . . . . 10 64 4.3 Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 10 65 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11 66 6. Security Considerations . . . . . . . . . . . . . . . . . . . 63 67 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 64 68 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 65 69 8.1 Normative References . . . . . . . . . . . . . . . . . . . . 65 70 8.2 Informative References . . . . . . . . . . . . . . . . . . . 65 71 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 66 72 Intellectual Property and Copyright Statements . . . . . . . . 67 74 1. Introduction 76 New Ethernet like interfaces have been defined in the Institute of 77 Electrical and Electronics Engineers (IEEE) 802.3ah project a.k.a. 78 Ethernet in the First Mile (EFM) [802.3ah]. In particular 2Base-TL 79 and 10Pass-TS physical interfaces (PHYs), defined over voice-grade 80 copper pairs, have been specified for the long and short reach 81 respectively. These interfaces, collectively called EFMCu, are based 82 on ITU-T G.SHDSL and VDSL specifications and support variable rates 83 and optional Physical Medium Entity (PME) aggregation (a.k.a. 84 multi-pair bonding). 86 2Base-TL PHY is capable of providing at least 2Mbps over 2700 m long 87 single copper pair with a mean Bit Error Rate (BER) of 10^-7 (using 88 5dB target noise margin). 90 10PASS-TS PHY is capable of providing at least 10Mbps over 750 m long 91 single copper pair with a mean BER of 10^-7 (using 6dB target noise 92 margin). 94 This memo defines a portion of the Management Information Base (MIB) 95 for use with network management protocols in the Internet community 96 to manage EFMCu interfaces. 98 Note that managed objects for Operation, Administration and 99 Management (OAM) and Ethernet over Passive Optical Networks (EPON) 100 clauses of IEEE 802.3ah are defined in EFM-COMMON-MIB 101 [I-D.ietf-hubmib-efm-mib] and EFM-EPON-MIB 102 [I-D.ietf-hubmib-efm-epon-mib] respectively. 104 2. The Internet-Standard Management Framework 106 For a detailed overview of the documents that describe the current 107 Internet-Standard Management Framework, please refer to section 7 of 108 RFC 3410 [RFC3410]. 110 Managed objects are accessed via a virtual information store, termed 111 the Management Information Base or MIB. MIB objects are generally 112 accessed through the Simple Network Management Protocol (SNMP). 113 Objects in the MIB are defined using the mechanisms defined in the 114 Structure of Management Information (SMI). This memo specifies a MIB 115 module that is compliant to the SMIv2, which is described in STD 58, 116 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 117 [RFC2580]. A detailed introduction to the current SNMP Management 118 Framework can be found in RFC 2570 [RFC2570]. 120 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 121 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 122 document are to be interpreted as described in RFC 2119 [RFC2119]. 124 3. Relation to other MIBs 126 This section outlines the relationship of this MIB with other MIBs 127 described in the relevant RFCs. Specifically, Interfaces Group MIB 128 (IF-MIB), Ethernet-Like (EtherLike-MIB), MAU (MAU-MIB), SHDSL 129 (HDSL2-SHDSL-LINE-MIB) and VDSL (VDSL-LINE-EXT-MCM-MIB) are 130 discussed. 132 3.1 Relation to Interfaces Group MIB 134 2Base-TL and 10Pass-TS PHY's specified in this MIB are stacked 135 Ethernet interfaces and as such are managed using generic interface 136 management objects defined in the IF-MIB [RFC2863]. The stack 137 management in done via the ifStackTable, as defined in the IF-MIB 138 [RFC2863] and ifInvStackTable, as defined in the 139 IF-INVERTED-STACK-MIB [RFC2864]. 141 3.1.1 Layering Model 143 An EFMCu interface can aggregate up to 32 Physical Medium Entity 144 (PME) sublayer devices (modems), using so called PME Aggregation 145 Function (PAF). 147 An generic EFMCu device can have a number of Physical Coding Sublayer 148 (PCS) ports, connected to a MAC via Medium Independent Interface 149 (MII) at the upper layer, and cross-connected to a number of 150 underlying PMEs, with a single PCS per PME relationship, see clause 151 61.1 of [802.3ah] for more details. 153 Each PME comprising an aggregated EFMCu port is represented in the 154 Interface table as a separate port with ifType of shdsl(169) for 155 2Base-TL or vdsl(97) for 10Pass-TS. The ifType values are defined in 156 IANAifType-MIB. ifSpeed for each PME shall return an actual bitrate 157 of the active PME or a configured bitrate for pre-activated modems 158 (note that unassigned PME has its default bitrate). 160 The ifStackTable is indexed by the ifIndex values of the aggregated 161 EFMCu port (PCS) and the PMEs connected to it. ifStackTable allows a 162 Network Management application to determine which PMEs are connected 163 to a particular PCS and change connections (if supported by the 164 application). The ifInvStackTable, being an inverted version of the 165 ifStackTable, provides an efficient means for a Network Management 166 application to read a subset of the ifStackTable and thereby 167 determine which PCS runs on top of a particular PME. 169 A new table efmCuAvailableStackTable defined in this MIB, specifies 170 for each PCS a list of PMEs, which can possibly be cross-connected to 171 that PCS, determined by the cross-connect capability of the device. 172 This table, modeled after ifStackTable, is read only, reflecting 173 current cross-connect capability, which can be dynamic in some 174 implementations (e.g. if PMEs are located on a pluggable module and 175 the card is pulled out). Note that PME availability per PCS, 176 described by efmCuAvailableStackTable, can be constrained by other 177 parameters, for example by aggregation capacity of a PCS or by the 178 PME in question being already connected to another PCS. So, in order 179 to ensure that a particular PME can be connected to the PCS, all 180 respective parameters (e.g. efmCuAvailableStackTable, ifStackTable 181 and efmCuPAFCapacity) SHALL be inspected. 183 The efmCuAvailableStackTable allows to define new entries 185 *EdNote: Add efmCuInvAvailableStackTable describing which PCS ports 186 can be connected to a particular PME. Possibly move these 2 tables to 187 a separate MIB to make cross-connect capability available to other 188 MIBs for import (changing the prefix of course from 'efmCu' to say 189 'if'). * 191 3.1.2 PME Aggregation Function (PAF) 193 The PME Aggregation Function (PAF) is OPTIONAL and MAY not be 194 supported. Note however that the agent is REQUIRED to report on the 195 PAF capability for all EFMCu ports (2Base-TL and 10Pass-TS). 197 *EdNote: Add more info.* 199 3.1.3 Discovery Operation 201 This MIB allows a Network Management application to control EFM 202 Discovery mechanism and query its results. Note that the Discovery 203 mechanism can work only if PAF is supported and enabled. 205 Two tables are used by Discovery mechanism: ifStackTable and 206 efmCuAvailableStackTable defined. The following pseudo-code defines 207 an example of Discovery and automatic PME assignment for a generic 208 PAF enabled multi-PCS EFMCu device, located at Central Office (CO): 210 FOREACH pcs[i] IN co_device 211 { // Discover only on PAF enabled ports with room for more PMEs 212 IF ( pcs[i].PAFSupported AND pcs[i].NumPMEs < pcs[i].PAFCapacity ) 213 { dc = pcs[i].DiscoveryCode = MAC[i]; // unique 6 Byte per PCS 214 // go over all currently disconnected PMEs, which can 215 // pottentially be connected to PCS[i] 216 FOREACH pme[j] IN efmCuAvailableStackTable[pcs[i]] AND 217 NOT IN ifInvStackTable[pme[j]] // unassigned 218 { pme[j].RemoteDiscoveryCode = dc; // Set if Clear 219 r = pme[j].RemoteDiscoveryCode; // Get 220 IF ( r == dc AND pcs[i].NumPMEs < pcs[i].PAFCapacity) 221 { // Remote CPE connected via PME[j] is/was a peer for 222 // PCS[i]. Connect this PME to the PCS (there's room) 223 ADD pme[j] TO ifStackTable[pcs[i]]; 224 pcs[i].NumPMEs = pcs[i].NumPMEs + 1; 225 // Discover all other currently disconnected PMEs, 226 // attached to the same CPE and connect them to the PCS 227 // provided there is enough room for more PMEs. 228 FOREACH pme[k] IN efmCuAvailableStackTable[pcs[i]] and 229 NOT IN ifInvStackTable[pme[k]] 230 { r = pme[k].RemoteDiscoveryCode; // Get 231 IF ( r == dc AND 232 pcs[i].NumPMEs < pcs[i].PAFCapacity) 233 { ADD pme[k] TO ifStackTable[pcs[i]]; 234 pcs[i].NumPMEs = pcs[i].NumPMEs + 1; 235 } 236 } 237 } 238 // Discovered all PMEs which lead to the same CPE and 239 // connected them to PCS[i]. Go to the next PCS. 240 BREAK; 241 } 242 } 243 } 245 The SNMP Agent builds efmCuStackTable according to the information 246 contained in the Clause 45 PME_Available_register (see [802.3ah] 247 61.1.5.3 and 45.2.3.20). 249 Adding a PME to the ifStackTable row for a specific PCS, involves 250 actual connection of the PME to the PCS, which can be done by 251 modifying Clause 45 PME_Aggregate_register (see [802.3ah] 61.1.5.3 252 and 45.2.3.21). 254 Note that PCS port does not have to be operationally 'down' for the 255 connection to succeed. In fact, a dynamic PME addition (and removal) 256 MAY be implemented whith an available PME being initialized first (by 257 setting its ifAdminStatus to 'up') and then added to an operationally 258 'up' PCS port, by modifying a respective ifStackTable entry. 260 It is RECOMMENDED that a removal of the last operationally 'up' PME 261 from an operationally 'up' PCS would be rejected by the 262 implementation, as this action would completetly drop the link. 264 3.1.4 EFMCu ports initialization 266 EFMCu ports being built on top of xDSL technology, require a lengthy 267 initialization or 'training' process, before any data can pass. 268 During this initialization both ends of a link (peers) work 269 cooperatively to achieve required data rate on a particular copper 270 pair. Sometimes, when the copper line is too long or the noise 271 environment on the line is too high, that 'training' process may fail 272 to achieve a specific target rate with required characteristics. 274 The ifAdminStatus object from the IF-MIB, controls the desired state 275 of a PCS and a PME port. Setting this object to 'up' instructs a 276 particular PCS or PME to start initialization process, which may take 277 tens of seconds for EFMCu ports, especially if PAF is involved. The 278 ifOperStatus object shows the operational state of an interface 279 (extended by efmCuPmeOperStatus defined in this MIB for PME 280 interfaces). 282 A disconnected PME may be initialized by changing the ifAdminState 283 from 'down' to 'up'. Changing the ifAdminState to 'up' on the PCS 284 initializes all PMEs connected to that particular PCS. Note that in 285 case of PAF some interfaces may fail to initialize while others 286 suceed. The PCS is considered operationally 'up' if at least one PME 287 aggregated by its PAF is operationally 'up'. When all PMEs connected 288 to the PCS are 'down' the PCS SHALL be considered operationally 289 'lowerLayerDown'. The PCS SHALL be considered operationally 290 'notPresent' if it is not connected to any PME. The PCS/PME 291 interface SHALL remain operationally 'down' during initialization. 293 The efmCuPmeOperStatus defined in this MIB expands PME's ifOperStatus 294 value of 'down' to 'downReady', 'downNotReady' and 'init' values, 295 indicating various EFMCu PME specific states. 297 3.1.5 Usage of ifTable 299 Both PME and PCS interfaces of the EFMCu PHY are managed using 300 interface specific management objects defined in this MIB and generic 301 interface objects from the ifTable of IF-MIB, with all management 302 table entries referenced by the interface index ifIndex. 304 The following table summarizes EFMCu specific interpretations for 305 some of the ifTable objects specified by the mandatory 306 ifGeneralInformationGroup: 308 +---------------------------------+---------------------------------+ 309 | IF-MIB object | EFMCu interpretation | 310 +---------------------------------+---------------------------------+ 311 | ifIndex | Interface index. Note that each | 312 | | PME and each PCS in the EFMCu | 313 | | PHY MUST have a unique index, | 314 | | as there some PCS and PME | 315 | | specific attributes accessible | 316 | | only on the PCS or PME level. | 317 | ifType | ethernetCsmacd(6) for PCS, | 318 | | shdsl(169) for 2Base-TL PME, | 319 | | vdsl(97) for 10Pass-TS PME | 320 | ifSpeed | Actual 'net' data rate as seen | 321 | | across MII | 322 | ifAdminStatus | Setting this object to 'up' | 323 | | instructs a particular PCS | 324 | | (with all PMEs connected to it) | 325 | | or PME to start initialization | 326 | | process | 327 | ifOperStatus | efmCuPmeOperStatus supplements | 328 | | the 'down' value of | 329 | | ifOperStatus for PMEs. | 330 +---------------------------------+---------------------------------+ 332 Table 1 334 3.2 Relation to SHDSL MIB 336 G.SHDSL.bis modems, similar to PME(s) comprising a 2BaseTL port, are 337 described in HDSL2-SHDSL-LINE-MIB [I-D.ietf-adslmib-gshdslbis]. Note 338 that not all attributes of G.SHDSL modems reflected in 339 HDSL2-SHDSL-LINE-MIB have adequate management objects (Clause 30 340 attributes and Clause 45 registers) in the EFM standard. 342 Because of these differences and for the purposes of simplicity, 343 unification of attributes common to both 2Base-TL and 10Pass-TS PMES 344 and name consistency (e.g. prefixing the 2BaseTL PME related objects 345 with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided not to 346 reference HDSL2-SHDSL-LINE-MIB objects, but define all the relevant 347 objects in this MIB. 349 However, if some functionality, not available in this MIB, is 350 required and supported by the PME, e.g. performance monitoring, 351 relevant HDSL2-SHDSL-LINE-MIB groups MAY be included and aplied for 352 PMEs of 2Base-TL subtype. 354 3.3 Relation to VDSL MIB 356 VDSL (DMT) modems, similar to the PME(s) comprising a 10PassTS port, 357 are described in VDSL-LINE-EXT-MCM-MIB 358 [I-D.ietf-adslmib-vdsl-ext-mcm]. Note that not all attributes of 359 VDSL modems reflected in VDSL-LINE-EXT-MCM-MIB have adequate 360 management objects (Clause 30 attributes and Clause 45 registers) in 361 the EFM standard. 363 Because of these differences and for the purposes of simplicity, 364 unification of attributes common to both 2Base-TL and 10Pass-TS PMES 365 and name consistency, it was decided not to reference 366 VDSL-LINE-EXT-MCM-MIB objects, but define all the relevant objects in 367 this MIB. 369 However, if some functionality, not available in this MIB, is 370 required and supported by the PME, relevant VDSL-LINE-EXT-MCM-MIB 371 groups MAY be included and applied for PMEs of 10Pass-TS subtype. 373 3.4 Relation to Ethernet-Like and MAU MIBs 375 The implementation of EtherLike-MIB [RFC3635] and MAU-MIB [RFC3636] 376 is REQUIRED for the EFMCu interfaces. As such EFMCu interfaces 377 2Base-TL/10Pass-TS SHALL return an ifType of ethernetCsmacd(6). 378 Information on the particular flavor of EFMCu that an interface is 379 running is available from ifSpeed in the IF-MIB [RFC2863], and 380 ifMauType in the MAU-MIB. 382 The MAU-MIB shall be augmented to include the following new values 383 for ifMauType (instances of dot2MauType): 385 o dot3MauType2BaseTL - voice grade UTP Phy specified in Clause 61 386 and 63 388 o dot3MauType10PassTS - voice grade UTP Phy specified in Clause 61 389 and 62 391 *EdNote: Should we also include -O/-R subtypes?* 393 4. MIB Structure 395 4.1 Overview 397 The main management objects defined in this MIB are split into 2 398 groups: 400 o efmCuPort - containing objects for configuration, capabilities, 401 status and notifications, common to all EFMCu PHYs. 403 o efmCuPme - containing objects for configuration, capabilities, 404 status and notifications of EFMCu PMEs. 406 In addition the efmCuAvailableStackTable is defined at the same 407 level. 409 The efmCuPme group in turn contains efmCuPme2B and efmCuPme10P 410 groups, which define configuration profiles specific to 2BaseTL and 411 10PassTS PMEs respectively as well as PME specific status 412 information. 414 4.2 Configuration Profiles 416 Since a managed node can have a large number of EFMCu PHYs, 417 provisioning every parameter on every EFMCu PHY may become 418 burdensome. Moreover, most PMEs are provisioned identically with the 419 same set of parameters. To simplify the provisioning process, this 420 MIB makes use of configuration profiles, similar to 421 HDSL2-SHDSL-LINE-MIB and VDSL-LINE-EXT-MCM-MIB. A profile is a set 422 of parameters that can be shared by multiple PME ports using the same 423 configuration. 425 The configuration profiles are defined in efmCuPme2BConfProfileTable 426 and efmCu10PConfProfileTable for 2Base-TL and 10Pass-TS PMEs 427 respectively. There are 12 predefined standard profiles for 2Base-TL 428 and 22 standard profiles for 10Pass-TS, defined in 802.3ah and 429 dedicated for rapid provisioning of EFMCu PHYs in most scenarios. An 430 ability to define new configuration profiles is also provided to 431 allow for EFMCu deployment tailored to specific copper environment 432 and spectral regulations. 434 A specific configuration profile is assigned to a specific PME via 435 efmCuPmeAdminProfile object. Alternatively, by assigning a non-empty 436 profile to a PCS port via efmCuAdminProfile, all PMEs connected to 437 the PCS port are made to share that profile, which comes handy during 438 configuration of aggregated ports. 440 4.3 Mapping of IEEE 802.3ah Managed Objects 442 This section contains the mapping between managed objects 443 (attributes) defined in [802.3ah] Clause 30, and managed objects 444 defined in this document and in associated MIB modules, i.e., the 445 IF-MIB [RFC2863]. 447 Note that majority of the objects defined in this MIB do not have 448 direct counterparts in Clause 30 and instead refer to Clause 45 449 registers. 451 *EdNote: It would be a good idea to update Clause 30 of 802.3ah after 452 this MIB is approved. I guess this should be done via a maintanence 453 request. * 455 +---------------------------------+---------------------------------+ 456 | IEEE 802.3 Managed Object | Corresponding SNMP Object | 457 +---------------------------------+---------------------------------+ 458 | oPAF - PME Basic Package | | 459 | (Mandatory) | | 460 | aPAFID | ifIndex (IF-MIB) | 461 | aPhyEnd | efmCuPhySide | 462 | aPHYCurrentStatus | efmCuStatus | 463 | aPAFSupported | efmCuPAFSupported | 464 | oPAF - PME Aggregation Package | | 465 | (Optional) | | 466 | aPAFAdminState | efmCuPAFAdminState | 467 | aPAFID | ifIndex (IF-MIB) | 468 | aLocalPAFCapacity | efmCuPAFCapacity | 469 | aLocalPMEAvailable | efmCuAvailableStackTable | 470 | aLocalPMEAggregate | ifStackTable (IF-MIB) | 471 | aRemotePAFSupported | efmCuRemotePAFSupported | 472 | aRemotePAFCapacity | efmCuRemotePAFCapacity | 473 | aRemotePMEAvailable | | 474 | aRemotePMEAggregate | | 475 | oPME - 10P/2B Package | | 476 | (Mandatory) | | 477 | aPMEID | ifIndex (IF-MIB) | 478 | aPMEAdminState | ifAdminState (IF-MIB) | 479 | aPMEStatus | efmCuPmeStatus | 480 | aPMESNRMgn | efmCuPmeSnrMgn | 481 | aTCCodingViolations | efmCuPmeTCCodingErrors | 482 | aProfileSelect | efmCuAdminProfile, | 483 | | efmCuPmeAdminProfile | 484 | aOperatingProfile | efmCuPmeOperProfile | 485 | aPMEFECCorrectedBlocks | efmCuPme10PFECCorrectedBlocks | 486 | aPMEFECUncorrectableBlocks | efmCuPme10PFECUncorrectedBlocks | 487 +---------------------------------+---------------------------------+ 489 Table 2 491 5. Definitions 493 EFM-CU-MIB DEFINITIONS ::= BEGIN 495 IMPORTS 496 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32, 497 Unsigned32, Counter32, mib-2 498 FROM SNMPv2-SMI -- [RFC2578] 499 TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress 500 FROM SNMPv2-TC -- [RFC2579] 501 SnmpAdminString 502 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 503 ifIndex, ifSpeed, InterfaceIndex 504 FROM IF-MIB -- [RFC2863] 505 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 506 FROM SNMPv2-CONF -- [RFC2580] 507 ; 509 efmCuMIB MODULE-IDENTITY 510 LAST-UPDATED "200407150000Z" -- July 15, 2004 511 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" 512 CONTACT-INFO 513 "WG charter: 514 http://www.ietf.org/html.charters/hubmib-charter.html 516 Mailing Lists: 517 General Discussion: hubmib@ietf.org 518 To Subscribe: hubmib-request@ietf.org 519 In Body: subscribe your_email_address 521 Chair: Dan Romascanu 522 Postal: Avaya 523 Atidim Technology Park, Bldg. 3 524 Tel Aviv 61131 525 Israel 526 Tel: +972 3 645 8414 527 E-mail: dromasca@avaya.com 529 Editor: Edward Beili 530 Postal: Actelis Networks Inc. 531 25 Bazel St., P.O.B. 10173 532 Petach-Tikva 10173 533 Israel 534 Tel: +972-3-924-3491 535 E-mail: edward.beili@actelis.com" 537 DESCRIPTION 538 "The objects in this MIB module are used to manage 539 the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces 540 2BASE-TL and 10PASS-TS, defined in IEEE Draft P802.3ah/D3.3. 542 The following reference is used throughout this MIB module: 544 [802.3ah] refers to: 545 IEEE Draft P802.3ah/D3.3: 'Draft amendment to - 546 Information technology - Telecommunications and 547 information exchange between systems - Local and 548 metropolitan area networks - Specific requirements - 549 Part 3: Carrier sense multiple access with collision 550 detection (CSMA/CD) access method and physical layer 551 specifications - Media Access Control Parameters, Physical 552 Layers and Management Parameters for subscriber access 553 networks', 19 April 2003. 555 Of particular interest are Clause 61, 'Physical Coding 556 Sublayer (PCS) and common specifications, type 10PASS-TS and 557 type 2BASE-TL', Clause 30, 'Management', and Clause 45, 558 'Management Data Input/Output (MDIO) Interface'. 560 Naming Conventions: 561 Atn - Attenuation 562 CO - Central Office 563 CPE - Customer Premises Equipment 564 EFM - Ethernet in the First Mile 565 EFMCu - EFM Copper 566 MDIO - Management Data Input/Output 567 Mgn - Margin 568 PAF - PME Aggregation Function 569 PCS - Physical Coding Sublayer 570 PMD - Physical Medium Dependent 571 PME - Physical Medium Entity 572 PSD - Power Spectral Density 573 SNR - Signal to Noise Ratio 574 TCPAM - Trellis Coded Pulse Amplitude Modulation 576 Copyright (C) The Internet Society (2004). This version 577 of this MIB module is part of RFC XXXX; see the RFC 578 itself for full legal notices." 580 -- EdNote: Replace XXXX with the actual RFC number & 581 -- remove this note 583 REVISION "200407150000Z" -- July 15, 2004 584 DESCRIPTION "Initial version, published as RFC XXXX." 586 ::= { mib-2 YYY } 588 -- EdNote: Replace YYY with a real OID once it is 589 -- allocated & remove this note. 591 -- Sections of the module 593 efmCuObjects OBJECT IDENTIFIER ::= { efmCuMIB 1 } 594 efmCuConformance OBJECT IDENTIFIER ::= { efmCuMIB 2 } 596 -- Groups in the module 598 efmCuPort OBJECT IDENTIFIER ::= { efmCuObjects 1 } 600 efmCuPme OBJECT IDENTIFIER ::= { efmCuObjects 2 } 602 -- Textual Conventions 604 ProfileIndex ::= TEXTUAL-CONVENTION 605 DISPLAY-HINT "d" 606 STATUS current 607 DESCRIPTION 608 "A unique value, greater than zero, for each PME configuration 609 profile in the managed EFMCu port. It is recommended that 610 values are assigned contiguously starting from 1. The value 611 for each profile must remain constant at least from one 612 re-initialization of the entity's network management system 613 to the next re-initialization." 614 SYNTAX Unsigned32 (1..255) 616 ProfileIndexOrZero ::= TEXTUAL-CONVENTION 617 DISPLAY-HINT "d" 618 STATUS current 619 DESCRIPTION 620 "This textual convention is an extension of the ProfileIndex 621 convention. The latter defines a greater than zero value used 622 to identify a PME profile in the managed EFMCu port. This 623 extension permits the additional value of zero. The value of 624 zero is object-specific and must therefore be defined as part 625 of the description of any object which uses this syntax. 626 Examples of the usage of zero value migh include situations 627 where current operational profile is unknown." 628 SYNTAX Unsigned32 (0..255) 630 ProfileIndexList ::= TEXTUAL-CONVENTION 631 DISPLAY-HINT "1d:" 632 STATUS current 633 DESCRIPTION 634 "Represents a list of up to 6 ProfileIndex's. 635 The ProfileIndex textual convention defines a greater than 636 zero value used to identify a PME profile in the managed EFMCu 637 port. The value of this object is a concatenation of zero or 638 more (up to 6) octets, where each octet contains an 8-bit 639 ProfileIndex value. 640 A non-empty profile list specifies a list of alternative 641 profiles any of which can be chosen for configuration of an 642 PME. A zero length string value means this list has no members 643 (empty). Examples of the usage of empty profile list might 644 include situations where configuration profile(s) is unknown, 645 or when no common profile(s) need to be referenced and 646 sub-interface profile shall take precedence." 647 SYNTAX OCTET STRING (SIZE(0..6)) 649 -- Port Notifications Group 651 efmCuPortNotifications OBJECT IDENTIFIER ::= { efmCuPort 0 } 653 efmCuLowBandwidth NOTIFICATION-TYPE 654 OBJECTS { 655 -- ifINdex is not needed here since we are under specific PCS 656 ifSpeed, 657 efmCuThreshLowBandwidth 658 } 659 STATUS current 660 DESCRIPTION 661 "This notification indicates that EFMCu port's data rate 662 reached or droped below a Low Bandwidth Threshold 663 (i.e. bandwidth degradation happening in case of PAF when one 664 or more PMEs drop)." 665 -- EdNote: add throttling limitations here 666 ::= { efmCuPortNotifications 1 } 668 -- PCS Port group 670 efmCuPortConfTable OBJECT-TYPE 671 SYNTAX SEQUENCE OF EfmCuPortConfEntry 672 MAX-ACCESS not-accessible 673 STATUS current 674 DESCRIPTION 675 "Table for Configuration of EFMCu 2BaseTL/10PassTS (PCS) 676 Ports. Entries in this table MUST be maintained in a 677 persistent manner" 678 ::= { efmCuPort 1 } 680 efmCuPortConfEntry OBJECT-TYPE 681 SYNTAX EfmCuPortConfEntry 682 MAX-ACCESS not-accessible 683 STATUS current 684 DESCRIPTION 685 "An entry in the EFMCu Port Configuration table. 686 Each entry represents an EFMCu port indexed by the ifIndex. 687 Note that an EFMCu PCS port runs on top of a single 688 or multiple PME port(s), which are also indexed by ifIndex." 689 INDEX { ifIndex } 690 ::= { efmCuPortConfTable 1 } 692 EfmCuPortConfEntry ::= 693 SEQUENCE { 694 efmCuPAFAdminState INTEGER, 695 efmCuPAFDiscoveryCode PhysAddress, 696 efmCuAdminProfile ProfileIndexList, 697 efmCuTargetDataRate Unsigned32, 698 efmCuTargetSnrMgn Unsigned32, 699 efmCuThreshLowBandwidth Unsigned32, 700 efmCuLowBandwidthEnable TruthValue 701 } 703 efmCuPAFAdminState OBJECT-TYPE 704 SYNTAX INTEGER { 705 enabled(1), 706 disabled(2) 707 } 708 MAX-ACCESS read-write 709 STATUS current 710 DESCRIPTION 711 "Administrative (desired) state of the PAF of the EFMCu port 712 (PCS). 713 When 'disabled', PME Aggregation will not be performed by the 714 PCS. No more than a single PME can be assigned to this PCS in 715 this case. 716 When 'enabled', PAF will be performed by the PCS when the link 717 is Up, even on a single attached PME, if PAF is supported. 719 PCS ports incapable of supporting PAF SHALL return a value of 720 'disabled'. Attempts to 'enable' such ports SHALL be ignored. 722 PAF 'enabled' port with multiple PMEs assigned cannot be 723 'disabled'. Attempts to 'disable' such port SHALL be rejected, 724 untill at most one PME is left assigned. 726 Changing PAFAdminState is a traffic disruptive operation and 727 as such SHALL be done when the link is Down. Attempts to 728 change this object SHALL be ignored if the link is Up or 729 Initializing. 731 This object maps to the Clause 30 attribute aPAFAdminState. 733 If a Clause 45 MDIO Interface to the PCS is present, then this 734 object maps to the PAF enable bit in the 10P/2B PCS control 735 register." 736 REFERENCE 737 "[802.3ah] 61.2.2, 45.2.3.18.3" 739 ::= { efmCuPortConfEntry 1 } 741 efmCuPAFDiscoveryCode OBJECT-TYPE 742 SYNTAX PhysAddress 743 MAX-ACCESS read-write 744 STATUS current 745 DESCRIPTION 746 "PAF Discovery Code of the EFMCu port (PCS). 747 A unique 6 Byte long code used by the Discovery function, when 748 PAF is supported. 749 PCS ports incapable of supporting PAF SHALL return a value of 750 all zeroes. Attempts to change this object SHALL be ignored in 751 this case. 752 This object MUST be instantiated for the -O subtype PCS before 753 writing operations on the efmCuPAFRemoteDiscoveryCode 754 (Set_if_Clear and Clear_if_Same) are performed by PMEs 755 associated with the PCS. 756 The value of this object is read-only for -R port subtypes. 757 The initial value of this object for -R ports after reset 758 is 0. This value may be changed as a result of writing 759 operation on efmCuPAFRemoteDiscoveryCode variable of remote 760 PME of -O subtype, connected to one of the local PMEs 761 associated with the PCS. 763 Discovery MUST be performed when the link is Down. 764 Attempts to change this object MUST be rejected with the error 765 inconsistentValue if the link is Up or Initializing. 767 The PAF Discovery code maps to the local Discovery code 768 variable in PAF (note that it does not have a corresponding 769 Clause 45 register)" 770 REFERENCE 771 "[802.3ah] 61.2.2.8.3, 61.2.2.8.4, 45.2.6.6.1" 772 ::= { efmCuPortConfEntry 2 } 774 efmCuAdminProfile OBJECT-TYPE 775 SYNTAX ProfileIndexList 776 MAX-ACCESS read-write 777 STATUS current 778 DESCRIPTION 779 "Desired configuration profile(s), common for all PMEs in the 780 EFMCu port. This object is a list of pointers to entries in 781 either efmCuPme2BConfProfileTable or 782 efmCuPme10PConfProfileTable, depending on the current 783 operating SubType of the EFMCu port as indicated by 784 efmCuPortSide. 785 The value of this object is a list of up to 6 indices of 786 configuration profiles. If this list consists of a single 787 Profile index, then all PMEs assigned to this EFMCu port SHALL 788 be configured according to the Configuration Profile 789 referenced by that index. The list, consisting of more than 790 one index, allows each PME in the port to be configured 791 according to any configuration profile specified in the list. 792 An empty list means that each PME in the port is configured 793 via corresponding efmCuPmeAdminProfile object. 795 This object is writable and readable for the -O subtype 796 (2BaseTL-O or 10PassTS-O) EFMCu ports. It is unavailable for 797 the -R subtype (2BaseTL-R or 10PassTS-R) ports. 799 Note that current operational Profile value is available via 800 efmCuPmeOperProfile object. 802 Modification of this object must be performed when the link is 803 Down. Attempts to change this object MUST be rejected, if the 804 link is Up or Initializing. 805 Attempts to set this object to a non-empty list with a member 806 value, that is not the value of the index for an active entry 807 in the corresponding profile table, MUST be rejected." 808 REFERENCE 809 "[802.3ah] 30.11.2.1.6" 810 ::= { efmCuPortConfEntry 3 } 812 efmCuTargetDataRate OBJECT-TYPE 813 SYNTAX Unsigned32(1..100000|999999) 814 UNITS "Kbps" 815 MAX-ACCESS read-write 816 STATUS current 817 DESCRIPTION 818 "Desired EFMCu port 'net' (as seen across MII) Data Rate in 819 Kbps, to be achieved during initialization, under spectral 820 restrictions placed on each PME via efmCuAdminProfile or 821 efmCuPmeAdminProfile, with the desired SNR Margin specified by 822 efmCuTargetSnrMgn. 823 In case of PAF, this object represents a sum of individual PME 824 data rates, modified to compensate for fragmentation and 825 64/65B framing overhead (e.g. target data rate of 10Mbps 826 shall allow lossless transmission of full-duplex 10Mbps 827 Ethernet frame stream with minimal inter-frame gap). 829 The value is limited above by 100Mbps as this is the max 830 burst rate across MII for EFMCu ports. 832 The value between 1 and 100000 indicates that the total data 833 rate (ifSpeed) of the EFMCu port after initialization should 834 be equal to the target data rate or less, if the target data 835 rate cannot be achieved under spectral restrictions specified 836 by efmCuAdminProfile/efmCiPmeAdminProfile and with desired SNR 837 margin. In case the copper environment allows to achieve 838 higher total data rate than specified by the target, the 839 excess capability SHALL be converted to additional SNR margin 840 and spread evenly across all active PMEs assigned to the (PCS) 841 port. 843 The value of 999999 means that the target data rate is not 844 fixed and should be set to the maximum attainable rate during 845 initialization (Best Effort), under specified spectral 846 restrictions and with desired SNR Margin. 848 This object is read-write for the -O subtype EFMCu ports 849 (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. 851 Changing of the Target Data Rate MUST be performed when the 852 link is Down. Attempts to change this object MUST be rejected 853 with the error inconsistentValue, if the link is Up or 854 Initializing. 856 Note that current Data Rate of the EFMCu port is represented 857 by ifSpeed object of IF-MIB." 858 ::= { efmCuPortConfEntry 4 } 860 efmCuTargetSnrMgn OBJECT-TYPE 861 SYNTAX Unsigned32(0..21) 862 UNITS "dB" 863 MAX-ACCESS read-write 864 STATUS current 865 DESCRIPTION 866 "Desired EFMCu port SNR Margin to be achieved on all PMEs 867 assigned to the port, during initializiation. (The SNR margin 868 is the difference between the desired SNR and the actual SNR). 870 Note that 802.3ah recommends using default Target SNR Margin 871 of 5dB for 2BaseTL ports and 6dB for 10PassTS ports in order 872 to achieve mean Bit Error Rate (BER) of 10^-7 at the PMA 873 service interface. 875 This object is read-write for the -O subtype EFMCu ports 876 (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. 878 Changing of the Target SNR Margin MUST be performed when the 879 link is Down. Attempts to change this object MUST be rejected 880 with the error inconsistentValue, if the link is Up or 881 Initializing. 883 Note that current SNR Margin of the PMEs comprising the EFMCu 884 port is represented by efmCuPmeSnrMgn." 885 REFERENCE 886 "[802.3ah] 61.1.2" 887 ::= { efmCuPortConfEntry 5 } 889 efmCuThreshLowBandwidth OBJECT-TYPE 890 SYNTAX Unsigned32(0..100000) 891 UNITS "Kbps" 892 MAX-ACCESS read-write 893 STATUS current 894 DESCRIPTION 895 "This object configures the EFMCu port Low Bandwidth alarm 896 threshold. When the current value of ifSpeed for this port 897 reaches or drops below this threshold, an 898 efmCuLowBandwidth notification MAY be generated if enabled by 899 efmCuLowBandwidthEnable. 901 The value of 0 means no efmCuLowBandwidth notifications 902 SHALL ever be generated. 904 This object is read-write for the -O subtype EFMCu ports 905 (2BaseTL-O/10PassTS-O) and not available for the -R subtypes." 906 ::= { efmCuPortConfEntry 6 } 908 efmCuLowBandwidthEnable OBJECT-TYPE 909 SYNTAX TruthValue 910 MAX-ACCESS read-write 911 STATUS current 912 DESCRIPTION 913 "Indicates whether efmCuLowBandwidth notifications should be 914 generated for this interface. 916 Value of truth(1) indicates that efmCuLowBandwidth 917 notification is enabled. Value of false(0) indicates the it is 918 disabled." 919 ::= { efmCuPortConfEntry 7 } 921 efmCuPortCapabilityTable OBJECT-TYPE 922 SYNTAX SEQUENCE OF EfmCuPortCapabilityEntry 923 MAX-ACCESS not-accessible 924 STATUS current 925 DESCRIPTION 926 "Table for Capabilities of EFMCu 2BaseTL/10PassTS (PCS) 927 Ports. Entries in this table MUST be maintained in a 928 persistent manner" 929 ::= { efmCuPort 2 } 931 efmCuPortCapabilityEntry OBJECT-TYPE 932 SYNTAX EfmCuPortCapabilityEntry 933 MAX-ACCESS not-accessible 934 STATUS current 935 DESCRIPTION 936 "An entry in the EFMCu Port Capability table. 937 Each entry represents an EFMCu port indexed by the ifIndex. 938 Note that an EFMCu PCS port runs on top of a single 939 or multiple PME port(s), which are also indexed by ifIndex." 940 INDEX { ifIndex } 941 ::= { efmCuPortCapabilityTable 1 } 943 EfmCuPortCapabilityEntry ::= 944 SEQUENCE { 945 efmCuPAFSupported TruthValue, 946 efmCuPeerPAFSupported TruthValue, 947 efmCuPAFCapacity Unsigned32, 948 efmCuPeerPAFCapacity Unsigned32 949 } 951 efmCuPAFSupported OBJECT-TYPE 952 SYNTAX TruthValue 953 MAX-ACCESS read-only 954 STATUS current 955 DESCRIPTION 956 "PME Aggregation Function (PAF) Capability of the EFMCu port 957 (PCS). 958 This object has a value of true(1) when the PCS can perform 959 PME aggregation on the available PMEs. 960 Ports incapable of PAF SHALL return a value of false(2). 962 This object maps to the Clause 30 attribute aPAFSupported. 964 If a Clause 45 MDIO Interface to the PCS is present, 965 then this object maps to the PAF available bit in the 966 10P/2B capability register." 967 REFERENCE 968 "[802.3ah] 61.2.2, 30.11.1.1.4, 45.2.3.17.1" 969 ::= { efmCuPortCapabilityEntry 1 } 971 efmCuPeerPAFSupported OBJECT-TYPE 972 SYNTAX TruthValue 973 MAX-ACCESS read-only 974 STATUS current 975 DESCRIPTION 976 "PME Aggregation Function (PAF) Capability of the EFMCu port 977 (PCS) link partner. 978 This object has a value of true(1) when the remote PCS can 979 perform PME aggregation on its available PMEs. 980 Ports whose peers are incapable of PAF or cannot be reached 981 because of the link state, SHALL return a value of false(2). 983 This object maps to the Clause 30 attribute 984 aRemotePAFSupported. 986 If a Clause 45 MDIO Interface to the PCS is present, then 987 this object maps to the Remote PAF supported bit in the 988 10P/2B capability register." 989 REFERENCE 990 "[802.3ah] 61.2.2, 30.11.1.1.9, 45.2.3.17.2" 991 ::= { efmCuPortCapabilityEntry 2 } 993 efmCuPAFCapacity OBJECT-TYPE 994 SYNTAX Unsigned32 (1..32) 995 MAX-ACCESS read-only 996 STATUS current 997 DESCRIPTION 998 "Number of PMEs that can be aggregated by the local PAF. 999 The number of PMEs currently assigned to a particluar 1000 EFMCu port (efmCuNumPMEs) is never greater than 1001 efmCuPAFCapacity. 1003 This object maps to the Clause 30 attribute 1004 aLocalPAFCapacity." 1005 REFERENCE 1006 "[802.3ah] 61.2.2, 30.11.1.1.6" 1007 ::= { efmCuPortCapabilityEntry 3 } 1009 efmCuPeerPAFCapacity OBJECT-TYPE 1010 SYNTAX Unsigned32 (0|1..32) 1011 MAX-ACCESS read-only 1012 STATUS current 1013 DESCRIPTION 1014 "Number of PMEs that can be aggregated by the PAF of the peer 1015 Phy (PCS port). 1016 Value of 0 is returned when peer PAF Capacity is unknown 1017 (peer cannot be reached). 1019 This object maps to the Clause 30 attribute 1020 aRemotePAFCapacity." 1021 REFERENCE 1022 "[802.3ah] 61.2.2, 30.11.1.1.10" 1023 ::= { efmCuPortCapabilityEntry 4 } 1025 efmCuPortStatusTable OBJECT-TYPE 1026 SYNTAX SEQUENCE OF EfmCuPortStatusEntry 1027 MAX-ACCESS not-accessible 1028 STATUS current 1029 DESCRIPTION 1030 "This table provides overall status information of EFMCu 1031 2BaseTL/10PassTS ports. This table contains live data from 1032 the equipment. As such, it is NOT persistent." 1033 ::= { efmCuPort 3 } 1035 efmCuPortStatusEntry OBJECT-TYPE 1036 SYNTAX EfmCuPortStatusEntry 1037 MAX-ACCESS not-accessible 1038 STATUS current 1039 DESCRIPTION 1040 "An entry in the EFMCu Port Status table. 1041 Each entry represents an EFMCu port indexed by the ifIndex. 1042 Note that an EFMCu PCS port runs on top of a single 1043 or multiple PME port(s), which are also indexed by ifIndex." 1044 INDEX { ifIndex } 1045 ::= { efmCuPortStatusTable 1 } 1047 EfmCuPortStatusEntry ::= 1048 SEQUENCE { 1049 efmCuFltStatus BITS, 1050 efmCuPortSide INTEGER, 1051 efmCuNumPMEs Unsigned32, 1052 efmCuPAFInErrors Counter32, 1053 efmCuPAFInSmallFragments Counter32, 1054 efmCuPAFInLargeFragments Counter32, 1055 efmCuPAFInBadFragments Counter32, 1056 efmCuPAFInLostFragments Counter32, 1057 efmCuPAFInLostStarts Counter32, 1058 efmCuPAFInLostEnds Counter32, 1059 efmCuPAFInOverflows Counter32 1060 } 1062 efmCuFltStatus OBJECT-TYPE 1063 SYNTAX BITS { 1064 noPeer(0), -- peer Phy cannot be reached 1065 pmeSubTypeMismatch(1), -- Assigned PMEs Sub-type Mismatch 1066 lowBandwidth(2) -- Low Bandwidth 1067 } 1068 MAX-ACCESS read-only 1069 STATUS current 1070 DESCRIPTION 1071 "EFMCu (PCS) port Fault Status. This is a bitmap of possible 1072 conditions. The various bit positions are: 1073 noPeer - peer PHY cannot be reached (e.g. 1075 no PMEs attached, all PMEs are Down 1076 etc.) More info is available in 1077 efmCuPmeFltStatus. 1078 pmeSubTypeMismatch - PMEs in the aggregation group are not 1079 of the same sub-type, e.g. PMEs with 1080 -O and -R subtype 1081 lowBandwidth - ifSpeed of the port reached or droped 1082 below efmCuThreshLowBandwidth 1084 This object is intended to supplement ifOperStatus object 1085 in IF-MIB. 1086 Additional information is available via efmCuPmeFltStatus 1087 object for each PME in the aggregation group (single PME if 1088 PAF is disabled)." 1089 REFERENCE 1090 "ifOperStatus in IF-MIB; efmCuPmeFltStatus" 1091 ::= { efmCuPortStatusEntry 1 } 1093 efmCuPortSide OBJECT-TYPE 1094 SYNTAX INTEGER { 1095 subscriber(1), -- -R sub-type 1096 office(2), -- -O sub-type 1097 unknown(3) -- no PMEs assigned or PME sub-type mismatch 1098 } 1099 MAX-ACCESS read-only 1100 STATUS current 1101 DESCRIPTION 1102 "EFM port mode of operation (subtype). 1103 The value of 'subscriber' indicates the port is designated as 1104 '-R' subtype (all PMEs assigned to this port are of subtype 1105 '-R'). 1106 The value of the 'office' indicates that the port is 1107 designated as '-O' subtype (all PMEs assigned to this port are 1108 of subtype '-O'). 1109 The value of 'unknown' indicates that the port has no assigned 1110 PMEs yet or that the assigned PMEs are not of the same side 1111 (subTypePMEMismatch). 1113 This object partially maps to the Clause 30 attribute 1114 aPhyEnd" 1115 REFERENCE 1116 "[802.3ah] 61.1, 30.11.1.1.2" 1117 ::= { efmCuPortStatusEntry 2 } 1119 efmCuNumPMEs OBJECT-TYPE 1120 SYNTAX Unsigned32 (0..32) 1121 MAX-ACCESS read-only 1122 STATUS current 1123 DESCRIPTION 1124 "Number of PMEs that is currently aggregated by the local PAF 1125 (assigned to the EFMCu port using ifStackTable). 1126 This number is never greater than efmCuPAFCapacity. 1128 This object SHALL be automatically incremented or decremented 1129 when a PME is added or deleted to/from the EFMCu port using 1130 ifStackTable." 1131 REFERENCE 1132 "[802.3ah] 61.2.2, 30.11.1.1.6" 1133 ::= { efmCuPortStatusEntry 3 } 1135 efmCuPAFInErrors OBJECT-TYPE 1136 SYNTAX Counter32 1137 MAX-ACCESS read-only 1138 STATUS current 1139 DESCRIPTION 1140 "A number of fragments that have been received across the 1141 gamma interface with RxErr asserted and discarded. 1142 This read-only counter is inactive (not incremented) when the 1143 PAF is unsupported or disabled. Upon disabling the PAF, the 1144 counter retains its previous value. 1146 If a Clause 45 MDIO Interface to the PCS is present, then 1147 this object maps to the 10P/2B PAF RX error register." 1148 REFERENCE 1149 "[802.3ah] 45.2.3.21" 1150 ::= { efmCuPortStatusEntry 4 } 1152 efmCuPAFInSmallFragments OBJECT-TYPE 1153 SYNTAX Counter32 1154 MAX-ACCESS read-only 1155 STATUS current 1156 DESCRIPTION 1157 "A number of fragments smaller than minFragmentSize 1158 (64 Bytes), that have been received across the gamma interface 1159 and discarded. 1160 This read-only counter is inactive when the PAF is 1161 unsupported or disabled. Upon disabling the PAF, the counter 1162 retains its previous value. 1164 If a Clause 45 MDIO Interface to the PCS is present, then 1165 this object maps to the 10P/2B PAF small fragments 1166 register." 1167 REFERENCE 1168 "[802.3ah] 45.2.3.22" 1169 ::= { efmCuPortStatusEntry 5 } 1171 efmCuPAFInLargeFragments OBJECT-TYPE 1172 SYNTAX Counter32 1173 MAX-ACCESS read-only 1174 STATUS current 1175 DESCRIPTION 1176 "A number of fragments larger than maxFragmentSize 1177 (512 Bytes), that have been received across the gamma 1178 interface and discarded. 1179 This read-only counter is inactive when the PAF is 1180 unsupported or disabled. Upon disabling the PAF, the counter 1181 retains its previous value. 1183 If a Clause 45 MDIO Interface to the PCS is present, then 1184 this object maps to the 10P/2B PAF large fragments 1185 register." 1186 REFERENCE 1187 "[802.3ah] 45.2.3.23" 1188 ::= { efmCuPortStatusEntry 6 } 1190 efmCuPAFInBadFragments OBJECT-TYPE 1191 SYNTAX Counter32 1192 MAX-ACCESS read-only 1193 STATUS current 1194 DESCRIPTION 1195 "A number of fragments which do not fit into the sequence 1196 expected by the frame assembly function, that have been 1197 received across the gamma interface and discarded (the 1198 frame buffer is flushed to the next valid frame start). 1199 This read-only counter is inactive when the PAF is 1200 unsupported or disabled. Upon disabling the PAF, the counter 1201 retains its previous value. 1203 If a Clause 45 MDIO Interface to the PCS is present, then 1204 this object maps to the 10P/2B PAF bad fragments 1205 register." 1206 REFERENCE 1207 "[802.3ah] 45.2.3.25" 1208 ::= { efmCuPortStatusEntry 7 } 1210 efmCuPAFInLostFragments OBJECT-TYPE 1211 SYNTAX Counter32 1212 MAX-ACCESS read-only 1213 STATUS current 1214 DESCRIPTION 1215 "A number of gaps in the sequence of fragments, that have been 1216 received across the gamma interface (the frame buffer is 1217 flushed to the next valid frame start, when fragment/fragments 1218 expected by the frame assembly function is/are not received). 1220 This read-only counter is inactive when the PAF is 1221 unsupported or disabled. Upon disabling the PAF, the counter 1222 retains its previous value. 1224 If a Clause 45 MDIO Interface to the PCS is present, then 1225 this object maps to the 10P/2B PAF lost fragment 1226 register." 1227 REFERENCE 1228 "[802.3ah] 45.2.3.26" 1229 ::= { efmCuPortStatusEntry 8 } 1231 efmCuPAFInLostStarts OBJECT-TYPE 1232 SYNTAX Counter32 1233 MAX-ACCESS read-only 1234 STATUS current 1235 DESCRIPTION 1236 "A number of missing StartOfPacket indicators expected by the 1237 frame assembly function. 1238 This read-only counter is inactive when the PAF is 1239 unsupported or disabled. Upon disabling the PAF, the counter 1240 retains its previous value. 1242 If a Clause 45 MDIO Interface to the PCS is present, then 1243 this object maps to the 10P/2B PAF lost start of fragment 1244 register." 1245 REFERENCE 1246 "[802.3ah] 45.2.3.27" 1247 ::= { efmCuPortStatusEntry 9 } 1249 efmCuPAFInLostEnds OBJECT-TYPE 1250 SYNTAX Counter32 1251 MAX-ACCESS read-only 1252 STATUS current 1253 DESCRIPTION 1254 "A number of missing EndOfPacket indicators expected by the 1255 frame assembly function. 1256 This read-only counter is inactive when the PAF is 1257 unsupported or disabled. Upon disabling the PAF, the counter 1258 retains its previous value. 1260 If a Clause 45 MDIO Interface to the PCS is present, then 1261 this object maps to the 10P/2B PAF lost start of fragment 1262 register." 1263 REFERENCE 1264 "[802.3ah] 45.2.3.28" 1265 ::= { efmCuPortStatusEntry 10 } 1267 efmCuPAFInOverflows OBJECT-TYPE 1268 SYNTAX Counter32 1269 MAX-ACCESS read-only 1270 STATUS current 1271 DESCRIPTION 1272 "A number of fragements, received accross the gamma interface 1273 and discarded, which would have caused the frame assembly 1274 buffer to overflow. 1275 This read-only counter is inactive when the PAF is 1276 unsupported or disabled. Upon disabling the PAF, the counter 1277 retains its previous value. 1279 If a Clause 45 MDIO Interface to the PCS is present, then 1280 this object maps to the 10P/2B PAF overflow register." 1281 REFERENCE 1282 "[802.3ah] 45.2.3.24" 1283 ::= { efmCuPortStatusEntry 11 } 1285 -- PME Notifications Group 1287 efmCuPmeNotifications OBJECT IDENTIFIER ::= { efmCuPme 0 } 1289 -- EdNote: Should I add more notifications here, for example 1290 -- efmCuPmePerfES, 1291 -- efmCuPmePerfSES, 1292 -- efmCuPmePerfCRCanomalies, 1293 -- efmCuPmePerfLOSWS, 1294 -- efmCuPmePerfUAS, 1295 -- efmCuPmeDeviceFault, 1296 -- efmCuPmeLocalPowerLoss 1297 -- Another option would be to reference HDSL2-SHDSL-LINE-MIB 1298 -- or VDSL-LINE-EXT-MCM-MIB, reusing notifications defined there. 1300 efmCuPmeLineAtnCrossing NOTIFICATION-TYPE 1301 OBJECTS { 1302 efmCuPmeLineAtn, 1303 efmCuPmeThreshLineAtn 1304 } 1305 STATUS current 1306 DESCRIPTION 1307 "This notification indicates that the loop attenuation 1308 threshold (as per the efmCuPmeThreshLineAtn 1309 value) has been reached/exceeded for the 2Base-TL/10Pass-TS 1310 PME." 1311 -- EdNote: add throttling limitations here 1312 ::= { efmCuPmeNotifications 1 } 1314 efmCuPmeSnrMgnCrossing NOTIFICATION-TYPE 1315 OBJECTS { 1316 efmCuPmeSnrMgn, 1317 efmCuPmeThreshSnrMgn 1318 } 1319 STATUS current 1320 DESCRIPTION 1321 "This notification indicates that the SNR margin threshold 1322 (as per the efmCuPmeThreshSnrMgn value) has been 1323 reached/exceeded for the 2Base-TL/10Pass-TS PME." 1324 -- EdNote: add throttling limitations here 1325 ::= { efmCuPmeNotifications 2 } 1327 efmCuPmeDeviceFault NOTIFICATION-TYPE 1328 OBJECTS { 1329 efmCuPmeFltStatus 1330 } 1331 STATUS current 1332 DESCRIPTION 1333 "This notification indicates that a fault in the PME has been 1334 detected by a vendor specific diagnostic or a self-test." 1335 -- EdNote: add throttling limitations here 1336 ::= { efmCuPmeNotifications 3 } 1338 efmCuPmeConfigInitFailure NOTIFICATION-TYPE 1339 OBJECTS { 1340 efmCuPmeFltStatus, 1341 efmCuAdminProfile, 1342 efmCuPmeAdminProfile 1343 } 1344 STATUS current 1345 DESCRIPTION 1346 "This notification indicates that PME initialization has 1347 failed, due to inability of the PME link to achieve requested 1348 configuration profile." 1349 -- EdNote: add throttling limitations here 1350 ::= { efmCuPmeNotifications 4 } 1352 efmCuPmeProtocolInitFailure NOTIFICATION-TYPE 1353 OBJECTS { 1354 efmCuPmeFltStatus, 1355 efmCuPmeOperSubType 1356 } 1357 STATUS current 1358 DESCRIPTION 1359 "This notification indicates that peer PME was using 1360 incompatible protocol during initialization." 1361 -- EdNote: add throttling limitations here 1362 ::= { efmCuPmeNotifications 5 } 1364 -- The PME group 1366 efmCuPmeConfTable OBJECT-TYPE 1367 SYNTAX SEQUENCE OF EfmCuPmeConfEntry 1368 MAX-ACCESS not-accessible 1369 STATUS current 1370 DESCRIPTION 1371 "Table for Configuration of common aspects for EFMCu 1372 2BaseTL/10PassTS PME ports (modems). Configuration of aspects 1373 specific to 2BaseTL or 10PassTS PME types is represented in 1374 efmCuPme2BConfTable and efmCuPme10PConfTable respectively. 1376 Entries in this table MUST be maintained in a persistent 1377 manner." 1378 ::= { efmCuPme 1 } 1380 efmCuPmeConfEntry OBJECT-TYPE 1381 SYNTAX EfmCuPmeConfEntry 1382 MAX-ACCESS not-accessible 1383 STATUS current 1384 DESCRIPTION 1385 "An entry in the EFMCu PME Configuration table. 1386 Each entry represents common aspects of an EFMCu PME port 1387 indexed by the ifIndex. Note that an EFMCu PME port can be 1388 stacked below a single PCS port, also indexed by ifIndex, 1389 possibly together with other PME ports if PAF is enabled." 1390 INDEX { ifIndex } 1391 ::= { efmCuPmeConfTable 1 } 1393 EfmCuPmeConfEntry ::= 1394 SEQUENCE { 1395 efmCuPmeAdminSubType INTEGER, 1396 efmCuPmeAdminProfile ProfileIndex, 1397 efmCuPAFRemoteDiscoveryCode PhysAddress, 1398 efmCuPmeThreshLineAtn Integer32, 1399 efmCuPmeThreshSnrMgn Integer32, 1400 efmCuPmeLineAtnCrossingEnable TruthValue, 1401 efmCuPmeSnrMgnCrossingEnable TruthValue, 1402 efmCuPmeDeviceFaultEnable TruthValue, 1403 efmCuPmeConfigInitFailEnable TruthValue, 1404 efmCuPmeProtocolInitFailEnable TruthValue 1405 } 1407 efmCuPmeAdminSubType OBJECT-TYPE 1408 SYNTAX INTEGER { 1409 ieee2BaseTLO(1), 1410 ieee2BaseTLR(2), 1411 ieee10PassTSO(3), 1412 ieee10PassTSR(4), 1413 ieee2BaseTLor10PassTSR(5), 1414 ieee2BaseTLor10PassTSO(6), 1415 ieee10PassTSor2BaseTLO(7) 1416 } 1417 MAX-ACCESS read-write 1418 STATUS current 1419 DESCRIPTION 1420 "Administrative (desired) sub-type of the PME. 1421 Possible values are: 1422 ieee2BaseTLO - PME shall operate as 2BaseTL-O 1423 ieee2BaseTLR - PME shall operate as 2BaseTL-R 1424 ieee10PassTSO - PME shall operate as 10PassTS-O 1425 ieee10PassTSR - PME shall operate as 10PassTS-R 1426 ieee2BaseTLor10PassTSR - PME shall operate as 2BaseTL-R or 1427 10PassTS-R. Actual value will be 1428 set by -O link partner during 1429 initialization (handshake). 1430 ieee2BaseTLor10PassTSO - PME shall operate as 2BaseTL-O 1431 (preferred) or 10PassTS-O. Actual 1432 value will be set during 1433 initialization depending on -R 1434 link partner capability (i.e. if 1435 -R is incapable of the preferred 1436 2BaseTL mode, 10PassTS will be 1437 used). 1438 ieee10PassTSor2BaseTLO - PME shall operate as 10PassTS-O 1439 (preferred) or 2BaseTL-O. Actual 1440 value will be set during 1441 initialization depending on -R 1442 link partner capability (i.e. if 1443 -R is incapable of the preferred 1444 10PassTS mode, 2BaseTL will be 1445 used). 1447 Changing efmCuPmeAdminSubType is a traffic disruptive 1448 operation and as such SHALL be done when the link is Down. 1449 Attempts to change this object SHALL be ignored if the link 1450 is Up or Initializing. 1451 Attempts to change this object to an unsupported subtype 1452 (see efmCuPmeSubTypesSupported) SHALL be rejected. 1454 The current operational sub type is indicated by 1455 efmCuPmeOperSubType variable. 1457 If a Clause 45 MDIO Interface to the PMA/PMD is present, then 1458 this object combines values of the Port sub-type select 1459 bits and the PMA/PMD type selection bits in the 10P/2B 1460 PMA/PMD control register" 1461 REFERENCE 1462 "[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7" 1463 ::= { efmCuPmeConfEntry 1 } 1465 efmCuPmeAdminProfile OBJECT-TYPE 1466 SYNTAX ProfileIndex 1467 MAX-ACCESS read-write 1468 STATUS current 1469 DESCRIPTION 1470 "Desired PME configuration profile. This object is a pointer 1471 to an entry in either efmCuPme2BConfProfileTable or 1472 efmCuPme10PConfProfileTable, depending on the current 1473 operating SubType of the PME. The value of this object is the 1474 index of the referenced profile. 1475 Note that if PME is assigned to a PCS port and value of 1476 efmCuAdminProfile for that port is not an empty list, then the 1477 profile(s) referenced by efmCuAdminProfile takes precedence 1478 over the profile referenced by efmCuPmeAdminProfile, i.e. the 1479 PME SHALL be configured according to efmCuAdminProfile. 1481 This object is writable and readable for the CO subtype PMEs 1482 (2BaseTL-O or 10PassTS-O). It is unavailable for the CPE 1483 subtype (2BaseTL-R or 10PassTS-R). 1485 Note that current operational Profile value is available via 1486 efmCuPmeOperProfile object. 1488 Modification of this object must be performed when the link is 1489 Down. Attempts to change this object MUST be rejected, if the 1490 link is Up or Initializing. 1491 Attempts to set this object to a value that is not the 1492 value of the index for an active entry in the corresponding 1493 profile table, MUST be rejected." 1494 REFERENCE 1495 "[802.3ah] 30.11.2.1.6" 1496 ::= { efmCuPmeConfEntry 2 } 1498 efmCuPAFRemoteDiscoveryCode OBJECT-TYPE 1499 SYNTAX PhysAddress 1500 MAX-ACCESS read-write 1501 STATUS current 1502 DESCRIPTION 1503 "PAF Remote Discovery Code of the PME port at CO. 1504 A 6 Byte long Discovery Code of the peer PCS connected via 1505 the PME. 1506 Reading this object results in a Discovery Get operation. 1507 Writing a zero to this object results in a Discovery 1508 Clear_if_Same operation (the value of efmCuPAFDiscoveryCode 1509 at the peer PCS shall be the same as efmCuPAFDiscoveryCode of 1510 the local PCS associated with the PME for the operation to 1511 succeed). 1512 Writing a non-zero value to this object results in a 1513 Discovery Set_if_Clear operation. 1514 This object does not exist in CPE port subtypes. A zero length 1515 octet string SHALL be returned for CPE port subtypes and also 1516 when PAF aggregation is not enabled. 1518 Discovery MUST be performed when the link is Down. 1519 Attempts to change this object MUST be rejected with the error 1520 inconsistentValue, if the link is Up or Initializing. 1522 If a Clause 45 MDIO Interface to the PMA/PMD is present, then 1523 this object is a function of 10P/2B aggregation discovery 1524 control register, Discovery operation result bits in 10P/2B 1525 aggregation and discovery status register and 1526 10P/2B aggregation discovery code register" 1527 REFERENCE 1528 "[802.3ah] 61.2.2.8.4, 45.2.6.6-45.2.6.8" 1529 ::= { efmCuPmeConfEntry 3 } 1531 efmCuPmeThreshLineAtn OBJECT-TYPE 1532 SYNTAX Integer32(-127..128) 1533 UNITS "dB" 1534 MAX-ACCESS read-write 1535 STATUS current 1536 DESCRIPTION 1537 "Desired Line Attenuation Threshold for the 2B/10P PME. 1538 This object configures the line attenuation alarm threshold. 1539 When the current value of Line Attenuation reaches or 1540 exceeds this threshold, a efmCuPmeLineAtnCrossing 1541 notification MAY be generated, if enabled by 1542 efmCuPmeLineAtnCrossingEnable. 1544 This object is writable for the CO subtype PMEs (-O). 1545 It is read-only for the CPE subtype (-R). 1547 Changing of the Line Attenuation Threshold must be performed 1548 when the link is Down. Attempts to change this object MUST be 1549 rejected with the error inconsistentValue, if the link is Up 1550 or Initializing. 1552 If a Clause 45 MDIO Interface to the PME is present, then this 1553 object will map to the Loop attenuation threshold bits in 1554 the 2B PMD line quality thresholds register" 1555 REFERENCE 1556 "[802.3ah] 45.2.1.36" 1557 ::= { efmCuPmeConfEntry 4 } 1559 efmCuPmeThreshSnrMgn OBJECT-TYPE 1560 SYNTAX Integer32(-127..128) 1561 UNITS "dB" 1562 MAX-ACCESS read-write 1563 STATUS current 1564 DESCRIPTION 1565 "Desired SNR Margin Threshold for the 2B/10P PME. 1566 This object configures the SNR margin alarm threshold. 1567 When the current value of SNR Margin reaches 1568 or exceeds this threshold, a efmCuPmeSnrMgnCrossing 1569 notification MAY be generated, if enabled by 1570 efmCuPmeSnrMgnCrossingEnable. 1572 This object is writable for the CO subtype PMEs 1573 (2BaseTL-O/10PassTS-R). It is read-only for the CPE subtype 1574 (2BaseTL-R/10PassTS-R). 1576 Changing of the SNR Margin Threshold must be performed when 1577 the link is Down. Attempts to change this object MUST be 1578 rejected with the error inconsistentValue, if the link is Up 1579 or Initializing. 1581 If a Clause 45 MDIO Interface to the PME is present, then this 1582 object will map to the SNR margin threshold bits in the 1583 2B PMD line quality thresholds register" 1584 REFERENCE 1585 "[802.3ah] 45.2.1.36" 1586 ::= { efmCuPmeConfEntry 5 } 1588 efmCuPmeLineAtnCrossingEnable OBJECT-TYPE 1589 SYNTAX TruthValue 1590 MAX-ACCESS read-write 1591 STATUS current 1592 DESCRIPTION 1593 "Indicates whether efmCuPmeLineAtnCrossing notifications 1594 should be generated for this interface. 1596 Value of truth(1) indicates that efmCuPmeLineAtnCrossing 1597 notification is enabled. Value of false(0) indicates the it is 1598 disabled." 1599 ::= { efmCuPmeConfEntry 6 } 1601 efmCuPmeSnrMgnCrossingEnable OBJECT-TYPE 1602 SYNTAX TruthValue 1603 MAX-ACCESS read-write 1604 STATUS current 1605 DESCRIPTION 1606 "Indicates whether efmCuPmeSnrMgnCrossing notifications 1607 should be generated for this interface. 1609 Value of truth(1) indicates that efmCuPmeSnrMgnCrossing 1610 notification is enabled. Value of false(0) indicates the it is 1611 disabled." 1612 ::= { efmCuPmeConfEntry 7 } 1614 efmCuPmeDeviceFaultEnable OBJECT-TYPE 1615 SYNTAX TruthValue 1616 MAX-ACCESS read-write 1617 STATUS current 1618 DESCRIPTION 1619 "Indicates whether efmCuPmeDeviceFault notifications 1620 should be generated for this interface. 1622 Value of truth(1) indicates that efmCuPmeDeviceFault 1623 notification is enabled. Value of false(0) indicates the it is 1624 disabled." 1625 ::= { efmCuPmeConfEntry 8 } 1627 efmCuPmeConfigInitFailEnable OBJECT-TYPE 1628 SYNTAX TruthValue 1629 MAX-ACCESS read-write 1630 STATUS current 1631 DESCRIPTION 1632 "Indicates whether efmCuPmeConfigInitFailure notifications 1633 should be generated for this interface. 1635 Value of truth(1) indicates that efmCuPmeConfigInitFailure 1636 notification is enabled. Value of false(0) indicates the it is 1637 disabled." 1638 ::= { efmCuPmeConfEntry 9 } 1640 efmCuPmeProtocolInitFailEnable OBJECT-TYPE 1641 SYNTAX TruthValue 1642 MAX-ACCESS read-write 1643 STATUS current 1644 DESCRIPTION 1645 "Indicates whether efmCuPmeProtocolInitFailure notifications 1646 should be generated for this interface. 1648 Value of truth(1) indicates that efmCuPmeProtocolInitFailure 1649 notification is enabled. Value of false(0) indicates the it is 1650 disabled." 1651 ::= { efmCuPmeConfEntry 10 } 1653 efmCuPmeCapabilityTable OBJECT-TYPE 1654 SYNTAX SEQUENCE OF EfmCuPmeCapabilityEntry 1655 MAX-ACCESS not-accessible 1656 STATUS current 1657 DESCRIPTION 1658 "Table for Configuration of common aspects for EFMCu 1659 2BaseTL/10PassTS PME ports (modems). Configuration of aspects 1660 specific to 2BaseTL or 10PassTS PME types is represented in 1661 efmCuPme2BConfTable and efmCuPme10PConfTable respectively. 1663 Entries in this table MUST be maintained in a persistent 1664 manner." 1665 ::= { efmCuPme 2 } 1667 efmCuPmeCapabilityEntry OBJECT-TYPE 1668 SYNTAX EfmCuPmeCapabilityEntry 1669 MAX-ACCESS not-accessible 1670 STATUS current 1671 DESCRIPTION 1672 "An entry in the EFMCu PME Configuration table. 1673 Each entry represents common aspects of an EFMCu PME port 1674 indexed by the ifIndex. Note that an EFMCu PME port can be 1675 stacked below a single PCS port, also indexed by ifIndex, 1676 possibly together with other PME ports if PAF is enabled." 1677 INDEX { ifIndex } 1678 ::= { efmCuPmeCapabilityTable 1 } 1680 EfmCuPmeCapabilityEntry ::= 1681 SEQUENCE { 1682 efmCuPmeSubTypesSupported BITS 1683 } 1685 efmCuPmeSubTypesSupported OBJECT-TYPE 1686 SYNTAX BITS { 1687 ieee2BaseTLO(0), 1688 ieee2BaseTLR(1), 1689 ieee10PassTSO(2), 1690 ieee10PassTSR(3) 1691 } 1692 MAX-ACCESS read-only 1693 STATUS current 1694 DESCRIPTION 1695 "PME supported sub-types. This is a bitmap of possible 1696 sub-types. The various bit positions are: 1697 ieee2BaseTLO - PME is capable of operating as 2BaseTL-O 1698 ieee2BaseTLR - PME is capable of operating as 2BaseTL-R 1699 ieee10PassTSO - PME is capable of operating as 10PassTS-O 1700 ieee10PassTSR - PME is capable of operating as 10PassTS-R 1702 An actual mode of operation is determined by 1703 efmCuPmeAdminSubType. 1705 If a Clause 45 MDIO Interface to the PCS is present, then this 1706 object combines the 10PASS-TS capable and 2BASE-TL capable 1707 bits in the 10P/2B PMA/PMD speed ability register and the 1708 CO supported and CPE supported bits in the 10P/2B PMA/PMD 1709 status register" 1710 REFERENCE 1711 "[802.3ah] 61.1, 45.2.1.4.1, 45.2.1.4.2, 45.2.1.12.2, 1712 45.2.1.12.3" 1713 ::= { efmCuPmeCapabilityEntry 1 } 1715 efmCuPmeStatusTable OBJECT-TYPE 1716 SYNTAX SEQUENCE OF EfmCuPmeStatusEntry 1717 MAX-ACCESS not-accessible 1718 STATUS current 1719 DESCRIPTION 1720 "Table for Configuration of common aspects for EFMCu 1721 2BaseTL/10PassTS PME ports (modems). Configuration of aspects 1722 specific to 2BaseTL or 10PassTS PME types is represented in 1723 efmCuPme2BConfTable and efmCuPme10PConfTable respectively. 1725 Entries in this table MUST be maintained in a persistent 1726 manner." 1727 ::= { efmCuPme 3 } 1729 efmCuPmeStatusEntry OBJECT-TYPE 1730 SYNTAX EfmCuPmeStatusEntry 1731 MAX-ACCESS not-accessible 1732 STATUS current 1733 DESCRIPTION 1734 "An entry in the EFMCu PME Configuration table. 1735 Each entry represents common aspects of an EFMCu PME port 1736 indexed by the ifIndex. Note that an EFMCu PME port can be 1737 stacked below a single PCS port, also indexed by ifIndex, 1738 possibly together with other PME ports if PAF is enabled." 1739 INDEX { ifIndex } 1740 ::= { efmCuPmeStatusTable 1 } 1742 EfmCuPmeStatusEntry ::= 1743 SEQUENCE { 1744 efmCuPmeOperStatus INTEGER, 1745 efmCuPmeFltStatus BITS, 1746 efmCuPmeOperSubType INTEGER, 1747 efmCuPmeOperProfile ProfileIndexOrZero, 1748 efmCuPmeSnrMgn Integer32, 1749 efmCuPmePeerSnrMgn Integer32, 1750 efmCuPmeLineAtn Integer32, 1751 efmCuPmePeerLineAtn Integer32, 1752 efmCuPmeTCCodingErrors Counter32 1753 } 1755 efmCuPmeOperStatus OBJECT-TYPE 1756 SYNTAX INTEGER { 1757 up(1), -- link is Up 1758 downNotReady(2), -- link is Down and not Ready 1759 downReady(3), -- link is Down and Ready 1760 init(4) -- link is Initializing 1761 } 1762 MAX-ACCESS read-only 1763 STATUS current 1764 DESCRIPTION 1765 "Current PME link Operational Status. Possible values are: 1766 up(1) - link is Up and ready to pass 64/65B 1767 encoded frames or fragments. 1768 downNotReady(2) - link is Down and the PME does not detect 1769 Handshake tones from its peer. This value 1770 may indicate a possible problem with 1771 the peer PME. 1772 downReady(3) - link is Down and the PME detects Handshake 1773 tones from its peer. 1774 init(4) - link is initializing, as a result of 1775 ifAdminStatus being set to 'up' for a 1776 particular PME or a PCS the PME is 1777 connected to. 1779 This object is intended to supplement Down state of 1780 ifOperStatus. 1782 This object partially maps to the Clause 30 attribute 1783 aPMEStatus. 1785 If a Clause 45 MDIO Interface to the PME is present, then this 1786 object partially maps to PMA/PMD link status bits in 10P/2B 1787 PMA/PMD status register." 1788 REFERENCE 1789 "[802.3ah] 30.11.2.1.3, 45.2.1.12.4" 1790 ::= { efmCuPmeStatusEntry 1 } 1792 efmCuPmeFltStatus OBJECT-TYPE 1793 SYNTAX BITS { 1794 lossOfFraming(0), -- Loss of Framing 1795 snrMgnDefect(1), -- SNR Margin dropped below Threshold 1796 lineAtnDefect(2), -- Line Attenuation exceeds Threshold 1797 deviceFault(3), -- Vendor-dependent diag or self-test 1798 -- fault 1799 configInitFailure(4), -- Configuration Init. failure 1800 protocolInitFailure(5) -- Protocol Initialization failure 1801 } 1802 MAX-ACCESS read-only 1803 STATUS current 1804 DESCRIPTION 1805 "Current PME link Fault Status. This is a bitmap of possible 1806 conditions. The various bit positions are: 1808 lossOfFraming - Loss of Framing for 10P or 1809 Loss of Sync word for 2B PMD or 1810 Loss of 64/65B Framing 1811 snrMgnDefect - SNR Margin dropped below the Threshold 1812 lineAtnDefect - Line Attenuation exceeds the Threshold 1813 deviceFault - Indicates a vendor-dependent 1814 diagnostic or self-test fault 1815 has been detected. 1816 configInitFailure - Configuration initialization failure, 1817 due to inability of the PME link to 1818 support configuration profile, 1819 requested during initialization. 1820 protocolInitFailure - Protocol initialization failure, 1821 due to incompatible protocol used by 1822 the Peer PME during init (that could 1823 happen if a peer PMD is G.SDHSL/VDSL 1824 modem for 2BaseTL/10PassTS PME 1825 respectively). 1827 This object is intended to supplement ifOperStatus in IF-MIB. 1829 This object partially maps to the Clause 30 attribute 1830 aPMEStatus. 1832 If a Clause 45 MDIO Interface to the PME is present, then this 1833 object consolidates information from various PMA/PMD 1834 registers, namely: Fault bit in PMA/PMD status 1 register, 1835 10P/2B PMA/PMD link loss register, 1836 10P outgoing indicator bits status register, 1837 10P incoming indicator bits status register, 1838 2B state defects register." 1839 REFERENCE 1840 "[802.3ah] 30.11.2.1.3, 45.2.1.2.1, 45.2.1.38, 1841 45.2.1.39, 45.2.1.54" 1842 ::= { efmCuPmeStatusEntry 2 } 1844 efmCuPmeOperSubType OBJECT-TYPE 1845 SYNTAX INTEGER { 1846 ieee2BaseTLO(1), 1847 ieee2BaseTLR(2), 1848 ieee10PassTSO(3), 1849 ieee10PassTSR(4) 1850 } 1851 MAX-ACCESS read-only 1852 STATUS current 1853 DESCRIPTION 1854 "Current operational sub-type of the PME. 1855 Possible values are: 1856 ieee2BaseTLO - PME operates as 2BaseTL-O 1857 ieee2BaseTLR - PME operates as 2BaseTL-R 1858 ieee10PassTSO - PME operates as 10PassTS-O 1859 ieee10PassTSR - PME operates as 10PassTS-R 1861 The operational sub type of the PME can be configured via 1862 efmCuPmeAdminSubType variable. 1864 If a Clause 45 MDIO Interface to the PMA/PMD is present, then 1865 this object combines values of the Port sub-type select 1866 bits, the PMA/PMD type selection bits in the 10P/2B 1867 PMA/PMD control register and the PMA/PMD link status bits in 1868 the 10P/2B PMA/PMD status register." 1869 REFERENCE 1870 "[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7, 45.2.1.12.4" 1871 ::= { efmCuPmeStatusEntry 3 } 1873 efmCuPmeOperProfile OBJECT-TYPE 1874 SYNTAX ProfileIndexOrZero 1875 MAX-ACCESS read-only 1876 STATUS current 1877 DESCRIPTION 1878 "PME current operating Profile. This object is a pointers to 1879 an entry in either efmCuPme2BConfProfileTable or 1880 efmCuPme10PConfProfileTable, depending on the current 1881 operating SubType of the PME as indicated by 1882 efmCuPmeOperSubType. 1883 The value of zero indicates that PME is down or initializing. 1885 This object partially maps to the aOperatingProfile 1886 attribute in Clause 30." 1887 REFERENCE 1888 "[802.3ah] 30.11.2.1.7" 1889 ::= { efmCuPmeStatusEntry 4 } 1891 efmCuPmeSnrMgn OBJECT-TYPE 1892 SYNTAX Integer32(-127..128) 1893 UNITS "dB" 1894 MAX-ACCESS read-only 1895 STATUS current 1896 DESCRIPTION 1897 "The current Signal-to-Noise Ratio (SNR) margin with respect 1898 to the received signal as perceived by the local PME. 1900 This object maps to the aPMESNRMgn attribute in Clause 30. 1902 If a Clause 45 MDIO Interface is present, then this 1903 object maps to the 10P/2B RX SNR margin register." 1904 REFERENCE 1905 "[802.3ah] 30.11.2.1.4, 45.2.1.16" 1906 ::= { efmCuPmeStatusEntry 5 } 1908 efmCuPmePeerSnrMgn OBJECT-TYPE 1909 SYNTAX Integer32(-127..128) 1910 UNITS "dB" 1911 MAX-ACCESS read-only 1912 STATUS current 1913 DESCRIPTION 1914 "The current SNR margin in dB with respect to the received 1915 signal, as perceived by the remote (link partner) PME. 1917 This object is not supported by -R PME subtypes. 1919 If a Clause 45 MDIO Interface is present, then this 1920 object maps to the 10P/2B link partner RX SNR margin 1921 register." 1922 REFERENCE 1923 "[802.3ah] 45.2.1.17" 1924 ::= { efmCuPmeStatusEntry 6} 1926 efmCuPmeLineAtn OBJECT-TYPE 1927 SYNTAX Integer32(-127..128) 1928 UNITS "dB" 1929 MAX-ACCESS read-only 1930 STATUS current 1931 DESCRIPTION 1932 "The current Line Attenuation in dB as perceived by the local 1933 PME. 1935 If a Clause 45 MDIO Interface is present, then this 1936 object maps to the Line Attenuation register" 1937 REFERENCE 1938 "[802.3ah] 45.2.1.18" 1939 ::= { efmCuPmeStatusEntry 7 } 1941 efmCuPmePeerLineAtn OBJECT-TYPE 1942 SYNTAX Integer32(-127..128) 1943 UNITS "dB" 1944 MAX-ACCESS read-only 1945 STATUS current 1946 DESCRIPTION 1947 "The current Line Attenuation in dB as perceived by the remote 1948 (link partner) PME. 1950 This object is not supported by CPE port subtypes. 1952 If a Clause 45 MDIO Interface is present, then this 1953 object maps to the 20P/2B link partner Line Attenuation 1954 register." 1955 REFERENCE 1956 "[802.3ah] 45.2.1.19" 1957 ::= { efmCuPmeStatusEntry 8 } 1959 efmCuPmeTCCodingErrors OBJECT-TYPE 1960 SYNTAX Counter32 1961 MAX-ACCESS read-only 1962 STATUS current 1963 DESCRIPTION 1964 "A number of 64/65-octet encapsulation errors. This counter is 1965 incremented for each 64/65-octet encapsulation error detected 1966 by the 64/65-octet receive function. 1968 If a Clause 45 MDIO Interface to the PME TC is present, then 1969 this object maps to the TC coding violations register 1970 (see 45.2.6.12)." 1971 REFERENCE 1972 "[802.3ah] 61.3.3.1, 45.2.6.12" 1973 ::= { efmCuPmeStatusEntry 9 } 1975 -- 2BaseTL specific PME group 1977 efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 } 1979 efmCuPme2BConfProfileTable OBJECT-TYPE 1980 SYNTAX SEQUENCE OF EfmCuPme2BConfProfileEntry 1981 MAX-ACCESS not-accessible 1982 STATUS current 1983 DESCRIPTION 1984 "This table supports definitions of configuration profiles for 1985 2BaseTL PMEs. 1986 First 12 entries in this table SHALL always be defined as 1987 follows (see 802.3ah Annex 63A): 1988 -------+------+-----+--------+------------------ 1989 Profile Rate Power Region Constellation 1990 index (Kbps) (dBm) (G.991.2) 1991 -------+------+-----+--------+------------------ 1992 1 5696 13.5 Annex A 32-TCPAM 1993 2 3072 13.5 Annex A 32-TCPAM 1994 3 2048 13.5 Annex A 16-TCPAM 1995 4 1024 13.5 Annex A 16-TCPAM 1996 5 704 13.5 Annex A 16-TCPAM 1997 6 512 13.5 Annex A 16-TCPAM 1998 7 5696 14.5 Annex B 32-TCPAM 1999 8 3072 14.5 Annex B 32-TCPAM 2000 9 2048 14.5 Annex B 16-TCPAM 2001 10 1024 13.5 Annex B 16-TCPAM 2002 11 704 13.5 Annex B 16-TCPAM 2003 12 512 13.5 Annex B 16-TCPAM 2005 These default entries SHALL be created by default and MUST 2006 not be deleted. 2008 Entries following the first 12, can be dynamically created and 2009 deleted, to provide custom profiles. 2011 This table MUST be maintained in a persistent manner." 2012 REFERENCE 2013 "[802.3ah] Annex 63A, 30.11.2.1.6" 2014 ::= { efmCuPme2B 2 } 2016 efmCuPme2BConfProfileEntry OBJECT-TYPE 2017 SYNTAX EfmCuPme2BConfProfileEntry 2018 MAX-ACCESS not-accessible 2019 STATUS current 2020 DESCRIPTION 2021 "Each entry corresponds to a single 2BaseTL PME configuration 2022 profile. Each profile contains a set of configuration 2023 parameters, which are applied to all 2BaseTL-O PMEs 2024 assigned to the 2BaseTL (PCS) port, referencing that profile 2025 via efmCuAdminProfile object or, if efmCuAdminProfile is zero, 2026 all 2BaseTL-O PMEs, referencing that profile via 2027 efmCuPmeAdminProfile. 2029 Profiles may be created/deleted using the row creation/ 2030 deletion mechanism via efmCuPme2BProfileRowStatus. If an 2031 active entry is referenced, the entry MUST remain 'active' 2032 until all references are removed. 2033 Default entries (first 12) MUST not be removed." 2034 INDEX { efmCuPme2BProfileIndex } 2035 ::= { efmCuPme2BConfProfileTable 1 } 2037 EfmCuPme2BConfProfileEntry ::= 2038 SEQUENCE { 2039 efmCuPme2BProfileIndex ProfileIndex, 2040 efmCuPme2BProfileDescr SnmpAdminString, 2041 efmCuPme2BRegion INTEGER, 2042 efmCuPme2BDataRate Unsigned32, 2043 efmCuPme2BPower Unsigned32, 2044 efmCuPme2BConstellation INTEGER, 2045 efmCuPme2BProfileRowStatus RowStatus 2046 } 2048 efmCuPme2BProfileIndex OBJECT-TYPE 2049 SYNTAX ProfileIndex 2050 MAX-ACCESS not-accessible 2051 STATUS current 2052 DESCRIPTION 2053 "2BaseTL PME Profile index. 2054 This object is the unique index associated with this profile. 2055 Entries in this table are referenced via efmCuAdminProfile 2056 or efmCuPmeAdminProfile objects." 2057 ::= { efmCuPme2BConfProfileEntry 1 } 2059 efmCuPme2BProfileDescr OBJECT-TYPE 2060 SYNTAX SnmpAdminString (SIZE(0..255)) 2061 MAX-ACCESS read-create 2062 STATUS current 2063 DESCRIPTION 2064 "A textual string containing information about 2BaseTL PME 2065 Profile. The string MAY include information about data rate 2066 and spectral limitations of this particular profile." 2067 ::= { efmCuPme2BConfProfileEntry 2 } 2069 efmCuPme2BRegion OBJECT-TYPE 2070 SYNTAX INTEGER { 2071 regionA(1), -- Annex A 2072 regionB(2), -- Annex B 2073 regionC(3) -- Annex C 2074 } 2075 MAX-ACCESS read-create 2076 STATUS current 2077 DESCRIPTION 2078 "Desired Power Spectral Density (PSD) Regional setting as 2079 specified in Regional Annex of [ITU-T G.991.2] to operate 2080 under. 2082 Possible values for this object are: 2083 regionA -- Annex A 2084 regionB -- Annex B 2085 regionC -- Annex C 2087 Changing Regional Annex must be performed when the link is 2088 Down. Attempts to change this object MUST be rejected with 2089 the error inconsistentValue, if the link is Up or 2090 Initializing. 2092 If a Clause 45 MDIO Interface to the PME is present, then this 2093 object maps to the Region bits in the 2B general 2094 parameter register." 2095 REFERENCE 2096 "[802.3ah] 45.2.1.42" 2097 ::= { efmCuPme2BConfProfileEntry 3 } 2099 efmCuPme2BDataRate OBJECT-TYPE 2100 SYNTAX Unsigned32(0..5696) 2101 UNITS "Kbps" 2102 MAX-ACCESS read-create 2103 STATUS current 2104 DESCRIPTION 2105 "Desired 2BaseTL PME Data Rate. 2106 The rate is fixed when the value of this object is n x 64Kbps, 2107 where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM. 2108 The value of 0 means that data rate is not fixed but is 2109 adaptive and should be set to the maximum attainable rate 2110 during line probing. 2112 If a Clause 45 MDIO Interface to the PME is present, then this 2113 object maps to the Min/Max Data Rate1 bits in the 2B PMD 2114 parameters register." 2115 REFERENCE 2116 "[802.3ah] 45.2.1.43" 2117 ::= { efmCuPme2BConfProfileEntry 4 } 2119 efmCuPme2BPower OBJECT-TYPE 2120 SYNTAX Unsigned32(10..42) 2121 UNITS "0.5 dBm" 2122 MAX-ACCESS read-create 2123 STATUS current 2124 DESCRIPTION 2125 "Desired Signal Transmit Power. Multiple of 0.5dBm. 2127 Changing of the Signal Transmit Power must be performed when 2128 the link is Down. Attempts to change this object MUST be 2129 rejected with the error inconsistentValue, if the link is Up 2130 or Initializing. 2132 If a Clause 45 MDIO Interface to the PME is present, then this 2133 object will map to the Power1 bits in the 2B PMD 2134 parameters register" 2135 REFERENCE 2136 "[802.3ah] 45.2.1.43" 2137 ::= { efmCuPme2BConfProfileEntry 5 } 2139 efmCuPme2BConstellation OBJECT-TYPE 2140 SYNTAX INTEGER { 2141 tcpam16(1), -- 16-TCPAM 2142 tcpam32(2) -- 32-TCPAM 2143 } 2144 MAX-ACCESS read-create 2145 STATUS current 2146 DESCRIPTION 2147 "Desired TCPAM Constellation of the 2BaseTL PME. The possible 2148 values are: 2149 tcpam16(1) - 16-TCPAM 2150 tcpam32(2) - 32-TCPAM 2152 If a Clause 45 MDIO Interface to the PME is present, then this 2153 object map to the Constellation1 bits in the 2B general 2154 parameter register." 2155 REFERENCE 2156 "[802.3ah] 45.2.1.43" 2157 ::= { efmCuPme2BConfProfileEntry 6 } 2159 efmCuPme2BProfileRowStatus OBJECT-TYPE 2160 SYNTAX RowStatus 2161 MAX-ACCESS read-create 2162 STATUS current 2163 DESCRIPTION 2164 "This object controls creation/deletion of the associated 2165 entry in efmCuPme2BConfProfileTable per the semantics of 2166 RowStatus. 2167 If an 'active' entry is referenced via efmCuAdminProfile or 2168 efmCuPmeAdminProfile, the entry MUST remain 'active' until all 2169 references are removed." 2170 ::= { efmCuPme2BConfProfileEntry 7 } 2172 -- 10PassTS specific PME group 2174 efmCuPme10P OBJECT IDENTIFIER ::= { efmCuPme 6 } 2176 efmCuPme10PConfProfileTable OBJECT-TYPE 2177 SYNTAX SEQUENCE OF EfmCuPme10PConfProfileEntry 2178 MAX-ACCESS not-accessible 2179 STATUS current 2180 DESCRIPTION 2181 "This table supports definitions of configuration profiles for 2182 10PassTL PMEs. 2183 First 22 entries in this table SHALL always be defined as 2184 follows (see 802.3ah Annex 62B.3): 2185 -------+--------+----+---------+-----+------------ 2186 Profile Bandplan UPBO BandNotch DRate URate 2187 Index PSDMask# p# p# p# p# 2188 -------+--------+----+---------+-----+------------ 2189 1 1 3 2,6,10,11 20 20(default) 2190 2 13 5 0 20 20 2191 3 1 1 0 20 20 2192 4 16 0 0 100 100 2193 5 16 0 0 70 50 2194 6 6 0 0 50 10 2195 7 17 0 0 30 30 2196 8 8 0 0 30 5 2197 9 4 0 0 25 25 2198 10 4 0 0 15 15 2199 11 23 0 0 10 10 2200 12 23 0 0 5 5 2201 13 16 0 2,5,9,11 100 100 2202 14 16 0 2,5,9,11 70 50 2203 15 6 0 2,6,10,11 50 10 2204 16 17 0 2,5,9,11 30 30 2205 17 8 0 2,6,10,11 30 5 2206 18 4 0 2,6,10,11 25 25 2207 19 4 0 2,6,10,11 15 15 2208 20 23 0 2,5,9,11 10 10 2209 21 23 0 2,5,9,11 5 5 2210 22 30 0 0 200 50 2212 These default entries SHALL be created by default and MUST 2213 not be deleted. 2215 Entries following the first 22, can be dynamically created and 2216 deleted, to provide custom profiles. 2218 This table MUST be maintained in a persistent manner." 2219 REFERENCE 2220 "[802.3ah] Annex 62B.3, 30.11.2.1.6" 2221 ::= { efmCuPme10P 1 } 2223 efmCuPme10PConfProfileEntry OBJECT-TYPE 2224 SYNTAX EfmCuPme10PConfProfileEntry 2225 MAX-ACCESS not-accessible 2226 STATUS current 2227 DESCRIPTION 2228 "Each entry corresponds to a single 10PassTS PME configuration 2229 profile. Each profile contains a set of configuration 2230 parameters, which are applied to all PMEs assigned to the 2231 10PassTS (PCS) port, referencing that profile via 2232 efmCuAdminProfile object, or, if efmCuAdminProfile is zero, 2233 to all PMEs referencing that profile via efmCuPmeAdminProfile. 2234 Profiles may be created/deleted using the row creation/ 2235 deletion mechanism via efmCuPme10PProfileRowStatus. If an 2236 'active' entry is referenced, the entry MUST remain 'active' 2237 until all references are removed. 2238 Default entries (first 22) MUST not be removed." 2239 INDEX { efmCuPme10PProfileIndex } 2240 ::= { efmCuPme10PConfProfileTable 1 } 2242 EfmCuPme10PConfProfileEntry ::= 2243 SEQUENCE { 2244 efmCuPme10PProfileIndex ProfileIndex, 2245 efmCuPme10PProfileDescr SnmpAdminString, 2246 efmCuPme10PBandplanPSDMskProfile INTEGER, 2247 efmCuPme10PUPBOReferenceProfile INTEGER, 2248 efmCuPme10PBandNotchProfiles BITS, 2249 efmCuPme10PPayloadURateProfile INTEGER, 2250 efmCuPme10PPayloadDRateProfile INTEGER, 2251 efmCuPme10PProfileRowStatus RowStatus 2252 } 2254 efmCuPme10PProfileIndex OBJECT-TYPE 2255 SYNTAX ProfileIndex 2256 MAX-ACCESS not-accessible 2257 STATUS current 2258 DESCRIPTION 2259 "10PassTS PME Profile Index. 2260 This object is the unique index associated with this profile. 2261 Entries in this table are referenced via efmCuAdminProfile or 2262 efmCuPmeAdminProfile." 2263 ::= { efmCuPme10PConfProfileEntry 1 } 2265 efmCuPme10PProfileDescr OBJECT-TYPE 2266 SYNTAX SnmpAdminString (SIZE(0..255)) 2267 MAX-ACCESS read-create 2268 STATUS current 2269 DESCRIPTION 2270 "A textual string containing information about 10PassTS PME 2271 Profile. The string MAY include information about data rate 2272 and spectral limitations of this particular profile." 2273 ::= { efmCuPme10PConfProfileEntry 2 } 2275 efmCuPme10PBandplanPSDMskProfile OBJECT-TYPE 2276 SYNTAX INTEGER {-- PSD Mask Bands Bandplan 2277 profile1(1), -- T1.424/T-U P1 FTTCab.M1 x/D/U/D/U A 2278 profile2(2), -- T1.424/T-U P1 FTTEx.M1 2279 profile3(3), -- T1.424/T-U P1 FTTCab.M2 2280 profile4(4), -- T1.424/T-U P1 FTTEx.M2 2281 profile5(5), -- T1.424/T-U P1 FTTCab.M1 D/D/U/D/U 2282 profile6(6), -- T1.424/T-U P1 FTTEx.M1 2283 profile7(7), -- T1.424/T-U P1 FTTCab.M2 2284 profile8(8), -- T1.424/T-U P1 FTTEx.M2 2285 profile9(9), -- T1.424/T-U P1 FTTCab.M1 U/D/U/D/x 2286 profile10(10), -- T1.424/T-U P1 FTTEx.M1 2287 profile11(11), -- T1.424/T-U P1 FTTCab.M2 2288 profile12(12), -- T1.424/T-U P1 FTTEx.M2 2289 profile13(13), -- TS1 101 270-1 Pcab.M1.A x/D/U/D/U B 2290 profile14(14), -- TS1 101 270-1 Pcab.M1.B 2291 profile15(15), -- TS1 101 270-1 Pex.P1.M1 2292 profile16(16), -- TS1 101 270-1 Pex.P2.M1 2293 profile17(17), -- TS1 101 270-1 Pcab.M2 2294 profile18(18), -- TS1 101 270-1 Pex.P1.M2 2295 profile19(19), -- TS1 101 270-1 Pex.P2.M2 2296 profile20(20), -- TS1 101 270-1 Pcab.M1.A U/D/U/D/x 2297 profile21(21), -- TS1 101 270-1 Pcab.M1.B 2298 profile22(22), -- TS1 101 270-1 Pex.P1.M1 2299 profile23(23), -- TS1 101 270-1 Pex.P2.M1 2300 profile24(24), -- TS1 101 270-1 Pcab.M2 2301 profile25(25), -- TS1 101 270-1 Pex.P1.M2 2302 profile26(26), -- TS1 101 270-1 Pex.P2.M2 2303 profile27(27), -- G.993.1 F.1.2.1 (VDSLoPOTS) x/D/U/D/U F 2304 profile28(28), -- G.993.1 F.1.2.2 (VDSLoTCM-ISDN) 2305 profile29(29) -- G.993.1 F.1.2.3 (PSD reduction) 2306 } 2307 MAX-ACCESS read-create 2308 STATUS current 2309 DESCRIPTION 2310 "10PassTS PME Bandplan and PSD Mask profile, 2311 as specified in 802.3ah Annex 62A. Possible values are: 2312 --------------+------------------------+-----------+--------- 2313 Profile Name PSD Mask Bands Bandplan 2314 --------------+------------------------+-----------+--------- 2315 profile1(1) - T1.424/T-U P1 FTTCab.M1 x/D/U/D/U A 2316 profile2(2) - T1.424/T-U P1 FTTEx.M1 2317 profile3(3) - T1.424/T-U P1 FTTCab.M2 2318 profile4(4) - T1.424/T-U P1 FTTEx.M2 2319 profile5(5) - T1.424/T-U P1 FTTCab.M1 D/D/U/D/U 2320 profile6(6) - T1.424/T-U P1 FTTEx.M1 2321 profile7(7) - T1.424/T-U P1 FTTCab.M2 2322 profile8(8) - T1.424/T-U P1 FTTEx.M2 2323 profile9(9) - T1.424/T-U P1 FTTCab.M1 U/D/U/D/x 2324 profile10(10) - T1.424/T-U P1 FTTEx.M1 2325 profile11(11) - T1.424/T-U P1 FTTCab.M2 2326 profile12(12) - T1.424/T-U P1 FTTEx.M2 2327 profile13(13) - TS1 101 270-1 Pcab.M1.A x/D/U/D/U B 2328 profile14(14) - TS1 101 270-1 Pcab.M1.B 2329 profile15(15) - TS1 101 270-1 Pex.P1.M1 2330 profile16(16) - TS1 101 270-1 Pex.P2.M1 2331 profile17(17) - TS1 101 270-1 Pcab.M2 2332 profile18(18) - TS1 101 270-1 Pex.P1.M2 2333 profile19(19) - TS1 101 270-1 Pex.P2.M2 2334 profile20(20) - TS1 101 270-1 Pcab.M1.A U/D/U/D/x 2335 profile21(21) - TS1 101 270-1 Pcab.M1.B 2336 profile22(22) - TS1 101 270-1 Pex.P1.M1 2337 profile23(23) - TS1 101 270-1 Pex.P2.M1 2338 profile24(24) - TS1 101 270-1 Pcab.M2 2339 profile25(25) - TS1 101 270-1 Pex.P1.M2 2340 profile26(26) - TS1 101 270-1 Pex.P2.M2 2341 profile27(27) - G.993.1 F.1.2.1 (VDSLoPOTS) x/D/U/D/U F 2342 profile28(28) - G.993.1 F.1.2.2 (VDSLoTCM-ISDN) 2343 profile29(29) - G.993.1 F.1.2.3 (PSD reduction) 2345 This object maps to the aBandplanPSDMaskProfile attribute 2346 in Clause 30." 2347 REFERENCE 2348 "[802.3ah] Annex 62A, 30.5.1.1.22" 2349 ::= { efmCuPme10PConfProfileEntry 3 } 2351 efmCuPme10PUPBOReferenceProfile OBJECT-TYPE 2352 SYNTAX INTEGER {-- Reference PSD 2353 profile1(1), -- T1.424/T-U Noise A M1 2354 profile2(2), -- T1.424/T-U Noise A M2 2355 profile3(3), -- T1.424/T-U Noise F M1 2356 profile4(4), -- T1.424/T-U Noise F M2 2357 profile5(5), -- ETSI TS 101 270-1 Noise A&B 2358 profile6(6), -- ETSI TS 101 270-1 Noise C 2359 profile7(7), -- ETSI TS 101 270-1 Noise D 2360 profile8(8), -- ETSI TS 101 270-1 Noise E 2361 profile9(9) -- ETSI TS 101 270-1 Noise F 2362 } 2363 MAX-ACCESS read-create 2364 STATUS current 2365 DESCRIPTION 2366 "10PassTS PME Upstream Power Back-Off (UPBO) Reference PSD 2367 Profile, as specified in 802.3ah Annex 62A. Possible values 2368 are: 2369 profile1(1) - T1.424/T-U Noise A M1 2370 profile2(2) - T1.424/T-U Noise A M2 2371 profile3(3) - T1.424/T-U Noise F M1 2372 profile4(4) - T1.424/T-U Noise F M2 2373 profile5(5) - ETSI TS 101 270-1 Noise A&B 2374 profile6(6) - ETSI TS 101 270-1 Noise C 2375 profile7(7) - ETSI TS 101 270-1 Noise D 2376 profile8(8) - ETSI TS 101 270-1 Noise E 2377 profile9(9) - ETSI TS 101 270-1 Noise F 2379 This object maps to the aUPBOReferenceProfile attribute 2380 in Clause 30." 2381 REFERENCE 2382 "[802.3ah] Annex 62A.3.4, 30.5.1.1.23" 2383 ::= { efmCuPme10PConfProfileEntry 4 } 2385 efmCuPme10PBandNotchProfiles OBJECT-TYPE 2386 SYNTAX BITS { -- G.991.3 T1.424/T-U TS101 270-1 StartF EndF 2387 -- Table Table Table (MHz) (MHz) 2388 profile0(0), -- no profile 2389 profile1(1), -- F-5 #01 - - 1.810 1.825 2390 profile2(2), -- 6-2 15-1 17 1.810 2.000 2391 profile3(3), -- F-5 #02 - - 1.907 1.912 2392 profile4(4), -- F-5 #03 - - 3.500 3.575 2393 profile5(5), -- 6-2 - 17 3.500 3.800 2394 profile6(6), -- - 15-1 - 3.500 4.000 2395 profile7(7), -- F-5 #04 - - 3.747 3.754 2396 profile8(8), -- F-5 #05 - - 3.791 3.805 2397 profile9(9), -- 6-2 - 17 7.000 7.100 2398 profile10(10),-- F-5 #06 15-1 - 7.000 7.300 2399 profile11(11) -- 6-2 15-1 1 10.100 10.150 2400 } 2401 MAX-ACCESS read-create 2402 STATUS current 2403 DESCRIPTION 2404 "10PassTS PME Egress Control Band Notch Profile bitmap, 2405 as specified in 802.3ah Annex 62A. Possible values are: 2406 --------------+---------+----------+-----------+------+----- 2407 Profile Name G.991.3 T1.424/T-U TS101 270-1 StartF EndF 2408 Table Table Table (MHz) (MHz) 2409 --------------+---------+----------+-----------+------+----- 2410 profile0(0) - no profile 2411 profile1(1) - F-5 #01 - - 1.810 1.825 2412 profile2(2) - 6-2 15-1 17 1.810 2.000 2413 profile3(3) - F-5 #02 - - 1.907 1.912 2414 profile4(4) - F-5 #03 - - 3.500 3.575 2415 profile5(5) - 6-2 - 17 3.500 3.800 2416 profile6(6) - - 15-1 - 3.500 4.000 2417 profile7(7) - F-5 #04 - - 3.747 3.754 2418 profile8(8) - F-5 #05 - - 3.791 3.805 2419 profile9(9) - 6-2 - 17 7.000 7.100 2420 profile10(10) - F-5 #06 15-1 - 7.000 7.300 2421 profile11(11) - 6-2 15-1 1 10.100 10.150 2423 Any combination of profiles can be specified by ORing 2424 individual profiles, for example value of 0x0622 selects 2425 profiles 2,6,10 and 11. 2427 This object maps to the aBandNotchProfile attribute 2428 in Clause 30." 2429 REFERENCE 2430 "[802.3ah] Annex 62A.3.5, 30.5.1.1.19" 2431 ::= { efmCuPme10PConfProfileEntry 5 } 2433 efmCuPme10PPayloadURateProfile OBJECT-TYPE 2434 SYNTAX INTEGER {-- Upstream Payload Rate (Mbps) 2435 profile5(5), -- 2.5 2436 profile10(10), -- 5 2437 profile15(15), -- 7.5 2438 profile20(20), -- 10 2439 profile25(25), -- 12.5 2440 profile30(30), -- 15 2441 profile50(50), -- 25 2442 profile70(70), -- 35 2443 profile100(100) -- 50 2444 } 2445 MAX-ACCESS read-create 2446 STATUS current 2447 DESCRIPTION 2448 "10PassTS PME Upstream Payload Rate Profile, 2449 as specified in 802.3ah Annex 62A. Possible values are: 2450 profile5(5) - 2.5 Mbps 2451 profile10(10) - 5 Mbps 2452 profile15(15) - 7.5 Mbps 2453 profile20(20) - 10 Mbps 2454 profile25(25) - 12.5 Mbps 2455 profile30(30) - 15 Mbps 2456 profile50(50) - 25 Mbps 2457 profile70(70) - 35 Mbps 2458 profile100(100) - 50 Mbps 2460 Each value represents a target for the PME's Upstream Payload 2461 Bitrate as seen at the MII. If the payload rate of the 2462 selected profile cannot be achieved based on the loop 2463 environment, bandplan and PSD mask, the PME initialization 2464 SHALL fail. 2466 This object maps to the aPayloadRateProfileUpstream 2467 attribute in Clause 30." 2468 REFERENCE 2469 "[802.3ah] Annex 62A.3.6, 30.5.1.1.20" 2470 ::= { efmCuPme10PConfProfileEntry 6 } 2472 efmCuPme10PPayloadDRateProfile OBJECT-TYPE 2473 SYNTAX INTEGER {-- Downstream Payload Rate (Mbps) 2474 profile5(5), -- 2.5 2475 profile10(10), -- 5 2476 profile15(15), -- 7.5 2477 profile20(20), -- 10 2478 profile25(25), -- 12.5 2479 profile30(30), -- 15 2480 profile50(50), -- 25 2481 profile70(70), -- 35 2482 profile100(100), -- 50 2483 profile140(140), -- 70 2484 profile200(200) -- 100 2485 } 2486 MAX-ACCESS read-create 2487 STATUS current 2488 DESCRIPTION 2489 "10PassTS PME Downstream Payload Rate Profile, 2490 as specified in 802.3ah Annex 62A. Possible values are: 2491 profile5(5) - 2.5 Mbps 2492 profile10(10) - 5 Mbps 2493 profile15(15) - 7.5 Mbps 2494 profile20(20) - 10 Mbps 2495 profile25(25) - 12.5 Mbps 2496 profile30(30) - 15 Mbps 2497 profile50(50) - 25 Mbps 2498 profile70(70) - 35 Mbps 2499 profile100(100) - 50 Mbps 2500 profile140(140) - 70 Mbps 2501 profile200(200) - 100 Mbps 2503 Each value represents a target for the PME's Downstream 2504 Payload Bitrate as seen at the MII. If the payload rate of 2505 the selected profile cannot be achieved based on the loop 2506 environment, bandplan and PSD mask, the PME initialization 2507 SHALL fail. 2509 This object maps to the aPayloadRateProfileDownstream 2510 attribute in Clause 30." 2511 REFERENCE 2512 "[802.3ah] Annex 62A.3.6, 30.5.1.1.21" 2513 ::= { efmCuPme10PConfProfileEntry 7 } 2515 efmCuPme10PProfileRowStatus OBJECT-TYPE 2516 SYNTAX RowStatus 2517 MAX-ACCESS read-create 2518 STATUS current 2519 DESCRIPTION 2520 "This object controls creation/deletion of the associated 2521 entry in efmCuPme10PConfProfileTable per the semantics of 2522 RowStatus. 2523 If an active entry is referenced via efmCuAdminProfile or 2524 efmCuPmeAdminProfile, the entry MUST remain 'active' until 2525 all references are removed." 2526 ::= { efmCuPme10PConfProfileEntry 8 } 2528 efmCuPme10PStatusTable OBJECT-TYPE 2529 SYNTAX SEQUENCE OF EfmCuPme10PStatusEntry 2530 MAX-ACCESS not-accessible 2531 STATUS current 2532 DESCRIPTION 2533 "Table reflecting status of EFMCu 10PassTS PMEs (modems)." 2534 ::= { efmCuPme10P 2 } 2536 efmCuPme10PStatusEntry OBJECT-TYPE 2537 SYNTAX EfmCuPme10PStatusEntry 2538 MAX-ACCESS not-accessible 2539 STATUS current 2540 DESCRIPTION 2541 "An entry in the EFMCu 10PassTS PME Status table." 2542 AUGMENTS { efmCuPmeStatusEntry } 2543 ::= { efmCuPme10PStatusTable 1 } 2545 EfmCuPme10PStatusEntry ::= 2546 SEQUENCE { 2547 efmCuPme10PElectricalLength Integer32, 2548 efmCuPme10PFECCorrectedBlocks Counter32, 2549 efmCuPme10PFECUncorrectedBlocks Counter32 2550 -- EdNote: To be continued 2551 } 2553 efmCuPme10PElectricalLength OBJECT-TYPE 2554 SYNTAX Integer32(0..8192|65535) 2555 UNITS "m" 2556 MAX-ACCESS read-only 2557 STATUS current 2558 DESCRIPTION 2559 "Electrical Length in meters as perceived by the 10PassTS PME 2560 after the link is established. 2561 The value of 65535 is returned if the link is Down or 2562 Initializing or the PME is unable to estimate the Electrical 2563 Length. 2565 If a Clause 45 MDIO Interface to the PME is present, then this 2566 object maps to the 10P Electrical Length register" 2567 REFERENCE 2568 "[802.3ah] 45.2.1.21" 2569 ::= { efmCuPme10PStatusEntry 1 } 2571 efmCuPme10PFECCorrectedBlocks OBJECT-TYPE 2572 SYNTAX Counter32 2573 MAX-ACCESS read-only 2574 STATUS current 2575 DESCRIPTION 2576 "A count of received and corrected FEC codewords in 10Pass-TS 2577 PME. 2579 This object maps to aPMEFECCorrectedBlocks attribute in 2580 clause 30. 2582 If a Clause 45 MDIO Interface to the PMA/PMD is present, 2583 then this object maps to the 10P FEC correctable errors 2584 register" 2585 REFERENCE 2586 "[802.3ah] 45.2.1.22" 2587 ::= { efmCuPme10PStatusEntry 2 } 2589 efmCuPme10PFECUncorrectedBlocks OBJECT-TYPE 2590 SYNTAX Counter32 2591 MAX-ACCESS read-only 2592 STATUS current 2593 DESCRIPTION 2594 "A count of received FEC codewords in 10Pass-TS PME, which are 2595 uncorrectable. 2597 This object maps to aPMEFECUncorrectableBlocks attribute in 2598 clause 30. 2600 If a Clause 45 MDIO Interface to the PMA/PMD is present, 2601 then this object maps to the 10P FEC uncorrectable errors 2602 register" 2603 REFERENCE 2604 "[802.3ah] 45.2.1.23" 2605 ::= { efmCuPme10PStatusEntry 3 } 2607 -- efmCuAvailableStackTable for use in Discovery 2609 efmCuAvailableStackTable OBJECT-TYPE 2610 SYNTAX SEQUENCE OF EfmCuAvailableStackEntry 2611 MAX-ACCESS not-accessible 2612 STATUS current 2613 DESCRIPTION 2614 "This table, modeled after ifStackTable from [IF-MIB], 2615 contains information on the possible 'on-top-of' 2616 relationships between the multiple sub-layers of network 2617 interfaces (as opposed to actual relationships in 2618 ifStackTable). In particular, it contains information on 2619 which PCS ports (sublayers) can possibly run 'on top of' 2620 which PMEs (sublayers), as determined by cross-connect 2621 capability of the EFMCu device, where each sub-layer 2622 corresponds to a conceptual row in the ifTable. For example, 2623 when the PCS port with ifIndex value x can be connected 2624 to run on top of the PME with ifIndex value y, then this table 2625 contains: 2627 efmCuAvailableStackStatus.x.y=capable 2629 Note that there's always at least on PCS for each PME and at 2630 least one PME for each PCS in the EFMCu devices, with 2631 efmCuPAFCapacity and efmCuPeerPAFCapacity indicating 2632 maximum number of PMEs which can be aggregated by local and 2633 remote PCS port respectively. 2634 This table is read only as it describes device capability" 2635 REFERENCE 2636 "ifStackTable of RFC 2863" 2637 ::= { efmCuObjects 3 } 2639 efmCuAvailableStackEntry OBJECT-TYPE 2640 SYNTAX EfmCuAvailableStackEntry 2641 MAX-ACCESS not-accessible 2642 STATUS current 2643 DESCRIPTION 2644 "Information on a particular relationship between two sub- 2645 layers, specifying that one sub-layer (PCS) runs on 'top' of 2646 the other sub-layer (PME). Each sub-layer corresponds to a 2647 conceptual row in the ifTable (interface index for PCS and 2648 PME respectively)." 2649 INDEX { 2650 efmCuAvailableStackHigherLayer, 2651 efmCuAvailableStackLowerLayer 2652 } 2653 ::= { efmCuAvailableStackTable 1 } 2655 EfmCuAvailableStackEntry ::= 2656 SEQUENCE { 2657 efmCuAvailableStackHigherLayer InterfaceIndex, 2658 efmCuAvailableStackLowerLayer InterfaceIndex, 2659 efmCuAvailableStackStatus INTEGER 2660 } 2662 efmCuAvailableStackHigherLayer OBJECT-TYPE 2663 SYNTAX InterfaceIndex 2664 MAX-ACCESS not-accessible 2665 STATUS current 2666 DESCRIPTION 2667 "The value of ifIndex corresponding to the higher sub-layer 2668 of the 'cross-connect capability' relationship, i.e., the 2669 PCS sub-layer which MAY run on 'top' of the PME sub-layer 2670 identified by the corresponding instance of 2671 efmCuAvailableStackLowerLayer." 2672 ::= { efmCuAvailableStackEntry 1 } 2674 efmCuAvailableStackLowerLayer OBJECT-TYPE 2675 SYNTAX InterfaceIndex 2676 MAX-ACCESS not-accessible 2677 STATUS current 2678 DESCRIPTION 2679 "The value of ifIndex corresponding to the lower sub-layer 2680 of the 'cross-connect capability' relationship, i.e., the 2681 PME sub-layer which MAY run 'below' the PCS sub-layer 2682 identified by the corresponding instance of 2683 efmCuAvailableStackHigherLayer." 2684 ::= { efmCuAvailableStackEntry 2 } 2686 efmCuAvailableStackStatus OBJECT-TYPE 2687 SYNTAX INTEGER { 2688 capable(1), 2689 outOfService(2) 2690 } 2691 MAX-ACCESS read-only 2692 STATUS current 2693 DESCRIPTION 2694 "The status of the 'cross-connect capability' relationship 2695 between two sub-layers. The following values are defined: 2696 capable(1) - the PME sub-layer interface, identified by 2697 the efmCuAvailableStackLowerLayer MAY be 2698 connected to run 'below' the PCS sub-layer 2699 interface, identified by the 2700 efmCuAvailableStackLowerLayer. 2701 outOfService(2) - the PME sub-layer interface cannot be 2702 connected due to unavailability of the 2703 interface. 2705 Note that PME availability per PCS, indicated by 'capable' 2706 value, can be constrained by other parameters, 2707 for example by aggregation capacity of a PCS or by the PME in 2708 question being already connected to another PCS. So, in 2709 order to ensure that a particular PME can be connected to the 2710 PCS, all respective parameters (e.g. efmCuAvailableStackTable, 2711 ifStackTable and efmCuPAFCapacity) SHALL be inspected. 2713 This object is read only, unlike ifStackStatus, as it 2714 describes the device capability." 2715 ::= { efmCuAvailableStackEntry 3 } 2717 -- 2718 -- Conformance Statements 2719 -- 2721 efmCuGroups OBJECT IDENTIFIER ::= { efmCuConformance 1 } 2723 efmCuCompliances OBJECT IDENTIFIER ::= { efmCuConformance 2 } 2725 -- Object Groups 2727 efmCuBasicGroup OBJECT-GROUP 2728 OBJECTS { 2729 efmCuPAFSupported, 2730 efmCuAdminProfile, 2731 efmCuTargetDataRate, 2732 efmCuTargetSnrMgn, 2733 efmCuPortSide, 2734 efmCuFltStatus 2735 } 2736 STATUS current 2737 DESCRIPTION 2738 "A collection of objects required for all of EFMCu ports." 2739 ::= { efmCuGroups 1 } 2741 efmCuPAFGroup OBJECT-GROUP 2742 OBJECTS { 2743 efmCuPeerPAFSupported, 2744 efmCuPAFCapacity, 2745 efmCuPeerPAFCapacity, 2746 efmCuPAFAdminState, 2747 efmCuPAFDiscoveryCode, 2748 efmCuPAFRemoteDiscoveryCode, 2749 efmCuNumPMEs, 2750 efmCuAvailableStackStatus 2751 } 2752 STATUS current 2753 DESCRIPTION 2754 "A collection of objects required for optional PME 2755 Aggregation Function (PAF) and PAF discovery in EFMCu ports." 2757 ::= { efmCuGroups 2 } 2759 efmCuPAFErrorsGroup OBJECT-GROUP 2760 OBJECTS { 2761 efmCuPAFInErrors, 2762 efmCuPAFInSmallFragments, 2763 efmCuPAFInLargeFragments, 2764 efmCuPAFInBadFragments, 2765 efmCuPAFInLostFragments, 2766 efmCuPAFInLostStarts, 2767 efmCuPAFInLostEnds, 2768 efmCuPAFInOverflows 2769 } 2770 STATUS current 2771 DESCRIPTION 2772 "A collection of objects supporting optional error counters 2773 of PAF on EFMCu ports." 2774 ::= { efmCuGroups 3 } 2776 efmCuPmeGroup OBJECT-GROUP 2777 OBJECTS { 2778 efmCuPmeAdminProfile, 2779 efmCuPmeOperStatus, 2780 efmCuPmeFltStatus, 2781 efmCuPmeSubTypesSupported, 2782 efmCuPmeAdminSubType, 2783 efmCuPmeOperSubType, 2784 efmCuPAFRemoteDiscoveryCode, 2785 efmCuPmeOperProfile, 2786 efmCuPmeSnrMgn, 2787 efmCuPmePeerSnrMgn, 2788 efmCuPmeLineAtn, 2789 efmCuPmePeerLineAtn, 2790 efmCuPmeTCCodingErrors, 2791 efmCuPmeThreshLineAtn, 2792 efmCuPmeThreshSnrMgn 2793 } 2794 STATUS current 2795 DESCRIPTION 2796 "A collection of objects providing information about 2797 a 2BaseTL/10PassTS PME." 2798 ::= { efmCuGroups 4 } 2800 efmCuAlarmConfGroup OBJECT-GROUP 2801 OBJECTS { 2802 efmCuThreshLowBandwidth, 2803 efmCuLowBandwidthEnable, 2804 efmCuPmeThreshLineAtn, 2805 efmCuPmeLineAtnCrossingEnable, 2806 efmCuPmeThreshSnrMgn, 2807 efmCuPmeSnrMgnCrossingEnable, 2808 efmCuPmeLineAtnCrossingEnable, 2809 efmCuPmeDeviceFaultEnable, 2810 efmCuPmeConfigInitFailEnable, 2811 efmCuPmeProtocolInitFailEnable 2812 -- efmCuPmeThreshES, 2813 -- efmCuPmethreshSES, 2814 -- efmCuPmeThreshCRCanomalies, 2815 -- efmCuPmeThreshLOSWS, 2816 -- efmCuPmeThreshUAS 2817 } 2818 STATUS current 2819 DESCRIPTION 2820 "A collection of objects required for configuration of alarm 2821 thresholds and notifications in EFMCu ports." 2822 ::= { efmCuGroups 5 } 2824 efmCuNotificationGroup NOTIFICATION-GROUP 2825 NOTIFICATIONS { 2826 efmCuLowBandwidth, 2827 efmCuPmeLineAtnCrossing, 2828 efmCuPmeSnrMgnCrossing, 2829 efmCuPmeDeviceFault, 2830 efmCuPmeConfigInitFailure, 2831 efmCuPmeProtocolInitFailure 2832 -- efmCuPmePerfES, 2833 -- efmCuPmePerfSES, 2834 -- efmCuPmePerfCRCanomalies, 2835 -- efmCuPmePerfLOSWS, 2836 -- efmCuPmePerfUAS, 2837 -- efmCuPmeDeviceFault, 2838 -- efmCuPmeLocalPowerLoss 2839 } 2840 STATUS current 2841 DESCRIPTION 2842 "This group supports notifications of significant conditions 2843 associated with EFMCu ports." 2844 ::= { efmCuGroups 6 } 2846 efmCuPme2BProfileGroup OBJECT-GROUP 2847 OBJECTS { 2848 efmCuPme2BProfileDescr, 2849 efmCuPme2BRegion, 2850 efmCuPme2BDataRate, 2851 efmCuPme2BPower, 2852 efmCuPme2BConstellation, 2853 efmCuPme2BProfileRowStatus 2854 } 2855 STATUS current 2856 DESCRIPTION 2857 "A collection of objects that constitute a configuration 2858 profile for configuration of 2BaseTL ports." 2859 ::= { efmCuGroups 7 } 2861 efmCuPme10PProfileGroup OBJECT-GROUP 2862 OBJECTS { 2863 efmCuPme10PProfileDescr, 2864 efmCuPme10PBandplanPSDMskProfile, 2865 efmCuPme10PUPBOReferenceProfile, 2866 efmCuPme10PBandNotchProfiles, 2867 efmCuPme10PPayloadURateProfile, 2868 efmCuPme10PPayloadDRateProfile, 2869 efmCuPme10PProfileRowStatus 2870 } 2871 STATUS current 2872 DESCRIPTION 2873 "A collection of objects that constitute a configuration 2874 profile for configuration of 10PassTS ports." 2875 ::= { efmCuGroups 8 } 2877 efmCuPme10PStatusGroup OBJECT-GROUP 2878 OBJECTS { 2879 efmCuPme10PElectricalLength, 2880 efmCuPme10PFECCorrectedBlocks, 2881 efmCuPme10PFECUncorrectedBlocks 2882 } 2883 STATUS current 2884 DESCRIPTION 2885 "A collection of objects providing status information 2886 specific to 10PassTS PMEs." 2887 ::= { efmCuGroups 9 } 2889 -- Compliance Statements 2891 efmCuCompliance MODULE-COMPLIANCE 2892 STATUS current 2893 DESCRIPTION 2894 "The compliance statement for 2BaseTL/10PassTS interfaces. 2895 Compliance with the following external compliance statements 2896 is prerequisite: 2898 MIB Module Compliance Statement 2899 ---------- -------------------- 2900 IF-MIB ifCompliance3 2901 IF-INVERTED-STACK-MIB ifInvCompliance 2902 EtherLike-MIB dot3Compliance2 2903 MAU-MIB mauModIfCompl3" 2905 MODULE -- this module 2906 MANDATORY-GROUPS { 2907 efmCuBasicGroup, 2908 efmCuPmeGroup, 2909 efmCuAlarmConfGroup, 2910 efmCuNotificationGroup 2911 } 2913 GROUP efmCuPme2BProfileGroup 2914 DESCRIPTION 2915 "Support for this group is only required for implementations 2916 supporting 2Base-TL Phy." 2918 GROUP efmCuPme10PProfileGroup 2919 DESCRIPTION 2920 "Support for this group is only required for implementations 2921 supporting 10Pass-TS Phy." 2923 GROUP efmCuPAFGroup 2924 DESCRIPTION 2925 "Support for this group is only required for implementations 2926 supporting PME Aggregation Function (PAF)." 2928 GROUP efmCuPAFErrorsGroup 2929 DESCRIPTION 2930 "Support for this group is optional for implementations 2931 supporting PME Aggregation Function (PAF)." 2933 GROUP efmCuPme10PStatusGroup 2934 DESCRIPTION 2935 "Support for this group is optional for implementations 2936 supporting 10Pass-TS Phy." 2938 OBJECT efmCuPmeSubTypesSupported 2939 SYNTAX BITS { 2940 ieee2BaseTLO(0), 2941 ieee2BaseTLR(1), 2942 ieee10PassTSO(2), 2943 ieee10PassTSR(3) 2944 } 2945 DESCRIPTION 2946 "Support for all subtypes is not required. However at least 2947 one value SHALL be supported" 2949 OBJECT efmCuPmeAdminSubType 2950 MIN-ACCESS read-only 2951 DESCRIPTION 2952 "Write access is not required (needed only for PMEs 2953 supporting more than a single subtype, e.g. 2954 ieee2BaseTLO and ieee2BaseTSR or ieee2BaseTLR and 2955 ieee10PassTSR)" 2957 OBJECT efmCuTargetSnrMgn 2958 MIN-ACCESS read-only 2959 DESCRIPTION 2960 "Write access is optional. For PHYs without write access 2961 the target SNR margin SHALL be fixed at 5dB for 2BaseTL 2962 and 6dB for 10PassTS." 2964 -- EdNote: To be Continued 2966 ::= { efmCuCompliances 1 } 2967 END 2969 6. Security Considerations 2971 There is a number of managed objects defined in this MIB module that 2972 have a MAX-ACCESS clause of read-write or read-create. Most objects 2973 are writeable only when the link is Down. Writing to these objects 2974 can have potentially disruptive effects on network operation, for 2975 example: 2977 o Changing of efmCuPmeAdminSubType MAY lead to a potential locking 2978 of the link, as peer PMEs of the same sub-type cannot exchange 2979 handshake messages. 2981 o Changing of efmCuPAFAdminState to enabled MAY lead to a potential 2982 locking of the link, if the peer Phy does not support PAF. 2984 o Changing of efmCuPAFDiscoveryCode, before the discovery operation, 2985 MAY lead to a wrongful discovery, with possile multiple -O ports 2986 connecting to the same -R (both -O ports have the same Discovery 2987 register value) and similar cases. 2989 o Changing PCS or PME configuration parameters (e.g. profile of a 2990 PCS or PME via efmCuAdminProfile or efmCuPmeAdminProfile) MAY lead 2991 to anything from link quality and rate degradation to a complete 2992 link initialization failure, as ability of an EFMCu port to 2993 support a particular configuration depends on the copper 2994 environment. 2996 o Activation of a PME can cause a severe degradation of service for 2997 another EFMCu Phy whose PME(s) MAY be affected by the cross-talk 2998 from the newly activated PME. 3000 o Removal of a PME from the operationally 'up' EFMCu port, 3001 aggregating several PMEs, MAY lead a link rate degradation 3003 The user of this MIB module must therefore be aware that support for 3004 SET operations in a non-secure environment without proper protection 3005 can have a negative effect on network operations. 3007 The readable objects in this MIB module (i.e., those with MAX-ACCESS 3008 other than not-accessible) may be considered sensitive in some 3009 environments since, collectively, they provide information about the 3010 performance of network interfaces and can reveal some aspects of 3011 their configuration. In particular since EFMCu can be carried over 3012 Unshielded Twisted Pair (UTP) voice grade copper in a bundle with 3013 other pairs belonging to another operator/customer, it is 3014 theoretically possible to evasdrop to an EFMCu transmission simply by 3015 "listening" to a cross-talk from an EFMCu pair, especially if the 3016 parameters of the EFMCu link in question are known. In such 3017 environments it is important to control even GET and NOTIFY access to 3018 these objects and possibly even to encrypt their values when sending 3019 them over the network via SNMP. 3021 SNMP versions prior to SNMPv3 did not include adequate security. 3022 Even if the network itself is secure (for example by using IPSec), 3023 even then, there is no control as to who on the secure network is 3024 allowed to access and GET/SET (read/change/create/delete) the objects 3025 in this MIB module. 3027 It is RECOMMENDED that implementers consider the security features as 3028 provided by the SNMPv3 framework (see [RFC3410], section 8), 3029 including full support for the SNMPv3 cryptographic mechanisms (for 3030 authentication and privacy). 3032 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3033 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3034 enable cryptographic security. It is then a customer/operator 3035 responsibility to ensure that the SNMP entity giving access to an 3036 instance of this MIB module is properly configured to give access to 3037 the objects only to those principals (users) that have legitimate 3038 rights to indeed GET or SET (change/create/delete) them. 3040 7. Acknowledgments 3042 Not yet. 3044 8. References 3046 8.1 Normative References 3048 [802.3ah] IEEE, "Draft amendment to - Information technology - 3049 Telecommunications and information exchange between 3050 systems - Local and metropolitan area networks - Specific 3051 requirements - Part 3: Carrier sense multiple access with 3052 collision detection (CSMA/CD) access method and physical 3053 layer specifications - Media Access Control Parameters, 3054 Physical Layers and Management Parameters for subscriber 3055 access networks", IEEE Draft P802.3ah/D3.3, April 2004. 3057 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3058 Requirement Levels", BCP 14, RFC 2119, March 1997. 3060 [RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart, 3061 "Introduction to Version 3 of the Internet-standard 3062 Network Management Framework", RFC 2570, April 1999. 3064 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3065 McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of 3066 Management Information Version 2 (SMIv2)", STD 58, RFC 3067 2578, April 1999. 3069 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3070 McCloghrie, K., Rose, M. and S. Waldbusser, "Textual 3071 Conventions for SMIv2", STD 58, RFC 2579, April 1999. 3073 [RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder, 3074 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3075 April 1999. 3077 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 3078 "Introduction and Applicability Statements for 3079 Internet-Standard Management Framework", RFC 3410, 3080 December 2002. 3082 8.2 Informative References 3084 [I-D.ietf-adslmib-gshdslbis] 3085 Sikes, C., Ray, B. and R. Abbi, "Definitions of Managed 3086 Objects for G.SHDSL.BIS Lines", 3087 draft-ietf-adslmib-gshdslbis-02 (work in progress), June 3088 2004. 3090 [I-D.ietf-adslmib-vdsl-ext-mcm] 3091 Dodge, M. and B. Ray, "Definitions of Managed Object 3092 Extensions for Very High Speed Digital Subscriber Lines 3093 (VDSL) Using Multiple Carrier Modulation (MCM) Line 3094 Coding", draft-ietf-adslmib-vdsl-ext-mcm-04 (work in 3095 progress), May 2004. 3097 [I-D.ietf-hubmib-efm-epon-mib] 3098 Khermosh, L., "Managed Objects for the Ethernet Passive 3099 Optical Networks", draft-ietf-hubmib-efm-epon-mib-01 (work 3100 in progress), April 2004. 3102 [I-D.ietf-hubmib-efm-mib] 3103 Squire, M., "Ethernet in the First Mile (EFM) Common MIB", 3104 draft-ietf-hubmib-efm-mib-01 (work in progress), June 3105 2004. 3107 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 3108 MIB", RFC 2863, June 2000. 3110 [RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table 3111 Extension to the Interfaces Group MIB", RFC 2864, June 3112 2000. 3114 [RFC3635] Flick, J., "Definitions of Managed Objects for the 3115 Ethernet-like Interface Types", RFC 3635, September 2003. 3117 [RFC3636] Flick, J., "Definitions of Managed Objects for IEEE 802.3 3118 Medium Attachment Units (MAUs)", RFC 3636, September 2003. 3120 Author's Address 3122 Edward Beili 3123 Actelis Networks 3124 Bazel 25 3125 Petach-Tikva 3126 Israel 3128 Phone: +972-3-924-3491 3129 EMail: edward.beili@actelis.com 3131 Intellectual Property Statement 3133 The IETF takes no position regarding the validity or scope of any 3134 Intellectual Property Rights or other rights that might be claimed to 3135 pertain to the implementation or use of the technology described in 3136 this document or the extent to which any license under such rights 3137 might or might not be available; nor does it represent that it has 3138 made any independent effort to identify any such rights. Information 3139 on the procedures with respect to rights in RFC documents can be 3140 found in BCP 78 and BCP 79. 3142 Copies of IPR disclosures made to the IETF Secretariat and any 3143 assurances of licenses to be made available, or the result of an 3144 attempt made to obtain a general license or permission for the use of 3145 such proprietary rights by implementers or users of this 3146 specification can be obtained from the IETF on-line IPR repository at 3147 http://www.ietf.org/ipr. 3149 The IETF invites any interested party to bring to its attention any 3150 copyrights, patents or patent applications, or other proprietary 3151 rights that may cover technology that may be required to implement 3152 this standard. Please address the information to the IETF at 3153 ietf-ipr@ietf.org. 3155 Disclaimer of Validity 3157 This document and the information contained herein are provided on an 3158 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 3159 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 3160 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 3161 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 3162 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3163 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 3165 Copyright Statement 3167 Copyright (C) The Internet Society (2004). This document is subject 3168 to the rights, licenses and restrictions contained in BCP 78, and 3169 except as set forth therein, the authors retain all their rights. 3171 Acknowledgment 3173 Funding for the RFC Editor function is currently provided by the 3174 Internet Society.