idnits 2.17.1 draft-ietf-hubmib-efm-cu-mib-06.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 3978, Section 5.1 on line 14. -- Found old boilerplate from RFC 3978, Section 5.5 on line 4097. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 4074. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 4081. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 4087. ** 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. 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 : ---------------------------------------------------------------------------- == There are 31 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. -- 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 (October 12, 2006) is 6403 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) == Unused Reference: 'I-D.ietf-hubmib-efm-mib' is defined on line 4017, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 3410 == Outdated reference: A later version (-06) exists of draft-ietf-hubmib-efm-epon-mib-05 == Outdated reference: A later version (-06) exists of draft-ietf-hubmib-efm-mib-04 Summary: 4 errors (**), 0 flaws (~~), 7 warnings (==), 7 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: April 15, 2007 October 12, 2006 6 Ethernet in the First Mile Copper (EFMCu) Interfaces MIB 7 draft-ietf-hubmib-efm-cu-mib-06.txt 9 Status of this Memo 11 By submitting this Internet-Draft, each author represents that any 12 applicable patent or other IPR claims of which he or she is aware 13 have been or will be disclosed, and any of which he or she becomes 14 aware will be disclosed, in accordance with Section 6 of BCP 79. 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 Internet- 19 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 April 15, 2007. 34 Copyright Notice 36 Copyright (C) The Internet Society (2006). 38 Abstract 40 This document defines Management Information Base (MIB) modules for 41 use with network management protocols in TCP/IP based internets. 42 This document proposes an extension to the Ethernet-like Interfaces 43 MIB and MAU MIB modules with a set of objects for managing Ethernet 44 in the First Mile Copper (EFMCu) interfaces 10PASS-TS and 2BASE-TL, 45 defined in IEEE Std 802.3ah-2004. In addition a set of objects is 46 defined, describing cross-connect capability of a managed device with 47 multi-layer (stacked) interfaces, extending the stack management 48 objects in the Interfaces Group MIB and the Inverted Stack Table MIB 49 modules. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. The Internet-Standard Management Framework . . . . . . . . . . 3 55 3. Relation to other MIB modules . . . . . . . . . . . . . . . . 4 56 3.1. Relation to Interfaces Group MIB module . . . . . . . . . 4 57 3.1.1. Layering Model . . . . . . . . . . . . . . . . . . . . 4 58 3.1.2. PME Aggregation Function (PAF) . . . . . . . . . . . . 6 59 3.1.3. Discovery Operation . . . . . . . . . . . . . . . . . 7 60 3.1.4. EFMCu ports initialization . . . . . . . . . . . . . . 9 61 3.1.5. Usage of ifTable . . . . . . . . . . . . . . . . . . . 9 62 3.2. Relation to SHDSL MIB module . . . . . . . . . . . . . . . 10 63 3.3. Relation to VDSL MIB module . . . . . . . . . . . . . . . 10 64 3.4. Relation to Ethernet-Like and MAU MIB modules . . . . . . 11 65 4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 12 66 4.1. EFM Copper MIB Overview . . . . . . . . . . . . . . . . . 12 67 4.2. Interface stack capability MIB Overview . . . . . . . . . 12 68 4.3. PME Profiles . . . . . . . . . . . . . . . . . . . . . . . 13 69 4.4. Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 13 70 5. Interface Stack Capability MIB Definitions . . . . . . . . . . 14 71 6. EFM Copper MIB Definitions . . . . . . . . . . . . . . . . . . 21 72 7. Security Considerations . . . . . . . . . . . . . . . . . . . 82 73 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 83 74 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 83 75 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 84 76 10.1. Normative References . . . . . . . . . . . . . . . . . . . 84 77 10.2. Informative References . . . . . . . . . . . . . . . . . . 85 78 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 87 79 Intellectual Property and Copyright Statements . . . . . . . . . . 88 81 1. Introduction 83 New Ethernet-like interfaces have been defined in the Institute of 84 Electrical and Electronics Engineers (IEEE) Standard 802.3ah-2004 85 [802.3ah], a.k.a. Ethernet in the First Mile (EFM), which is now a 86 part of the base IEEE Standard 802.3-2005 [802.3]. In particular 87 2BASE-TL and 10PASS-TS physical interfaces (PHYs), defined over 88 voice-grade copper pairs, have been specified for the long and short 89 reach respectively. These interfaces, collectively called EFMCu, are 90 based on ITU-T G.SHDSL [G.991.2] and VDSL [G.993.1] specifications 91 and support variable rates and optional Physical Medium Entity (PME) 92 aggregation (a.k.a. multi-pair bonding). 94 2BASE-TL PHY is capable of providing at least 2Mbps over 2700 m long 95 single copper pair with a mean Bit Error Rate (BER) of 10^-7 (using 96 5dB target noise margin). 98 10PASS-TS PHY is capable of providing at least 10Mbps over 750 m long 99 single copper pair with a mean BER of 10^-7 (using 6dB target noise 100 margin). 102 This memo defines a Management Information Base (MIB) module for use 103 with network management protocols in the Internet community to manage 104 EFMCu interfaces. In addition a MIB module is defined describing 105 cross-connect capability of a stacked interface. 107 Note that managed objects for Operation, Administration and 108 Management (OAM) and Ethernet over Passive Optical Networks (EPON) 109 clauses of IEEE 802.3ah are defined in EFM-COMMON-MIB [I-D.ietf- 110 hubmib-efm-mib] and EFM-EPON-MIB [I-D.ietf-hubmib-efm-epon-mib] 111 respectively. 113 2. The Internet-Standard Management Framework 115 For a detailed overview of the documents that describe the current 116 Internet-Standard Management Framework, please refer to section 7 of 117 RFC 3410 [RFC3410]. 119 Managed objects are accessed via a virtual information store, termed 120 the Management Information Base or MIB. MIB objects are generally 121 accessed through the Simple Network Management Protocol (SNMP). 122 Objects in the MIB are defined using the mechanisms defined in the 123 Structure of Management Information (SMI). This memo specifies a MIB 124 module that is compliant to the SMIv2, which is described in STD 58, 125 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 126 [RFC2580]. 128 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 129 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 130 document are to be interpreted as described in RFC 2119 [RFC2119]. 132 3. Relation to other MIB modules 134 This section outlines the relationship of the MIB modules defined in 135 this document with other MIB modules described in the relevant RFCs. 136 Specifically, Interfaces Group MIB (IF-MIB), Ethernet-Like 137 (EtherLike-MIB), MAU (MAU-MIB), SHDSL (HDSL2-SHDSL-LINE-MIB) and VDSL 138 (VDSL-LINE-EXT-MCM-MIB) are discussed. 140 3.1. Relation to Interfaces Group MIB module 142 2BASE-TL and 10PASS-TS PHY's specified in the EFM-CU-MIB module are 143 stacked (a.k.a. aggregated or bonded) Ethernet interfaces and as such 144 are managed using generic interface management objects defined in the 145 IF-MIB [RFC2863]. 147 The stack management, i.e. actual connection of the sub-layers to the 148 top layer interface, is done via the ifStackTable, as defined in the 149 IF-MIB [RFC2863] and its inverse ifInvStackTable, as defined in the 150 IF-INVERTED-STACK-MIB [RFC2864]. 152 The new tables ifCapStackTable and its inverse ifInvCapStackTable 153 defined in the IF-CAP-STACK-MIB module below, extend the stack 154 management with an ability to describe possible connections or cross- 155 connect capability, when a flexible cross-connect matrix is present 156 between the interface layers. 158 3.1.1. Layering Model 160 An EFMCu interface can aggregate up to 32 Physical Medium Entity 161 (PME) sub-layer devices (modems), using so called PME Aggregation 162 Function (PAF). 164 A generic EFMCu device can have a number of Physical Coding Sublayer 165 (PCS) ports, each connected to a MAC via Medium Independent Interface 166 (MII) at the upper layer, and cross-connected to a number of 167 underlying PMEs, with a single PCS per PME relationship, see clause 168 61.1 of [802.3ah] for more details. 170 Each PME in the aggregated EFMCu port is represented in the Interface 171 table (ifTable) as a separate port with ifType of shdsl(169) for 172 2BASE-TL or vdsl(97) for 10PASS-TS. The ifType values are defined in 173 [IANAifType-MIB]. 175 ifSpeed for each PME SHALL return the actual data bitrate of the 176 active PME (e.g. for 2BaseTL PMEs it is a multiple of 64Kbps). Zero 177 value SHALL be returned when PME is initializing or down. 179 The ifSpeed of the PCS is the sum of the current operating data rates 180 of all PMEs in the aggregation group, without the 64/65B 181 encapsulation overhead and PAF overhead, but accounting for the 182 Inter-Frame Gaps (IFG). 184 When using the stated definition of ifSpeed for the PCS, there would 185 be no frame loss in the following configuration (the test-sets are 186 configured to generate 100% of back to back traffic, i.e. minimal 187 IFG, at 10 or 100Mbps, with min and max frame sizes; the EFM 188 interfaces are aggregated, to achieve the shown speed): 190 [testset]--10BaseT--[CO]--2BaseTL--[CPE]--10BaseT--[testset] 191 ifSpeed= 10Mbps 10Mbps 10Mbps 193 [testset]--100BaseT--[CO]--10PassTS--[CPE]--100BaseT--[testset] 194 ifSpeed= 100Mbps 100Mbps 100Mbps 196 Figure 1: Example configuration with no frame loss 198 The following figure shows the layering diagram and corresponding use 199 of ifTable and ifMauTable: 201 _________________________ _ 202 | LLC | | 203 +-------------------------+ | 1 ifEntry 204 | MAC | | ifType: ethernetCsmacd(6) 205 +-------------------------+ > ifMauEntry 206 | Reconsiliation | | ifMauType: dot3MauType2BaseTL or 207 +-------------------------+ | dot3MauType10PassTS 208 | PCS | | 209 +-------------+---+-------+ + 210 | TC \ | | | | 211 +-----\ | | | | 212 | PMA > PME 1 |...| PME N | > N ifEntry (N=1..32) 213 +-----/ | | | | ifType: shdsl(169) or vdsl(97) 214 | PMD/ | | | | 215 -------------+---+------- - 217 Figure 2: Use of ifTable and ifMauTable for EFMCu ports 219 The ifStackTable is indexed by the ifIndex values of the aggregated 220 EFMCu port (PCS) and the PMEs connected to it. ifStackTable allows a 221 Network Management application to determine which PMEs are connected 222 to a particular PCS and change connections (if supported by the 223 application). The ifInvStackTable, being an inverted version of the 224 ifStackTable, provides an efficient means for a Network Management 225 application to read a subset of the ifStackTable and thereby 226 determine which PCS runs on top of a particular PME. 228 A new table ifCapStackTable defined in the IF-CAP-STACK-MIB module, 229 specifies for each higher-layer interface (e.g. PCS port) a list of 230 lower-layer interfaces (e.g. PMEs), which can possibly be cross- 231 connected to that higher-layer interface, determined by the cross- 232 connect capability of the device. This table, modeled after 233 ifStackTable, is read only, reflecting current cross-connect 234 capability of a stacked interface, which can be dynamic in some 235 implementations (e.g. if PMEs are located on a pluggable module and 236 the module is pulled out). Note that PME availability per PCS, 237 described by ifCapStackTable, can be constrained by other parameters, 238 for example by aggregation capacity of a PCS or by the PME in 239 question being already connected to another PCS. So, in order to 240 ensure that a particular PME can be connected to the PCS, all 241 respective parameters (e.g. ifCapStackTable, ifStackTable and 242 efmCuPAFCapacity) SHALL be inspected. 244 The ifInvCapStackTable, also defined in the IF-CAP-STACK-MIB module, 245 describes which higher-layer interfaces (e.g. PCS ports) can 246 possibly be connected to a particular lower-layer interface (e.g. 247 PME), providing inverted mapping of ifCapStackTable. While it 248 contains no additional information beyond that already contained in 249 the ifCapStackTable, the ifInvCapStackTable has the ifIndex values in 250 its INDEX clause in the reverse order, i.e., the lower-layer 251 interface first, and the higher-layer interface second, providing an 252 efficient means for a Network Management application to read a subset 253 of the ifCapStackTable and thereby determine which interfaces can be 254 connected to run on top of a particular interface. 256 3.1.2. PME Aggregation Function (PAF) 258 The PME Aggregation Function (PAF) allows a number of PMEs to be 259 aggregated onto a PCS port, by fragmenting the Ethernet frames, 260 transmitting the fragments over multiple PMEs and assembling the 261 original frames at the remote port. PAF is OPTIONAL, meaning that a 262 device with a single PME MAY perform fragmentation and re-assembly if 263 this function is supported by the device. Note however that the 264 agent is REQUIRED to report on the PAF capability for all EFMCu ports 265 (2BASE-TL and 10PASS-TS). 267 The EFM-CU-MIB module allows a Network Management application to 268 query PAF capability and enable/disable it if supported. Note that 269 enabling PAF effectively turns on fragmentation and re-assembly, even 270 on a single-PME port. 272 3.1.3. Discovery Operation 274 The EFMCu ports may optionally support discovery operation, whereby 275 PMEs, during initialization, exchange information about their 276 respective aggregation groups (PCS). This information can then be 277 used to detect copper misconnections or for an automatic assignment 278 of the local PMEs into aggregation groups instead of a fixed pre- 279 configuration. 281 The MIB modules defined in this document allow a Network Management 282 application to control EFM Discovery mechanism and query its results. 283 Note that the Discovery mechanism can work only if PAF is supported 284 and enabled. 286 Two tables are used by the EFM Discovery mechanism: ifStackTable and 287 ifCapStackTable. The following pseudo-code gives an example of the 288 Discovery and automatic PME assignment for a generic PAF enabled 289 multi-PCS EFMCu device, located at Central Office (CO), using objects 290 defined in these MIB modules and in IF-MIB [Note that automatic PME 291 assignment is only shown here for the purposes of the example. Fixed 292 PME pre-assignment, manual assignment or auto-assignment using an 293 alternative internal algorithm may be chosen by a particular 294 implementation]: 296 // Go over all PCS ports in the CO device 297 FOREACH pcs[i] IN CO_device 298 { // Perform discovery and auto-assignment only on PAF enabled ports 299 // with room for more PMEs 300 IF ( pcs[i].PAFSupported AND pcs[i].NumPMEs < pcs[i].PAFCapacity ) 301 { dc = pcs[i].DiscoveryCode = MAC[i]; // unique 6 Byte per PCS 302 // Go over all disconnected PMEs, which can 303 // pottentially be connected to the PCS 304 FOREACH pme[j] IN ifCapStackTable[pcs[i]] AND 305 NOT ifInvStackTable[pme[j]] // not connected 306 { // Try to grab the remote RT_device, by writing the value 307 // of the local 6 Byte discovery code to the remote 308 // discovery code register (via handshake mechanism). 309 // This operation is atomic Set-if-Clear action, i.e. it 310 // would succeed only if the remote discovery register was 311 // zero. Read the remote discovery code register via Get 312 // operation to see if the RT_device, attached via the PME 313 // is indeed marked as being the CO_device peer. 314 pme[j].RemoteDiscoveryCode = dc; // Set-if-Clear 315 r = pme[j].RemoteDiscoveryCode; // Get 316 IF ( r == dc AND pcs[i].NumPMEs < pcs[i].PAFCapacity) 317 { // Remote RT_device connected via PME[j] is/was a peer 318 // for PCS[i] and there room for another PME in the 319 // PCS[i] aggregation group (max. PAF capacity is not 320 // reached yet). 321 // Connect this PME to the PCS (via ifStackTable, 322 // ifInvStackTable being inverse of ifStackTable is 323 // updated automatically) 324 ADD pme[j] TO ifStackTable[pcs[i]]; 325 // pcs[i] is auto-added to ifInvStackTable[pme[j]] 326 pcs[i].NumPMEs = pcs[i].NumPMEs + 1; 327 // Discover all other disconnected PMEs, 328 // attached to the same RT_device and connect them to 329 // the PCS provided there is enough room for more PMEs. 330 FOREACH pme[k] IN ifCapStackTable[pcs[i]] and 331 NOT ifInvStackTable[pme[k]] 332 { r = pme[k].RemoteDiscoveryCode; // Get 333 IF ( r == dc AND 334 pcs[i].NumPMEs < pcs[i].PAFCapacity) 335 { ADD pme[k] TO ifStackTable[pcs[i]]; 336 // pcs[i] is added TO ifInvStackTable[pme[k]] 337 pcs[i].NumPMEs = pcs[i].NumPMEs + 1; 338 } 339 } 340 } 341 // At this point we have discovered all local PMEs which 342 // are physically connected to the same remote RT_device 343 // and connected them to PCS[i]. Go to the next PCS. 344 BREAK; 345 } 346 } 347 } 349 An SNMP Agent for a EFMCu device builds ifCapStackTable and its 350 inverse ifInvCapStackTable according to the information contained in 351 the Clause 45 PME_Available_register (see [802.3ah] 61.1.5.3 and 352 45.2.3.20). 354 Adding a PME to the ifStackTable row for a specific PCS, involves 355 actual connection of the PME to the PCS, which can be done by 356 modifying Clause 45 PME_Aggregate_register (see [802.3ah] 61.1.5.3 357 and 45.2.3.21). 359 Note that PCS port does not have to be operationally 'down' for the 360 connection to succeed. In fact, a dynamic PME addition (and removal) 361 MAY be implemented with an available PME being initialized first (by 362 setting its ifAdminStatus to 'up') and then added to an operationally 363 'up' PCS port, by modifying a respective ifStackTable (and respective 364 ifInvStackTable) entry. 366 It is RECOMMENDED that a removal of the last operationally 'up' PME 367 from an operationally 'up' PCS would be rejected by the 368 implementation, as this action would completely drop the link. 370 3.1.4. EFMCu ports initialization 372 EFMCu ports being built on top of xDSL technology, require a lengthy 373 initialization or 'training' process, before any data can pass. 374 During this initialization both ends of a link (peers) work 375 cooperatively to achieve required data rate on a particular copper 376 pair. Sometimes, when the copper line is too long or the noise on 377 the line is too high, that 'training' process may fail to achieve a 378 specific target rate with required characteristics. 380 The ifAdminStatus object from the IF-MIB, controls the desired state 381 of a PCS with all the PMEs connected to it or of an individual PME 382 port. Setting this object to 'up' instructs a particular PCS or PME 383 to start initialization process, which may take tens of seconds for 384 EFMCu ports, especially if PAF is involved. The ifOperStatus object 385 shows the operational state of an interface (extended by 386 ifMauMediaAvailable object from MAU-MIB for PCS and 387 efmCuPmeOperStatus defined in the EFM-CU-MIB module for PME 388 interfaces). 390 A disconnected PME may be initialized by changing the ifAdminState 391 from 'down' to 'up'. Changing the ifAdminState to 'up' on the PCS 392 initializes all PMEs connected to that particular PCS. Note that in 393 case of PAF some interfaces may fail to initialize while others 394 succeed. The PCS is considered operationally 'up' if at least one 395 PME aggregated by its PAF is operationally 'up'. When all PMEs 396 connected to the PCS are 'down' the PCS SHALL be considered 397 operationally 'lowerLayerDown'. The PCS SHALL be considered 398 operationally 'notPresent' if it is not connected to any PME. The 399 PCS/PME interface SHALL remain operationally 'down' during 400 initialization. 402 The efmCuPmeOperStatus defined in the EFM-CU-MIB module expands PME's 403 ifOperStatus value of 'down' to 'downReady', 'downNotReady' and 404 'init' values, indicating various EFMCu PME specific states. 406 3.1.5. Usage of ifTable 408 Both PME and PCS interfaces of the EFMCu PHY are managed using 409 interface specific management objects defined in the EFM-CU-MIB 410 module and generic interface objects from the ifTable of IF-MIB, with 411 all management table entries referenced by the interface index 412 ifIndex. 414 The following table summarizes EFMCu specific interpretations for 415 some of the ifTable objects specified by the mandatory 416 ifGeneralInformationGroup: 418 +---------------+---------------------------------------------------+ 419 | IF-MIB object | EFMCu interpretation | 420 +---------------+---------------------------------------------------+ 421 | ifIndex | Interface index. Note that each PME and each PCS | 422 | | in the EFMCu PHY MUST have a unique index, as | 423 | | there some PCS and PME specific attributes | 424 | | accessible only on the PCS or PME level. | 425 | ifType | ethernetCsmacd(6) for PCS, shdsl(169) for | 426 | | 2BASE-TL PME, vdsl(97) for 10PASS-TS PME | 427 | ifSpeed | Operating data rate for the PME. For the PCS it | 428 | | is the sum of the current operating data rates of | 429 | | all PMEs in the aggregation group, without the | 430 | | 64/65B encapsulation overhead and PAF overhead, | 431 | | but accounting for the Inter-Frame Gaps (IFG) | 432 | ifAdminStatus | Setting this object to 'up' instructs a | 433 | | particular PCS (with all PMEs connected to it) or | 434 | | PME to start initialization process | 435 | ifOperStatus | efmCuPmeOperStatus supplements the 'down' value | 436 | | of ifOperStatus for PMEs. | 437 +---------------+---------------------------------------------------+ 439 Table 1 441 3.2. Relation to SHDSL MIB module 443 G.SHDSL.bis modems, similar to PME(s) comprising a 2BASE-TL port, are 444 described in HDSL2-SHDSL-LINE-MIB [RFC4319]. Note that not all 445 attributes of G.SHDSL modems reflected in HDSL2-SHDSL-LINE-MIB have 446 adequate management objects (Clause 30 attributes and Clause 45 447 registers) in the EFM standard. 449 Because of these differences and for the purposes of simplicity, 450 unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs 451 and name consistency (e.g. prefixing the 2BASE-TL PME related objects 452 with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided not to 453 reference HDSL2-SHDSL-LINE-MIB objects, but define all the relevant 454 objects in the EFM-CU-MIB module. 456 However, if some functionality, not available in the EFM-CU-MIB 457 module, is required and supported by the PME, e.g. performance 458 monitoring, relevant HDSL2-SHDSL-LINE-MIB groups MAY be included and 459 applied for PMEs of 2BASE-TL subtype. 461 3.3. Relation to VDSL MIB module 463 VDSL (DMT) modems, similar to the PME(s) comprising a 10PASS-TS port, 464 are described in VDSL-LINE-EXT-MCM-MIB [RFC4070]. Note that not all 465 attributes of VDSL modems reflected in VDSL-LINE-EXT-MCM-MIB have 466 adequate management objects (Clause 30 attributes and Clause 45 467 registers) in the EFM standard. 469 Because of these differences and for the purposes of simplicity, 470 unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs 471 and name consistency, it was decided not to reference VDSL-LINE-EXT- 472 MCM-MIB objects, but define all the relevant objects in the EFM-CU- 473 MIB module. 475 However, if some functionality, not available in the EFM-CU-MIB 476 module, is required and supported by the PME, relevant VDSL-LINE-EXT- 477 MCM-MIB groups MAY be included and applied for PMEs of 10PASS-TS 478 subtype. 480 3.4. Relation to Ethernet-Like and MAU MIB modules 482 The implementation of EtherLike-MIB [RFC3635] and MAU-MIB [I-D.ietf- 483 hubmib-rfc3636bis] is REQUIRED for the EFMCu interfaces. 485 Two new values of ifMauType (OBJECT-IDENTITIES of dot3MauType) and 486 corresponding bit definitions of ifMauTypeListBits 487 (IANAifMauTypeListBits) have been defined in the IANA-MAU-MIB 488 [I-D.ietf-hubmib-rfc3636bis] for the EFMCu MAUs: 490 o dot3MauType2BaseTL and b2BaseTL - for 2BASE-TL MAU 492 o dot3MauType10PassTS and b10PassTS - for 10PASS-TS MAU 494 Additionally IANA-MAU-MIB defines two new values of 495 ifMauMediaAvailable, as a textual convention IANAifMauMediaAvailable 496 - availableReduced and ready, specifically for the EFMCu ports. Due 497 to the PME aggregation, the EFMCu interpretation of some possible 498 ifMauMediaAvailable values differs from other MAUs as follows: 500 o unknown - the EFMCu interface (PCS with connected PMEs) is 501 initializing 503 o ready - the interface is down, at least one PME in the aggregation 504 group (all PMEs connected to the PCS) is ready for handshake 506 o available - the interface is up, all PMEs in the aggregation group 507 are up 509 o notAvailable - the interface is down, all PMEs in the aggregation 510 group are down, no handshake tones are detected by any PME 512 o availableReduced - the interface is up, a link fault is detected 513 at the receive direction by one or more PMEs in the aggregation 514 group, but at least one PME is up 516 o pmdLinkFault - a link fault is detected at the receive direction 517 by all PMEs in the aggregation group 519 As an EtherLike interface every EFMCu port (an ifEntry representing a 520 consolidation of LLC, MAC and PCS (sub)layers) SHALL return an ifType 521 of ethernetCsmacd(6). While most of the MAU characteristics are not 522 applicable to the EFMCu ports (no auto-negotiation, false carriers or 523 jabber), they SHALL return an appropriate ifMauType 524 (dot3MauType2BaseTL or dot3mauType10PassTS) in order to direct the 525 management software to look in the EFM-CU-MIB module for the desired 526 information. For example the information on the particular EFMCu 527 flavor that an EFMCu port is running is available from 528 efmCuOperSubType, defined in the EFM-CU-MIB module. 530 Since EFMCu PMEs are not EtherLike interfaces, they cannot be 531 instantiated as MAU interface objects. 533 4. MIB Structure 535 4.1. EFM Copper MIB Overview 537 The main management objects defined in the EFM-CU-MIB module are 538 split into 2 groups: 540 o efmCuPort - containing objects for configuration, capabilities, 541 status and notifications, common to all EFMCu PHYs. 543 o efmCuPme - containing objects for configuration, capabilities, 544 status and notifications of EFMCu PMEs. 546 The efmCuPme group in turn contains efmCuPme2B and efmCuPme10P 547 groups, which define PME Profiles specific to 2BASE-TL and 10PASS-TS 548 PMEs respectively, as well as PME specific status information. 550 4.2. Interface stack capability MIB Overview 552 The IF-CAP-STACK-MIB module contains 2 tables: 554 o ifCapStackTable - containing objects that define possible 555 relationships among the sub-layers of an interface with flexible 556 cross-connect (cross-connect capability). 558 o ifInvCapStackTable - an inverse of the ifCapstackTable. 560 4.3. PME Profiles 562 Since a managed node can have a large number of EFMCu PHYs, 563 provisioning every parameter on every EFMCu PHY may become 564 burdensome. Moreover, most PMEs are provisioned identically with the 565 same set of parameters. To simplify the provisioning process, the 566 EFM-CU-MIB module makes use of configuration profiles, similar to 567 HDSL2-SHDSL-LINE-MIB and VDSL-LINE-EXT-MCM-MIB. A profile is a set 568 of parameters, used either for configuration or representation of a 569 PME. The same profile can be shared by multiple PME ports, using the 570 same configuration. 572 The PME profiles are defined in efmCuPme2BProfileTable and 573 efmCu10PProfileTable for 2BASE-TL and 10PASS-TS PMEs respectively. 574 There are 12 predefined standard profiles for 2BASE-TL and 22 575 standard profiles for 10PASS-TS, defined in 802.3ah and dedicated for 576 rapid provisioning of EFMCu PHYs in most scenarios. In addition the 577 EFM-CU-MIB defines two additional predefined profiles for "best- 578 effort" provisioning of 2BASE-TL PMEs. An ability to define new 579 configuration profiles is also provided to allow for EFMCu deployment 580 tailored to specific copper environment and spectral regulations. 582 A specific configuration or administrative profile is assigned to a 583 specific PME via efmCuPmeAdminProfile object. If 584 efmCuPmeAdminProfile is zero, then efmCuAdminProfile object of the 585 PCS port, connected to the PME, determines the configuration profile 586 (or a list of possible profiles) for that PME. This mechanism allows 587 to specify a common profile(s) for all PMEs connected to the PCS 588 port, with an ability to change individual PME profiles by setting 589 efmCuPmeAdminProfile object, which overwrites profile set by 590 efmCuAdminProfile. 592 A current operating PME profile is pointed to by efmCuPmeOperProfile 593 object. Note that this profile entry, can be created automatically, 594 to reflect achieved parameters in adaptive (not fixed) 595 initialization. 597 4.4. Mapping of IEEE 802.3ah Managed Objects 599 This section contains the mapping between relevant managed objects 600 (attributes) defined in [802.3ah] Clause 30, and managed objects 601 defined in this document and in associated MIB modules, i.e., the IF- 602 MIB [RFC2863]. 604 Note that majority of the objects defined in the EFM-CU-MIB module do 605 not have direct counterparts in Clause 30 and instead refer to Clause 606 45 registers. 608 +---------------------------------+---------------------------------+ 609 | IEEE 802.3 Managed Object | Corresponding SNMP Object | 610 +---------------------------------+---------------------------------+ 611 | oMAU - Basic Package | | 612 | (Mandatory) | | 613 | aMAUType | ifMauType (MAU-MIB) | 614 | aMAUTypeList | ifMauTypeListBits (MAU-MIB) | 615 | aMediaAvailable | ifMediaAvailable (MAU-MIB) | 616 | oPAF - Basic Package | | 617 | (Mandatory) | | 618 | aPAFID | ifIndex (IF-MIB) | 619 | aPhyEnd | efmCuPhySide | 620 | aPHYCurrentStatus | efmCuStatus | 621 | aPAFSupported | efmCuPAFSupported | 622 | oPAF - PME Aggregation Package | | 623 | (Optional) | | 624 | aPAFAdminState | efmCuPAFAdminState | 625 | aLocalPAFCapacity | efmCuPAFCapacity | 626 | aLocalPMEAvailable | ifCapStackTable | 627 | aLocalPMEAggregate | ifStackTable (IF-MIB) | 628 | aRemotePAFSupported | efmCuRemotePAFSupported | 629 | aRemotePAFCapacity | efmCuRemotePAFCapacity | 630 | aRemotePMEAggregate | | 631 | oPME - 10P/2B Package | | 632 | (Mandatory) | | 633 | aPMEID | ifIndex (IF-MIB) | 634 | aPMEAdminState | ifAdminState (IF-MIB) | 635 | aPMEStatus | efmCuPmeStatus | 636 | aPMESNRMgn | efmCuPmeSnrMgn | 637 | aTCCodingViolations | efmCuPmeTCCodingErrors | 638 | aTCCRCErrors | efmCuPmeTCCrcErrors | 639 | aProfileSelect | efmCuAdminProfile, | 640 | | efmCuPmeAdminProfile | 641 | aOperatingProfile | efmCuPmeOperProfile | 642 | aPMEFECCorrectedBlocks | efmCuPme10PFECCorrectedBlocks | 643 | aPMEFECUncorrectableBlocks | efmCuPme10PFECUncorrectedBlocks | 644 +---------------------------------+---------------------------------+ 646 Table 2 648 5. Interface Stack Capability MIB Definitions 650 IF-CAP-STACK-MIB DEFINITIONS ::= BEGIN 651 IMPORTS 652 MODULE-IDENTITY, OBJECT-TYPE, mib-2 653 FROM SNMPv2-SMI -- RFC 2578 654 RowStatus 655 FROM SNMPv2-TC -- RFC 2579 656 MODULE-COMPLIANCE, OBJECT-GROUP 657 FROM SNMPv2-CONF -- RFC 2580 658 ifStackGroup2, ifStackHigherLayer, ifStackLowerLayer 659 FROM IF-MIB -- RFC 2863 660 ; 662 ifCapStackMIB MODULE-IDENTITY 663 LAST-UPDATED "200610120000Z" -- October 12, 2006 664 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" 665 CONTACT-INFO 666 "WG charter: 667 http://www.ietf.org/html.charters/hubmib-charter.html 669 Mailing Lists: 670 General Discussion: hubmib@ietf.org 671 To Subscribe: hubmib-request@ietf.org 672 In Body: subscribe your_email_address 674 Chair: Dan Romascanu 675 Postal: Avaya 676 Atidim Technology Park, Bldg. 3 677 Tel Aviv 61131 678 Israel 679 Tel: +972 3 645 8414 680 E-mail: dromasca@avaya.com 682 Editor: Edward Beili 683 Postal: Actelis Networks Inc. 684 25 Bazel St., P.O.B. 10173 685 Petach-Tikva 10173 686 Israel 687 Tel: +972-3-924-3491 688 E-mail: edward.beili@actelis.com" 690 DESCRIPTION 691 "The objects in this MIB module are used to describe 692 cross-connect capabilities of stacked (layered) interfaces, 693 complementing ifStackTable and ifInvStackTable defined in 694 IF-MIB and IF-INVERTED-STACK-MIB respectively. 696 Copyright (C) The Internet Society (2006). This version 697 of this MIB module is part of RFC XXXX; see the RFC 698 itself for full legal notices." 700 REVISION "200610120000Z" -- October 12, 2006 701 DESCRIPTION "Initial version, published as RFC XXXX." 703 -- EdNote: Replace XXXX with the actual RFC number & 704 -- remove this note 706 ::= { mib-2 ZZZ } 708 -- EdNote: Replace ZZZ with a real OID once it is 709 -- allocated & remove this note. 711 -- Sections of the module 713 ifCapStackObjects OBJECT IDENTIFIER ::= { ifCapStackMIB 1 } 715 -- Groups in the module 717 -- 718 -- ifCapStackTable group 719 -- 721 ifCapStackTable OBJECT-TYPE 722 SYNTAX SEQUENCE OF IfCapStackEntry 723 MAX-ACCESS not-accessible 724 STATUS current 725 DESCRIPTION 726 "This table, modeled after ifStackTable from IF-MIB, 727 contains information on the possible 'on-top-of' 728 relationships between the multiple sub-layers of network 729 interfaces (as opposed to actual relationships described in 730 ifStackTable). In particular, it contains information on 731 which sub-layers MAY possibly run 'on top of' which other 732 sub-layers, as determined by cross-connect capability of the 733 device, where each sub-layer corresponds to a conceptual row 734 in the ifTable. For example, when the sub-layer with ifIndex 735 value x can be connected to run on top of the sub-layer with 736 ifIndex value y, then this table contains: 738 ifCapStackStatus.x.y=active 740 Note that for most stacked interfaces (e.g. 2BASE-TL) 741 there's always at least one higher-level interface (e.g. PCS 742 port) for each lower-level interface (e.g. PME) and at 743 least one lower-level interface for each higher-level 744 interface, that is, there is at least a single 'active' row 745 for any existing value of x or y. 747 This table is read only as it describes device capability" 749 REFERENCE 750 "IF-MIB, ifStackTable" 751 ::= { ifCapStackObjects 1 } 753 ifCapStackEntry OBJECT-TYPE 754 SYNTAX IfCapStackEntry 755 MAX-ACCESS not-accessible 756 STATUS current 757 DESCRIPTION 758 "Information on a particular relationship between two 759 sub-layers, specifying that one sub-layer runs on 'top' of the 760 other sub-layer. Each sub-layer corresponds to a conceptual 761 row in the ifTable (interface index for lower- and 762 higher-layer respectively)." 763 INDEX { 764 ifStackHigherLayer, 765 ifStackLowerLayer 766 } 767 ::= { ifCapStackTable 1 } 769 IfCapStackEntry ::= SEQUENCE { 770 ifCapStackStatus RowStatus 771 } 773 ifCapStackStatus OBJECT-TYPE 774 SYNTAX RowStatus 775 MAX-ACCESS read-only 776 STATUS current 777 DESCRIPTION 778 "The status of the 'cross-connect capability' relationship 779 between two sub-layers. The following values can be returned: 780 active(1) - indicates that the sub-layer interface, 781 identified by the ifStackLowerLayer MAY 782 be connected to run 'below' the sub-layer 783 interface, identified by the 784 ifStackHigherLayer index. 785 notInService(2) - the sub-layer interfaces cannot be 786 connected temporarily due to 787 unavailability of the interface(s), e.g. 788 one of the interfaces is located on a 789 pluggable module which is absent. 791 Note that lower-layer interface availability per higher-layer, 792 indicated by the value of 'active', can be constrained by 793 other parameters, for example by the aggregation capacity of 794 a higher-layer interface or by the lower-layer interface in 795 question being already connected to another higher-layer 796 interface. In order to ensure that a particular sub-layer can 797 be connected to another sub-layer, all respective objects 798 (e.g. ifCapStackTable, ifStackTable and efmCuPAFCapacity for 799 for EFMCu interfaces) SHALL be inspected. 801 This object is read only, unlike ifStackStatus, as it 802 describes a cross-connect capability." 803 ::= { ifCapStackEntry 1 } 805 ifInvCapStackTable OBJECT-TYPE 806 SYNTAX SEQUENCE OF IfInvCapStackEntry 807 MAX-ACCESS not-accessible 808 STATUS current 809 DESCRIPTION 810 "A table containing information on the possible relationships 811 between the multiple sub-layers of network interfaces. This 812 table, modeled after ifInvStackTable from 813 IF-INVERTED-STACK-MIB, is an inverse of the ifCapStackTable 814 defined in this MIB module. 815 In particular, this table contains information on which 816 sub-layers MAY run 'underneath' which other sub-layers, where 817 each sub-layer corresponds to a conceptual row in the ifTable. 818 For example, when the sub-layer with ifIndex value x MAY be 819 connected to run underneath the sub-layer with ifIndex value 820 y, then this table contains: 822 ifInvCapStackStatus.x.y=active 824 This table contains exactly the same number of rows as the 825 ifCapStackTable, but the rows appear in a different order. 827 This table is read only as it describes a cross-connect 828 capability." 829 REFERENCE 830 "IF-INVERTED-STACK-MIB, ifInvStackTable" 831 ::= { ifCapStackObjects 2 } 833 ifInvCapStackEntry OBJECT-TYPE 834 SYNTAX IfInvCapStackEntry 835 MAX-ACCESS not-accessible 836 STATUS current 837 DESCRIPTION 838 "Information on a particular relationship between two sub- 839 layers, specifying that one sub-layer MAY run underneath the 840 other sub-layer. Each sub-layer corresponds to a conceptual 841 row in the ifTable." 842 INDEX { ifStackLowerLayer, ifStackHigherLayer } 843 ::= { ifInvCapStackTable 1 } 845 IfInvCapStackEntry ::= SEQUENCE { 846 ifInvCapStackStatus RowStatus 847 } 849 ifInvCapStackStatus OBJECT-TYPE 850 SYNTAX RowStatus 851 MAX-ACCESS read-only 852 STATUS current 853 DESCRIPTION 854 "The status of the possible relationship between two 855 sub-layers. 857 An instance of this object exists for each instance of the 858 ifCapStackStatus object, and vice versa. For example, if the 859 variable ifCapStackStatus.H.L exists, then the variable 860 ifInvStackStatus.L.H must also exist, and vice versa. In 861 addition, the two variables always have the same value. 863 The ifInvStackStatus object is read-only, as it describes 864 a cross-connect capability." 865 ::= { ifInvCapStackEntry 1 } 867 -- 868 -- ifCapStackConformance group 869 -- 871 ifCapStackConformance OBJECT IDENTIFIER 872 ::= { ifCapStackObjects 3 } 874 -- Conformance Statements 876 ifCapStackGroups OBJECT IDENTIFIER ::= 877 { ifCapStackConformance 1 } 879 ifCapStackCompliances OBJECT IDENTIFIER ::= 880 { ifCapStackConformance 2 } 882 -- Units of Conformance 884 ifCapStackGroup OBJECT-GROUP 885 OBJECTS { 886 ifCapStackStatus, 887 ifInvCapStackStatus 888 } 889 STATUS current 890 DESCRIPTION 891 "A collection of objects providing information on the 892 cross-connect capability of multi-layer (stacked) network 893 interfaces." 894 ::= { ifCapStackGroups 1 } 896 -- Compliance Statements 898 ifCapStackCompliance MODULE-COMPLIANCE 899 STATUS current 900 DESCRIPTION 901 "The compliance statement for SNMP entities, which provide 902 information on the cross-connect capability of multi-layer 903 (stacked) network interfaces, with flexible cross-connect 904 between the sub-layers. 905 Compliance with the following external compliance statements 906 is REQUIRED: 908 MIB Module Compliance Statement 909 ---------- -------------------- 910 IF-MIB ifCompliance3 911 IF-INVERTED-STACK-MIB ifInvCompliance" 913 MODULE -- this module 914 MANDATORY-GROUPS { 915 ifCapStackGroup 916 } 918 OBJECT ifCapStackStatus 919 SYNTAX INTEGER { active(1) } 920 DESCRIPTION 921 "Support for the notInService(2) value is OPTIONAL for 922 implementations supporting pluggable interfaces." 924 OBJECT ifInvCapStackStatus 925 SYNTAX INTEGER { active(1) } 926 DESCRIPTION 927 "Support for the notInService(2) value is OPTIONAL for 928 implementations supporting pluggable interfaces." 930 MODULE IF-MIB 931 MANDATORY-GROUPS { 932 ifStackGroup2 933 } 935 MODULE IF-INVERTED-STACK-MIB 936 MANDATORY-GROUPS { 937 ifInvStackGroup 938 } 940 ::= { ifCapStackCompliances 1 } 941 END 943 6. EFM Copper MIB Definitions 945 EFM-CU-MIB DEFINITIONS ::= BEGIN 947 IMPORTS 948 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32, 949 Unsigned32, Counter32, mib-2 950 FROM SNMPv2-SMI -- RFC 2578 951 TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress 952 FROM SNMPv2-TC -- RFC 2579 953 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 954 FROM SNMPv2-CONF -- RFC 2580 955 SnmpAdminString 956 FROM SNMP-FRAMEWORK-MIB -- RFC 3411 957 ifIndex, ifSpeed 958 FROM IF-MIB -- RFC 2863 959 ; 961 efmCuMIB MODULE-IDENTITY 962 LAST-UPDATED "200610120000Z" -- October 12, 2006 963 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" 964 CONTACT-INFO 965 "WG charter: 966 http://www.ietf.org/html.charters/hubmib-charter.html 968 Mailing Lists: 969 General Discussion: hubmib@ietf.org 970 To Subscribe: hubmib-request@ietf.org 971 In Body: subscribe your_email_address 973 Chair: Dan Romascanu 974 Postal: Avaya 975 Atidim Technology Park, Bldg. 3 976 Tel Aviv 61131 977 Israel 978 Tel: +972 3 645 8414 979 E-mail: dromasca@avaya.com 981 Editor: Edward Beili 982 Postal: Actelis Networks Inc. 984 25 Bazel St., P.O.B. 10173 985 Petach-Tikva 10173 986 Israel 987 Tel: +972-3-924-3491 988 E-mail: edward.beili@actelis.com" 990 DESCRIPTION 991 "The objects in this MIB module are used to manage 992 the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces 993 2BASE-TL and 10PASS-TS, defined in IEEE Std. 802.3ah-2004, 994 which is now a part of IEEE Std. 802.3-2005. 996 The following references are used throughout this MIB module: 998 [802.3ah] refers to: 999 IEEE Std 802.3ah-2004: 'IEEE Standard for Information 1000 technology - Telecommunications and information exchange 1001 between systems - Local and metropolitan area networks - 1002 Specific requirements - 1003 Part 3: Carrier Sense Multiple Access with Collision 1004 Detection (CSMA/CD) Access Method and Physical Layer 1005 Specifications - 1006 Amendment: Media Access Control Parameters, Physical 1007 Layers and Management Parameters for Subscriber Access 1008 Networks', 07 September 2004. 1010 Of particular interest are Clause 61, 'Physical Coding 1011 Sublayer (PCS) and common specifications, type 10PASS-TS and 1012 type 2BASE-TL', Clause 30, 'Management', Clause 45, 1013 'Management Data Input/Output (MDIO) Interface', Annex 62A, 1014 'PMD profiles for 10PASS-TS' and Annex 63A, 'PMD profiles for 1015 2BASE-TL'. 1017 [G.991.2] refers to: 1018 ITU-T Recommendation G.991.2: 'Single-pair High-speed Digital 1019 Subscriber Line (SHDSL) transceivers', December 2003. 1021 [ANFP] refers to: 1022 NICC Document ND1602:2005/08: 'Specification of the Access 1023 Network Frequency Plan (ANFP) applicable to transmission 1024 systems used on the BT Access Network,' August 2005. 1026 Naming Conventions: 1027 Atn - Attenuation 1028 CO - Central Office 1029 CPE - Customer Premises Equipment 1030 EFM - Ethernet in the First Mile 1031 EFMCu - EFM Copper 1032 MDIO - Management Data Input/Output 1033 Mgn - Margin 1034 PAF - PME Aggregation Function 1035 PBO - Power Back-Off 1036 PCS - Physical Coding Sublayer 1037 PMD - Physical Medium Dependent 1038 PME - Physical Medium Entity 1039 PSD - Power Spectral Density 1040 SNR - Signal to Noise Ratio 1041 TCPAM - Trellis Coded Pulse Amplitude Modulation 1043 Copyright (C) The Internet Society (2006). This version 1044 of this MIB module is part of RFC XXXX; see the RFC 1045 itself for full legal notices." 1047 REVISION "200610120000Z" -- October 12, 2006 1048 DESCRIPTION "Initial version, published as RFC XXXX." 1050 -- EdNote: Replace XXXX with the actual RFC number & 1051 -- remove this note 1053 ::= { mib-2 YYY } 1055 -- EdNote: Replace YYY with a real OID once it is 1056 -- allocated & remove this note. 1058 -- Sections of the module 1060 efmCuObjects OBJECT IDENTIFIER ::= { efmCuMIB 1 } 1062 efmCuConformance OBJECT IDENTIFIER ::= { efmCuMIB 2 } 1064 -- Groups in the module 1066 efmCuPort OBJECT IDENTIFIER ::= { efmCuObjects 1 } 1068 efmCuPme OBJECT IDENTIFIER ::= { efmCuObjects 2 } 1070 -- Textual Conventions 1072 ProfileIndex ::= TEXTUAL-CONVENTION 1073 DISPLAY-HINT "d" 1074 STATUS current 1075 DESCRIPTION 1076 "A unique value, greater than zero, for each PME configuration 1077 profile in the managed EFMCu port. It is RECOMMENDED that 1078 values are assigned contiguously starting from 1. The value 1079 for each profile MUST remain constant at least from one 1080 re-initialization of the entity's network management system 1081 to the next re-initialization." 1082 SYNTAX Unsigned32 (1..255) 1084 ProfileIndexOrZero ::= TEXTUAL-CONVENTION 1085 DISPLAY-HINT "d" 1086 STATUS current 1087 DESCRIPTION 1088 "This textual convention is an extension of the ProfileIndex 1089 convention. The latter defines a greater than zero value used 1090 to identify a PME profile in the managed EFMCu port. This 1091 extension permits the additional value of zero. The value of 1092 zero is object-specific and MUST therefore be defined as part 1093 of the description of any object which uses this syntax. 1094 Examples of the usage of zero value might include situations 1095 where current operational profile is unknown." 1096 SYNTAX Unsigned32 (0..255) 1098 ProfileIndexList ::= TEXTUAL-CONVENTION 1099 DISPLAY-HINT "1d:" 1100 STATUS current 1101 DESCRIPTION 1102 "Represents a list of up to 6 ProfileIndex's. 1103 The ProfileIndex textual convention defines a greater than 1104 zero value used to identify a PME profile in the managed EFMCu 1105 port. The value of this object is a concatenation of one or 1106 more (up to 6) octets, where each octet contains an 8-bit 1107 ProfileIndex value. 1108 The ProfileIndexList specifies a list of alternative 1109 profiles, any of which can be chosen for configuration of an 1110 PME." 1111 SYNTAX OCTET STRING (SIZE(1..6)) 1113 TruthValueOrUnknown ::= TEXTUAL-CONVENTION 1114 STATUS current 1115 DESCRIPTION 1116 "This textual convention is an extension of the TruthValue 1117 convention. The latter defines a boolean value with 1118 possible values of true(1) and false(2). This 1119 extension permits the additional value of unknown(0), which 1120 can be returned as a result of GET operation, when an exact 1121 true or false value of the object cannot be determined." 1122 SYNTAX INTEGER { unknown(0), true(1), false(2) } 1124 -- Port Notifications Group 1126 efmCuPortNotifications OBJECT IDENTIFIER ::= { efmCuPort 0 } 1127 efmCuLowRateCrossing NOTIFICATION-TYPE 1128 OBJECTS { 1129 -- ifIndex is not needed here since we are under specific PCS 1130 ifSpeed, 1131 efmCuThreshLowRate 1132 } 1133 STATUS current 1134 DESCRIPTION 1135 "This notification indicates that the EFMCu port' data rate 1136 has reached/dropped below or exceeded the low rate threshold, 1137 specified by efmCuThreshLowRate. 1139 This notification MAY be send for the -O subtype ports 1140 (2BaseTL-O/10PassTS-O) while the port is up, on the crossing 1141 event in both directions: from normal (rate is above the 1142 threshold) to low (rate equals the threshold or below it) and 1143 from low to normal. This notification is not applicable to 1144 the -R subtypes. 1146 It is RECOMMENDED that a small debouncing period of 2.5 sec, 1147 between the detection of the condition and notification, 1148 is implemented to prevent simultaneous LinkUp/LinkDown and 1149 efmCuLowRateCrossing notifications to be sent. 1151 The adaptive nature of the EFMCu technology allows the port to 1152 adapt itself to the changes in the copper environment, e.g. 1153 an impulse noise, alien crosstalk or a micro-interruption may 1154 temporarily drop one or more PMEs in the aggregation group, 1155 causing a rate degradation of the aggregated EFMCu link. 1156 The dropped PMEs would then try to re-initialize, possibly at 1157 a lower rate than before, adjusting the rate to provide 1158 required target SNR margin. 1160 Generation of this notification is controlled by the 1161 efmCuLowRateCrossingEnable object." 1162 ::= { efmCuPortNotifications 1 } 1164 -- PCS Port group 1166 efmCuPortConfTable OBJECT-TYPE 1167 SYNTAX SEQUENCE OF EfmCuPortConfEntry 1168 MAX-ACCESS not-accessible 1169 STATUS current 1170 DESCRIPTION 1171 "Table for Configuration of EFMCu 2BASE-TL/10PASS-TS (PCS) 1172 Ports. Entries in this table MUST be maintained in a 1173 persistent manner" 1174 ::= { efmCuPort 1 } 1176 efmCuPortConfEntry OBJECT-TYPE 1177 SYNTAX EfmCuPortConfEntry 1178 MAX-ACCESS not-accessible 1179 STATUS current 1180 DESCRIPTION 1181 "An entry in the EFMCu Port Configuration table. 1182 Each entry represents an EFMCu port indexed by the ifIndex. 1183 Note that an EFMCu PCS port runs on top of a single 1184 or multiple PME port(s), which are also indexed by ifIndex." 1185 INDEX { ifIndex } 1186 ::= { efmCuPortConfTable 1 } 1188 EfmCuPortConfEntry ::= 1189 SEQUENCE { 1190 efmCuPAFAdminState INTEGER, 1191 efmCuPAFDiscoveryCode PhysAddress, 1192 efmCuAdminProfile ProfileIndexList, 1193 efmCuTargetDataRate Unsigned32, 1194 efmCuTargetSnrMgn Unsigned32, 1195 efmCuAdaptiveSpectra TruthValue, 1196 efmCuThreshLowRate Unsigned32, 1197 efmCuLowRateCrossingEnable TruthValue 1198 } 1200 efmCuPAFAdminState OBJECT-TYPE 1201 SYNTAX INTEGER { 1202 enabled(1), 1203 disabled(2) 1204 } 1205 MAX-ACCESS read-write 1206 STATUS current 1207 DESCRIPTION 1208 "Administrative (desired) state of the PAF of the EFMCu port 1209 (PCS). 1210 When 'disabled', PME Aggregation will not be performed by the 1211 PCS. No more than a single PME can be assigned to this PCS in 1212 this case. 1213 When 'enabled', PAF will be performed by the PCS when the link 1214 is Up, even on a single attached PME, if PAF is supported. 1216 PCS ports incapable of supporting PAF SHALL return a value of 1217 'disabled'. Attempts to 'enable' such ports SHALL be ignored. 1219 PAF 'enabled' port with multiple PMEs assigned cannot be 1220 'disabled'. Attempts to 'disable' such port SHALL be rejected, 1221 until at most one PME is left assigned. 1223 Changing PAFAdminState is a traffic disruptive operation and 1224 as such SHALL be done when the link is Down. Attempts to 1225 change this object SHALL be ignored if the link is Up or 1226 Initializing. 1228 This object maps to the Clause 30 attribute aPAFAdminState. 1230 If a Clause 45 MDIO Interface to the PCS is present, then this 1231 object maps to the PAF enable bit in the 10P/2B PCS control 1232 register. 1234 This object MUST be maintained in a persistent manner." 1235 REFERENCE 1236 "[802.3ah] 61.2.2, 45.2.3.18.3" 1237 ::= { efmCuPortConfEntry 1 } 1239 efmCuPAFDiscoveryCode OBJECT-TYPE 1240 SYNTAX PhysAddress 1241 MAX-ACCESS read-write 1242 STATUS current 1243 DESCRIPTION 1244 "PAF Discovery Code of the EFMCu port (PCS). 1245 A unique 6 Byte long code used by the Discovery function, when 1246 PAF is supported. 1247 PCS ports incapable of supporting PAF SHALL return a value of 1248 all zeroes. Attempts to change this object SHALL be ignored in 1249 this case. 1250 This object MUST be instantiated for the -O subtype PCS before 1251 writing operations on the efmCuPAFRemoteDiscoveryCode 1252 (Set_if_Clear and Clear_if_Same) are performed by PMEs 1253 associated with the PCS. 1254 The value of this object is read-only for -R port subtypes. 1255 The initial value of this object for -R ports after reset 1256 is 0. This value may be changed as a result of writing 1257 operation on efmCuPAFRemoteDiscoveryCode variable of remote 1258 PME of -O subtype, connected to one of the local PMEs 1259 associated with the PCS. 1261 Discovery MUST be performed when the link is Down. 1262 Attempts to change this object MUST be rejected with the error 1263 inconsistentValue if the link is Up or Initializing. 1265 The PAF Discovery code maps to the local Discovery code 1266 variable in PAF (note that it does not have a corresponding 1267 Clause 45 register)" 1268 REFERENCE 1269 "[802.3ah] 61.2.2.8.3, 61.2.2.8.4, 45.2.6.6.1" 1270 ::= { efmCuPortConfEntry 2 } 1272 efmCuAdminProfile OBJECT-TYPE 1273 SYNTAX ProfileIndexList 1274 MAX-ACCESS read-write 1275 STATUS current 1276 DESCRIPTION 1277 "Desired configuration Profile(s), common for all PMEs in the 1278 EFMCu port. This object is a list of pointers to entries in 1279 either efmCuPme2BProfileTable or 1280 efmCuPme10PProfileTable, depending on the current 1281 operating SubType of the EFMCu port as indicated by 1282 efmCuPortSide. 1283 The value of this object is a list of up to 6 indices of 1284 Profiles. If this list consists of a single Profile index, 1285 then all PMEs assigned to this EFMCu port SHALL be configured 1286 according to the Profile referenced by that index, unless it 1287 is overwritten by corresponding non-zero efmCuPmeAdminProfile, 1288 which takes precedence over efmCuAdminProfile. 1289 The list, consisting of more than one index, allows each PME 1290 in the port to be configured according to any Profile 1291 specified in the list. 1292 By default this object has a value of 0x01, referencing 1st 1293 entry in efmCuPme2BProfileTable or efmCuPme10PProfileTable. 1295 This object is writable and readable for the -O subtype 1296 (2BaseTL-O or 10PassTS-O) EFMCu ports. It is unavailable for 1297 the -R subtype (2BaseTL-R or 10PassTS-R) ports. 1299 Note that current operational Profile value is available via 1300 efmCuPmeOperProfile object. 1302 Modification of this object MUST be performed when the link is 1303 Down. Attempts to change this object MUST be rejected, if the 1304 link is Up or Initializing. 1305 Attempts to set this object to a list with a member 1306 value, that is not the value of the index for an active entry 1307 in the corresponding profile table, MUST be rejected. 1309 This object MUST be maintained in a persistent manner." 1310 REFERENCE 1311 "[802.3ah] 30.11.2.1.6" 1312 DEFVAL { '01'H } 1313 ::= { efmCuPortConfEntry 3 } 1315 efmCuTargetDataRate OBJECT-TYPE 1316 SYNTAX Unsigned32(1..100000|999999) 1317 UNITS "Kbps" 1318 MAX-ACCESS read-write 1319 STATUS current 1320 DESCRIPTION 1321 "Desired EFMCu port 'net' (as seen across MII) Data Rate in 1322 Kbps, to be achieved during initialization, under spectral 1323 restrictions placed on each PME via efmCuAdminProfile or 1324 efmCuPmeAdminProfile, with the desired SNR Margin specified by 1325 efmCuTargetSnrMgn. 1326 In case of PAF, this object represents a sum of individual PME 1327 data rates, modified to compensate for fragmentation and 1328 64/65B framing overhead (e.g. target data rate of 10Mbps 1329 SHALL allow lossless transmission of full-duplex 10Mbps 1330 Ethernet frame stream with minimal inter-frame gap). 1332 The value is limited above by 100Mbps as this is the max 1333 burst rate across MII for EFMCu ports. 1335 The value between 1 and 100000 indicates that the total data 1336 rate (ifSpeed) of the EFMCu port after initialization SHALL 1337 be equal to the target data rate or less, if the target data 1338 rate cannot be achieved under spectral restrictions specified 1339 by efmCuAdminProfile/efmCuPmeAdminProfile and with desired SNR 1340 margin. In case the copper environment allows to achieve 1341 higher total data rate than that specified by the target, the 1342 excess capability SHALL be either converted to additional SNR 1343 margin or reclaimed by minimizing transmit power as controlled 1344 by efmCuAdaptiveSpectra. 1346 The value of 999999 means that the target data rate is not 1347 fixed and SHALL be set to the maximum attainable rate during 1348 initialization (Best Effort), under specified spectral 1349 restrictions and with desired SNR Margin. 1351 This object is read-write for the -O subtype EFMCu ports 1352 (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. 1354 Changing of the Target Data Rate MUST be performed when the 1355 link is Down. Attempts to change this object MUST be rejected 1356 with the error inconsistentValue, if the link is Up or 1357 Initializing. 1359 Note that current Data Rate of the EFMCu port is represented 1360 by ifSpeed object of IF-MIB. 1362 This object MUST be maintained in a persistent manner." 1363 ::= { efmCuPortConfEntry 4 } 1365 efmCuTargetSnrMgn OBJECT-TYPE 1366 SYNTAX Unsigned32(0..21) 1367 UNITS "dB" 1368 MAX-ACCESS read-write 1369 STATUS current 1370 DESCRIPTION 1371 "Desired EFMCu port SNR Margin to be achieved on all PMEs 1372 assigned to the port, during initializiation. (The SNR margin 1373 is the difference between the desired SNR and the actual SNR). 1375 Note that 802.3ah recommends using default Target SNR Margin 1376 of 5dB for 2BASE-TL ports and 6dB for 10PASS-TS ports in order 1377 to achieve mean Bit Error Rate (BER) of 10^-7 at the PMA 1378 service interface. 1380 This object is read-write for the -O subtype EFMCu ports 1381 (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. 1383 Changing of the Target SNR Margin MUST be performed when the 1384 link is Down. Attempts to change this object MUST be rejected 1385 with the error inconsistentValue, if the link is Up or 1386 Initializing. 1388 Note that current SNR Margin of the PMEs comprising the EFMCu 1389 port is represented by efmCuPmeSnrMgn. 1391 This object MUST be maintained in a persistent manner." 1392 REFERENCE 1393 "[802.3ah] 61.1.2" 1394 ::= { efmCuPortConfEntry 5 } 1396 efmCuAdaptiveSpectra OBJECT-TYPE 1397 SYNTAX TruthValue 1398 MAX-ACCESS read-write 1399 STATUS current 1400 DESCRIPTION 1401 "Indicates how to utilize excess capacity when the copper 1402 environment allows to achieve higher total data rate than that 1403 specified by the efmCuTargetDataRate. 1405 Value of true(1) indicates that the excess capability SHALL be 1406 reclaimed by minimizing transmit power, e.g. using higher 1407 constellations and Power Back-Off, in order to reduce 1408 interference to other copper pairs in the binder and the 1409 adverse impact to link/system performance. 1411 Value of false(2) indicates that the excess capability SHALL 1412 be converted to additional SNR margin and spread evenly across 1413 all active PMEs assigned to the (PCS) port, to increase link 1414 robustness. 1416 This object is read-write for the -O subtype EFMCu ports 1417 (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. 1419 Changing of this object MUST be performed when the link is 1420 Down. Attempts to change this object MUST be rejected with the 1421 error inconsistentValue, if the link is Up or Initializing. 1423 This object MUST be maintained in a persistent manner." 1424 ::= { efmCuPortConfEntry 6 } 1426 efmCuThreshLowRate OBJECT-TYPE 1427 SYNTAX Unsigned32(1..100000) 1428 UNITS "Kbps" 1429 MAX-ACCESS read-write 1430 STATUS current 1431 DESCRIPTION 1432 "This object configures the EFMCu port low rate crossing alarm 1433 threshold. When the current value of ifSpeed for this port 1434 reaches/drops below or exceeds this threshold, an 1435 efmCuLowRateCrossing notification MAY be generated if enabled 1436 by efmCuLowRateCrossingEnable. 1438 This object is read-write for the -O subtype EFMCu ports 1439 (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. 1441 This object MUST be maintained in a persistent manner." 1442 ::= { efmCuPortConfEntry 7 } 1444 efmCuLowRateCrossingEnable OBJECT-TYPE 1445 SYNTAX TruthValue 1446 MAX-ACCESS read-write 1447 STATUS current 1448 DESCRIPTION 1449 "Indicates whether efmCuLowRateCrossing notifications should 1450 be generated for this interface. 1452 Value of true(1) indicates that efmCuLowRateCrossing 1453 notification is enabled. Value of false(2) indicates that 1454 the notification is disabled. 1456 This object is read-write for the -O subtype EFMCu ports 1457 (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. 1459 This object MUST be maintained in a persistent manner." 1460 ::= { efmCuPortConfEntry 8 } 1462 efmCuPortCapabilityTable OBJECT-TYPE 1463 SYNTAX SEQUENCE OF EfmCuPortCapabilityEntry 1464 MAX-ACCESS not-accessible 1465 STATUS current 1466 DESCRIPTION 1467 "Table for Capabilities of EFMCu 2BASE-TL/10PASS-TS (PCS) 1468 Ports. Entries in this table MUST be maintained in a 1469 persistent manner" 1470 ::= { efmCuPort 2 } 1472 efmCuPortCapabilityEntry OBJECT-TYPE 1473 SYNTAX EfmCuPortCapabilityEntry 1474 MAX-ACCESS not-accessible 1475 STATUS current 1476 DESCRIPTION 1477 "An entry in the EFMCu Port Capability table. 1478 Each entry represents an EFMCu port indexed by the ifIndex. 1479 Note that an EFMCu PCS port runs on top of a single 1480 or multiple PME port(s), which are also indexed by ifIndex." 1481 INDEX { ifIndex } 1482 ::= { efmCuPortCapabilityTable 1 } 1484 EfmCuPortCapabilityEntry ::= 1485 SEQUENCE { 1486 efmCuPAFSupported TruthValue, 1487 efmCuPeerPAFSupported TruthValueOrUnknown, 1488 efmCuPAFCapacity Unsigned32, 1489 efmCuPeerPAFCapacity Unsigned32 1490 } 1492 efmCuPAFSupported OBJECT-TYPE 1493 SYNTAX TruthValue 1494 MAX-ACCESS read-only 1495 STATUS current 1496 DESCRIPTION 1497 "PME Aggregation Function (PAF) Capability of the EFMCu port 1498 (PCS). 1499 This object has a value of true(1) when the PCS can perform 1500 PME aggregation on the available PMEs. 1501 Ports incapable of PAF SHALL return a value of false(2). 1503 This object maps to the Clause 30 attribute aPAFSupported. 1505 If a Clause 45 MDIO Interface to the PCS is present, 1506 then this object maps to the PAF available bit in the 1507 10P/2B capability register." 1508 REFERENCE 1509 "[802.3ah] 61.2.2, 30.11.1.1.4, 45.2.3.17.1" 1510 ::= { efmCuPortCapabilityEntry 1 } 1512 efmCuPeerPAFSupported OBJECT-TYPE 1513 SYNTAX TruthValueOrUnknown 1514 MAX-ACCESS read-only 1515 STATUS current 1516 DESCRIPTION 1517 "PME Aggregation Function (PAF) Capability of the EFMCu port 1518 (PCS) link partner. 1519 This object has a value of true(1) when the remote PCS can 1520 perform PME aggregation on its available PMEs. 1521 Ports whose peers are incapable of PAF, SHALL return a value 1522 of false(2). 1523 Ports whose peers cannot be reached because of the link 1524 state, SHALL return a value if unknown(0). 1526 This object maps to the Clause 30 attribute 1527 aRemotePAFSupported. 1529 If a Clause 45 MDIO Interface to the PCS is present, then 1530 this object maps to the Remote PAF supported bit in the 1531 10P/2B capability register." 1532 REFERENCE 1533 "[802.3ah] 61.2.2, 30.11.1.1.9, 45.2.3.17.2" 1534 ::= { efmCuPortCapabilityEntry 2 } 1536 efmCuPAFCapacity OBJECT-TYPE 1537 SYNTAX Unsigned32 (1..32) 1538 MAX-ACCESS read-only 1539 STATUS current 1540 DESCRIPTION 1541 "Number of PMEs that can be aggregated by the local PAF. 1542 The number of PMEs currently assigned to a particular 1543 EFMCu port (efmCuNumPMEs) is never greater than 1544 efmCuPAFCapacity. 1546 This object maps to the Clause 30 attribute 1547 aLocalPAFCapacity." 1548 REFERENCE 1549 "[802.3ah] 61.2.2, 30.11.1.1.6" 1550 ::= { efmCuPortCapabilityEntry 3 } 1552 efmCuPeerPAFCapacity OBJECT-TYPE 1553 SYNTAX Unsigned32 (0|1..32) 1554 MAX-ACCESS read-only 1555 STATUS current 1556 DESCRIPTION 1557 "Number of PMEs that can be aggregated by the PAF of the peer 1558 Phy (PCS port). 1559 Value of 0 is returned when peer PAF Capacity is unknown 1560 (peer cannot be reached). 1562 This object maps to the Clause 30 attribute 1563 aRemotePAFCapacity." 1564 REFERENCE 1565 "[802.3ah] 61.2.2, 30.11.1.1.10" 1566 ::= { efmCuPortCapabilityEntry 4 } 1568 efmCuPortStatusTable OBJECT-TYPE 1569 SYNTAX SEQUENCE OF EfmCuPortStatusEntry 1570 MAX-ACCESS not-accessible 1571 STATUS current 1572 DESCRIPTION 1573 "This table provides overall status information of EFMCu 1574 2BASE-TL/10PASS-TS ports, complementing the generic status 1575 information from the ifTable of IF-MIB and ifMauTable of 1576 MAU-MIB. Additional status information about connected PMEs 1577 is available from efmCuPmeStatusTable. 1579 This table contains live data from the equipment. As such, 1580 it is NOT persistent." 1581 ::= { efmCuPort 3 } 1583 efmCuPortStatusEntry OBJECT-TYPE 1584 SYNTAX EfmCuPortStatusEntry 1585 MAX-ACCESS not-accessible 1586 STATUS current 1587 DESCRIPTION 1588 "An entry in the EFMCu Port Status table. 1589 Each entry represents an EFMCu port indexed by the ifIndex. 1590 Note that an EFMCu PCS port runs on top of a single 1591 or multiple PME port(s), which are also indexed by ifIndex." 1592 INDEX { ifIndex } 1593 ::= { efmCuPortStatusTable 1 } 1595 EfmCuPortStatusEntry ::= 1596 SEQUENCE { 1597 efmCuFltStatus BITS, 1598 efmCuPortSide INTEGER, 1599 efmCuNumPMEs Unsigned32, 1600 efmCuPAFInErrors Counter32, 1601 efmCuPAFInSmallFragments Counter32, 1602 efmCuPAFInLargeFragments Counter32, 1603 efmCuPAFInBadFragments Counter32, 1604 efmCuPAFInLostFragments Counter32, 1605 efmCuPAFInLostStarts Counter32, 1606 efmCuPAFInLostEnds Counter32, 1607 efmCuPAFInOverflows Counter32 1608 } 1610 efmCuFltStatus OBJECT-TYPE 1611 SYNTAX BITS { 1612 noPeer(0), 1613 peerPowerLoss(1), 1614 pmeSubTypeMismatch(2), 1615 lowRate(3) 1616 } 1617 MAX-ACCESS read-only 1618 STATUS current 1619 DESCRIPTION 1620 "EFMCu (PCS) port Fault Status. This is a bitmap of possible 1621 conditions. The various bit positions are: 1622 noPeer - peer PHY cannot be reached (e.g. 1623 no PMEs attached, all PMEs are Down 1624 etc.) More info is available in 1625 efmCuPmeFltStatus. 1626 peerPowerLoss - peer PHY has indicated impending unit 1627 failure due to loss of local power 1628 ('Dying Gasp'). 1629 pmeSubTypeMismatch - local PMEs in the aggregation group 1630 are not of the same sub-type, e.g. 1631 some PMEs in the local device are -O 1632 while others are -R subtype. 1633 lowRate - ifSpeed of the port reached or dropped 1634 below efmCuThreshLowRate 1636 This object is intended to supplement ifOperStatus object 1637 in IF-MIB and ifMauMediaAvailable in MAU-MIB. 1639 Additional information is available via efmCuPmeFltStatus 1640 object for each PME in the aggregation group (single PME if 1641 PAF is disabled)." 1642 REFERENCE 1643 "IF-MIB, ifOperStatus; MAU-MIB, ifMauMediaAvailable; 1644 efmCuPmeFltStatus" 1645 ::= { efmCuPortStatusEntry 1 } 1647 efmCuPortSide OBJECT-TYPE 1648 SYNTAX INTEGER { 1649 subscriber(1), 1650 office(2), 1651 unknown(3) 1652 } 1653 MAX-ACCESS read-only 1654 STATUS current 1655 DESCRIPTION 1656 "EFM port mode of operation (subtype). 1657 The value of 'subscriber' indicates the port is designated as 1658 '-R' subtype (all PMEs assigned to this port are of subtype 1659 '-R'). 1660 The value of the 'office' indicates that the port is 1661 designated as '-O' subtype (all PMEs assigned to this port are 1662 of subtype '-O'). 1663 The value of 'unknown' indicates that the port has no assigned 1664 PMEs yet or that the assigned PMEs are not of the same side 1665 (subTypePMEMismatch). 1667 This object partially maps to the Clause 30 attribute 1668 aPhyEnd" 1669 REFERENCE 1670 "[802.3ah] 61.1, 30.11.1.1.2" 1671 ::= { efmCuPortStatusEntry 2 } 1673 efmCuNumPMEs OBJECT-TYPE 1674 SYNTAX Unsigned32 (0..32) 1675 MAX-ACCESS read-only 1676 STATUS current 1677 DESCRIPTION 1678 "Number of PMEs that is currently aggregated by the local PAF 1679 (assigned to the EFMCu port using ifStackTable). 1680 This number is never greater than efmCuPAFCapacity. 1682 This object SHALL be automatically incremented or decremented 1683 when a PME is added or deleted to/from the EFMCu port using 1684 ifStackTable." 1685 REFERENCE 1686 "[802.3ah] 61.2.2, 30.11.1.1.6" 1687 ::= { efmCuPortStatusEntry 3 } 1689 efmCuPAFInErrors OBJECT-TYPE 1690 SYNTAX Counter32 1691 MAX-ACCESS read-only 1692 STATUS current 1693 DESCRIPTION 1694 "A number of fragments that have been received across the 1695 gamma interface with RxErr asserted and discarded. 1696 This read-only counter is inactive (not incremented) when the 1697 PAF is unsupported or disabled. Upon disabling the PAF, the 1698 counter retains its previous value. 1700 If a Clause 45 MDIO Interface to the PCS is present, then 1701 this object maps to the 10P/2B PAF RX error register. 1703 Discontinuities in the value of this counter can occur at 1704 re-initialization of the management system, and at other times 1705 as indicated by the value of ifCounterDiscontinuityTime, 1706 defined in IF-MIB." 1707 REFERENCE 1708 "[802.3ah] 45.2.3.21" 1709 ::= { efmCuPortStatusEntry 4 } 1711 efmCuPAFInSmallFragments OBJECT-TYPE 1712 SYNTAX Counter32 1713 MAX-ACCESS read-only 1714 STATUS current 1715 DESCRIPTION 1716 "A number of fragments smaller than minFragmentSize 1717 (64 Bytes), which have been received across the gamma 1718 interface and discarded. 1719 This read-only counter is inactive when the PAF is 1720 unsupported or disabled. Upon disabling the PAF, the counter 1721 retains its previous value. 1723 If a Clause 45 MDIO Interface to the PCS is present, then 1724 this object maps to the 10P/2B PAF small fragments 1725 register. 1727 Discontinuities in the value of this counter can occur at 1728 re-initialization of the management system, and at other times 1729 as indicated by the value of ifCounterDiscontinuityTime, 1730 defined in IF-MIB." 1731 REFERENCE 1732 "[802.3ah] 45.2.3.22" 1733 ::= { efmCuPortStatusEntry 5 } 1735 efmCuPAFInLargeFragments OBJECT-TYPE 1736 SYNTAX Counter32 1737 MAX-ACCESS read-only 1738 STATUS current 1739 DESCRIPTION 1740 "A number of fragments larger than maxFragmentSize 1741 (512 Bytes), which have been received across the gamma 1742 interface and discarded. 1743 This read-only counter is inactive when the PAF is 1744 unsupported or disabled. Upon disabling the PAF, the counter 1745 retains its previous value. 1747 If a Clause 45 MDIO Interface to the PCS is present, then 1748 this object maps to the 10P/2B PAF large fragments 1749 register. 1751 Discontinuities in the value of this counter can occur at 1752 re-initialization of the management system, and at other times 1753 as indicated by the value of ifCounterDiscontinuityTime, 1754 defined in IF-MIB." 1755 REFERENCE 1756 "[802.3ah] 45.2.3.23" 1757 ::= { efmCuPortStatusEntry 6 } 1759 efmCuPAFInBadFragments OBJECT-TYPE 1760 SYNTAX Counter32 1761 MAX-ACCESS read-only 1762 STATUS current 1763 DESCRIPTION 1764 "A number of fragments which do not fit into the sequence 1765 expected by the frame assembly function, that have been 1766 received across the gamma interface and discarded (the 1767 frame buffer is flushed to the next valid frame start). 1768 This read-only counter is inactive when the PAF is 1769 unsupported or disabled. Upon disabling the PAF, the counter 1770 retains its previous value. 1772 If a Clause 45 MDIO Interface to the PCS is present, then 1773 this object maps to the 10P/2B PAF bad fragments 1774 register. 1776 Discontinuities in the value of this counter can occur at 1777 re-initialization of the management system, and at other times 1778 as indicated by the value of ifCounterDiscontinuityTime, 1779 defined in IF-MIB." 1780 REFERENCE 1781 "[802.3ah] 45.2.3.25" 1782 ::= { efmCuPortStatusEntry 7 } 1784 efmCuPAFInLostFragments OBJECT-TYPE 1785 SYNTAX Counter32 1786 MAX-ACCESS read-only 1787 STATUS current 1788 DESCRIPTION 1789 "A number of gaps in the sequence of fragments, which have 1790 been received across the gamma interface (the frame buffer is 1791 flushed to the next valid frame start, when fragment/fragments 1792 expected by the frame assembly function is/are not received). 1793 This read-only counter is inactive when the PAF is 1794 unsupported or disabled. Upon disabling the PAF, the counter 1795 retains its previous value. 1797 If a Clause 45 MDIO Interface to the PCS is present, then 1798 this object maps to the 10P/2B PAF lost fragment 1799 register. 1801 Discontinuities in the value of this counter can occur at 1802 re-initialization of the management system, and at other times 1803 as indicated by the value of ifCounterDiscontinuityTime, 1804 defined in IF-MIB." 1805 REFERENCE 1806 "[802.3ah] 45.2.3.26" 1807 ::= { efmCuPortStatusEntry 8 } 1809 efmCuPAFInLostStarts OBJECT-TYPE 1810 SYNTAX Counter32 1811 MAX-ACCESS read-only 1812 STATUS current 1813 DESCRIPTION 1814 "A number of missing StartOfPacket indicators expected by the 1815 frame assembly function. 1816 This read-only counter is inactive when the PAF is 1817 unsupported or disabled. Upon disabling the PAF, the counter 1818 retains its previous value. 1820 If a Clause 45 MDIO Interface to the PCS is present, then 1821 this object maps to the 10P/2B PAF lost start of fragment 1822 register. 1824 Discontinuities in the value of this counter can occur at 1825 re-initialization of the management system, and at other times 1826 as indicated by the value of ifCounterDiscontinuityTime, 1827 defined in IF-MIB." 1828 REFERENCE 1829 "[802.3ah] 45.2.3.27" 1830 ::= { efmCuPortStatusEntry 9 } 1832 efmCuPAFInLostEnds OBJECT-TYPE 1833 SYNTAX Counter32 1834 MAX-ACCESS read-only 1835 STATUS current 1836 DESCRIPTION 1837 "A number of missing EndOfPacket indicators expected by the 1838 frame assembly function. 1839 This read-only counter is inactive when the PAF is 1840 unsupported or disabled. Upon disabling the PAF, the counter 1841 retains its previous value. 1843 If a Clause 45 MDIO Interface to the PCS is present, then 1844 this object maps to the 10P/2B PAF lost start of fragment 1845 register. 1847 Discontinuities in the value of this counter can occur at 1848 re-initialization of the management system, and at other times 1849 as indicated by the value of ifCounterDiscontinuityTime, 1850 defined in IF-MIB." 1851 REFERENCE 1852 "[802.3ah] 45.2.3.28" 1853 ::= { efmCuPortStatusEntry 10 } 1855 efmCuPAFInOverflows OBJECT-TYPE 1856 SYNTAX Counter32 1857 MAX-ACCESS read-only 1858 STATUS current 1859 DESCRIPTION 1860 "A number of fragments, received across the gamma interface 1861 and discarded, which would have caused the frame assembly 1862 buffer to overflow. 1863 This read-only counter is inactive when the PAF is 1864 unsupported or disabled. Upon disabling the PAF, the counter 1865 retains its previous value. 1867 If a Clause 45 MDIO Interface to the PCS is present, then 1868 this object maps to the 10P/2B PAF overflow register. 1870 Discontinuities in the value of this counter can occur at 1871 re-initialization of the management system, and at other times 1872 as indicated by the value of ifCounterDiscontinuityTime, 1873 defined in IF-MIB." 1874 REFERENCE 1875 "[802.3ah] 45.2.3.24" 1876 ::= { efmCuPortStatusEntry 11 } 1878 -- PME Notifications Group 1880 efmCuPmeNotifications OBJECT IDENTIFIER ::= { efmCuPme 0 } 1882 efmCuPmeLineAtnCrossing NOTIFICATION-TYPE 1883 OBJECTS { 1884 efmCuPmeLineAtn, 1885 efmCuPmeThreshLineAtn 1886 } 1887 STATUS current 1888 DESCRIPTION 1889 "This notification indicates that the loop attenuation 1890 threshold (as per the efmCuPmeThreshLineAtn 1891 value) has been reached/exceeded for the 2BASE-TL/10PASS-TS 1892 PME. This notification MAY be send on the crossing event in 1893 both directions: from normal to exceeded and from exceeded 1894 to normal. 1896 It is RECOMMENDED that a small debouncing period of 2.5 sec, 1897 between the detection of the condition and notification, 1898 is implemented to prevent intermittent notifications to be 1899 sent. 1901 Generation of this notification is controlled by the 1902 efmCuPmeLineAtnCrossingEnable object." 1903 ::= { efmCuPmeNotifications 1 } 1905 efmCuPmeSnrMgnCrossing NOTIFICATION-TYPE 1906 OBJECTS { 1907 efmCuPmeSnrMgn, 1908 efmCuPmeThreshSnrMgn 1909 } 1910 STATUS current 1911 DESCRIPTION 1912 "This notification indicates that the SNR margin threshold 1913 (as per the efmCuPmeThreshSnrMgn value) has been 1914 reached/exceeded for the 2BASE-TL/10PASS-TS PME. 1915 This notification MAY be send on the crossing event in 1916 both directions: from normal to exceeded and from exceeded 1917 to normal. 1919 It is RECOMMENDED that a small debouncing period of 2.5 sec, 1920 between the detection of the condition and notification, 1921 is implemented to prevent intermittent notifications to be 1922 sent. 1924 Generation of this notification is controlled by the 1925 efmCuPmeSnrMgnCrossingEnable object." 1926 ::= { efmCuPmeNotifications 2 } 1928 efmCuPmeDeviceFault NOTIFICATION-TYPE 1929 OBJECTS { 1930 efmCuPmeFltStatus 1931 } 1932 STATUS current 1933 DESCRIPTION 1934 "This notification indicates that a fault in the PME has been 1935 detected by a vendor specific diagnostic or a self-test. 1937 Generation of this notification is controlled by the 1938 efmCuPmeDeviceFaultEnable object." 1939 ::= { efmCuPmeNotifications 3 } 1941 efmCuPmeConfigInitFailure NOTIFICATION-TYPE 1942 OBJECTS { 1943 efmCuPmeFltStatus, 1944 efmCuAdminProfile, 1945 efmCuPmeAdminProfile 1946 } 1947 STATUS current 1948 DESCRIPTION 1949 "This notification indicates that PME initialization has 1950 failed, due to inability of the PME link to achieve requested 1951 configuration profile. 1953 Generation of this notification is controlled by the 1954 efmCuPmeConfigInitFailEnable object." 1955 ::= { efmCuPmeNotifications 4 } 1957 efmCuPmeProtocolInitFailure NOTIFICATION-TYPE 1958 OBJECTS { 1959 efmCuPmeFltStatus, 1960 efmCuPmeOperSubType 1961 } 1962 STATUS current 1963 DESCRIPTION 1964 "This notification indicates that peer PME was using 1965 incompatible protocol during initialization. 1967 Generation of this notification is controlled by the 1968 efmCuPmeProtocolInitFailEnable object." 1969 ::= { efmCuPmeNotifications 5 } 1971 -- The PME group 1973 efmCuPmeConfTable OBJECT-TYPE 1974 SYNTAX SEQUENCE OF EfmCuPmeConfEntry 1975 MAX-ACCESS not-accessible 1976 STATUS current 1977 DESCRIPTION 1978 "Table for Configuration of common aspects for EFMCu 1979 2BASE-TL/10PASS-TS PME ports (modems). Configuration of 1980 aspects specific to 2BASE-TL or 10PASS-TS PME types is 1981 represented in efmCuPme2BConfTable and efmCuPme10PConfTable 1982 respectively. 1984 Entries in this table MUST be maintained in a persistent 1985 manner." 1986 ::= { efmCuPme 1 } 1988 efmCuPmeConfEntry OBJECT-TYPE 1989 SYNTAX EfmCuPmeConfEntry 1990 MAX-ACCESS not-accessible 1991 STATUS current 1992 DESCRIPTION 1993 "An entry in the EFMCu PME Configuration table. 1994 Each entry represents common aspects of an EFMCu PME port 1995 indexed by the ifIndex. Note that an EFMCu PME port can be 1996 stacked below a single PCS port, also indexed by ifIndex, 1997 possibly together with other PME ports if PAF is enabled." 1998 INDEX { ifIndex } 1999 ::= { efmCuPmeConfTable 1 } 2001 EfmCuPmeConfEntry ::= 2002 SEQUENCE { 2003 efmCuPmeAdminSubType INTEGER, 2004 efmCuPmeAdminProfile ProfileIndexOrZero, 2005 efmCuPAFRemoteDiscoveryCode PhysAddress, 2006 efmCuPmeThreshLineAtn Integer32, 2007 efmCuPmeThreshSnrMgn Integer32, 2008 efmCuPmeLineAtnCrossingEnable TruthValue, 2009 efmCuPmeSnrMgnCrossingEnable TruthValue, 2010 efmCuPmeDeviceFaultEnable TruthValue, 2011 efmCuPmeConfigInitFailEnable TruthValue, 2012 efmCuPmeProtocolInitFailEnable TruthValue 2013 } 2015 efmCuPmeAdminSubType OBJECT-TYPE 2016 SYNTAX INTEGER { 2017 ieee2BaseTLO(1), 2018 ieee2BaseTLR(2), 2019 ieee10PassTSO(3), 2020 ieee10PassTSR(4), 2021 ieee2BaseTLor10PassTSR(5), 2022 ieee2BaseTLor10PassTSO(6), 2023 ieee10PassTSor2BaseTLO(7) 2024 } 2025 MAX-ACCESS read-write 2026 STATUS current 2027 DESCRIPTION 2028 "Administrative (desired) sub-type of the PME. 2029 Possible values are: 2030 ieee2BaseTLO - PME SHALL operate as 2BaseTL-O 2031 ieee2BaseTLR - PME SHALL operate as 2BaseTL-R 2032 ieee10PassTSO - PME SHALL operate as 10PassTS-O 2033 ieee10PassTSR - PME SHALL operate as 10PassTS-R 2034 ieee2BaseTLor10PassTSR - PME SHALL operate as 2BaseTL-R or 2035 10PassTS-R. Actual value will be 2036 set by -O link partner during 2037 initialization (handshake). 2038 ieee2BaseTLor10PassTSO - PME SHALL operate as 2BaseTL-O 2039 (preferred) or 10PassTS-O. Actual 2040 value will be set during 2041 initialization depending on -R 2042 link partner capability (i.e. if 2043 -R is incapable of the preferred 2044 2BaseTL mode, 10PassTS will be 2045 used). 2046 ieee10PassTSor2BaseTLO - PME SHALL operate as 10PassTS-O 2047 (preferred) or 2BaseTL-O. Actual 2048 value will be set during 2049 initialization depending on -R 2050 link partner capability (i.e. if 2051 -R is incapable of the preferred 2052 10PassTS mode, 2BaseTL will be 2053 used). 2055 Changing efmCuPmeAdminSubType is a traffic disruptive 2056 operation and as such SHALL be done when the link is Down. 2057 Attempts to change this object SHALL be ignored if the link 2058 is Up or Initializing. 2059 Attempts to change this object to an unsupported subtype 2060 (see efmCuPmeSubTypesSupported) SHALL be rejected. 2062 The current operational sub type is indicated by 2063 efmCuPmeOperSubType variable. 2065 If a Clause 45 MDIO Interface to the PMA/PMD is present, then 2066 this object combines values of the Port sub-type select bits 2067 and the PMA/PMD type selection bits in the 10P/2B PMA/PMD 2068 control register" 2069 REFERENCE 2070 "[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7" 2071 ::= { efmCuPmeConfEntry 1 } 2073 efmCuPmeAdminProfile OBJECT-TYPE 2074 SYNTAX ProfileIndexOrZero 2075 MAX-ACCESS read-write 2076 STATUS current 2077 DESCRIPTION 2078 "Desired PME configuration Profile. This object is a pointer 2079 to an entry in either efmCuPme2BProfileTable or 2080 efmCuPme10PProfileTable, depending on the current operating 2081 SubType of the PME. The value of this object is the index of 2082 the referenced profile. 2083 The value of zero (default) indicates that the PME is 2084 configured via efmCuAdminProfile object for the PCS port, 2085 to which this PME is assigned. That is, the profile referenced 2086 by efmCuPmeAdminProfile takes precedence over the profile(s) 2087 referenced by efmCuAdminProfile. 2089 This object is writable and readable for the CO subtype PMEs 2090 (2BaseTL-O or 10PassTS-O). It is unavailable for the CPE 2091 subtype (2BaseTL-R or 10PassTS-R). 2093 Note that current operational Profile value is available via 2094 efmCuPmeOperProfile object. 2096 Modification of this object MUST be performed when the link is 2097 Down. Attempts to change this object MUST be rejected, if the 2098 link is Up or Initializing. 2099 Attempts to set this object to a value that is not the value 2100 of the index for an active entry in the corresponding profile 2101 table, MUST be rejected." 2102 REFERENCE 2103 "[802.3ah] 30.11.2.1.6" 2104 DEFVAL { 0 } 2105 ::= { efmCuPmeConfEntry 2 } 2107 efmCuPAFRemoteDiscoveryCode OBJECT-TYPE 2108 SYNTAX PhysAddress 2109 MAX-ACCESS read-write 2110 STATUS current 2111 DESCRIPTION 2112 "PAF Remote Discovery Code of the PME port at CO. 2113 A 6 Byte long Discovery Code of the peer PCS connected via 2114 the PME. 2115 Reading this object results in a Discovery Get operation. 2116 Writing a zero to this object results in a Discovery 2117 Clear_if_Same operation (the value of efmCuPAFDiscoveryCode 2118 at the peer PCS SHALL be the same as efmCuPAFDiscoveryCode of 2119 the local PCS associated with the PME for the operation to 2120 succeed). 2121 Writing a non-zero value to this object results in a 2122 Discovery Set_if_Clear operation. 2123 This object does not exist in CPE port subtypes. A zero length 2124 octet string SHALL be returned for CPE port subtypes and also 2125 when PAF aggregation is not enabled. 2127 Discovery MUST be performed when the link is Down. 2128 Attempts to change this object MUST be rejected with the error 2129 inconsistentValue, if the link is Up or Initializing. 2131 If a Clause 45 MDIO Interface to the PMA/PMD is present, then 2132 this object is a function of 10P/2B aggregation discovery 2133 control register, Discovery operation result bits in 10P/2B 2134 aggregation and discovery status register and 2135 10P/2B aggregation discovery code register" 2136 REFERENCE 2137 "[802.3ah] 61.2.2.8.4, 45.2.6.6-45.2.6.8" 2138 ::= { efmCuPmeConfEntry 3 } 2140 efmCuPmeThreshLineAtn OBJECT-TYPE 2141 SYNTAX Integer32(-127..128) 2142 UNITS "dB" 2143 MAX-ACCESS read-write 2144 STATUS current 2145 DESCRIPTION 2146 "Desired Line Attenuation Threshold for the 2B/10P PME. 2147 This object configures the line attenuation alarm threshold. 2148 When the current value of Line Attenuation reaches or 2149 exceeds this threshold, a efmCuPmeLineAtnCrossing 2150 notification MAY be generated, if enabled by 2151 efmCuPmeLineAtnCrossingEnable. 2153 This object is writable for the CO subtype PMEs (-O). 2154 It is read-only for the CPE subtype (-R). 2156 Changing of the Line Attenuation Threshold MUST be performed 2157 when the link is Down. Attempts to change this object MUST be 2158 rejected with the error inconsistentValue, if the link is Up 2159 or Initializing. 2161 If a Clause 45 MDIO Interface to the PME is present, then this 2162 object maps to the Loop attenuation threshold bits in 2163 the 2B PMD line quality thresholds register" 2164 REFERENCE 2165 "[802.3ah] 45.2.1.36" 2166 ::= { efmCuPmeConfEntry 4 } 2168 efmCuPmeThreshSnrMgn OBJECT-TYPE 2169 SYNTAX Integer32(-127..128) 2170 UNITS "dB" 2171 MAX-ACCESS read-write 2172 STATUS current 2173 DESCRIPTION 2174 "Desired SNR Margin Threshold for the 2B/10P PME. 2175 This object configures the SNR margin alarm threshold. 2176 When the current value of SNR Margin reaches or exceeds this 2177 threshold, a efmCuPmeSnrMgnCrossing notification MAY be 2178 generated, if enabled by efmCuPmeSnrMgnCrossingEnable. 2180 This object is writable for the CO subtype PMEs 2181 (2BaseTL-O/10PassTS-R). It is read-only for the CPE subtype 2182 (2BaseTL-R/10PassTS-R). 2184 Changing of the SNR Margin Threshold MUST be performed when 2185 the link is Down. Attempts to change this object MUST be 2186 rejected with the error inconsistentValue, if the link is Up 2187 or Initializing. 2189 If a Clause 45 MDIO Interface to the PME is present, then this 2190 object maps to the SNR margin threshold bits in the 2B PMD 2191 line quality thresholds register" 2192 REFERENCE 2193 "[802.3ah] 45.2.1.36" 2194 ::= { efmCuPmeConfEntry 5 } 2196 efmCuPmeLineAtnCrossingEnable OBJECT-TYPE 2197 SYNTAX TruthValue 2198 MAX-ACCESS read-write 2199 STATUS current 2200 DESCRIPTION 2201 "Indicates whether efmCuPmeLineAtnCrossing notifications 2202 should be generated for this interface. 2204 Value of true(1) indicates that efmCuPmeLineAtnCrossing 2205 notification is enabled. Value of false(2) indicates that 2206 the notification is disabled." 2207 ::= { efmCuPmeConfEntry 6 } 2209 efmCuPmeSnrMgnCrossingEnable OBJECT-TYPE 2210 SYNTAX TruthValue 2211 MAX-ACCESS read-write 2212 STATUS current 2213 DESCRIPTION 2214 "Indicates whether efmCuPmeSnrMgnCrossing notifications 2215 should be generated for this interface. 2217 Value of true(1) indicates that efmCuPmeSnrMgnCrossing 2218 notification is enabled. Value of false(2) indicates that 2219 the notification is disabled." 2220 ::= { efmCuPmeConfEntry 7 } 2222 efmCuPmeDeviceFaultEnable OBJECT-TYPE 2223 SYNTAX TruthValue 2224 MAX-ACCESS read-write 2225 STATUS current 2226 DESCRIPTION 2227 "Indicates whether efmCuPmeDeviceFault notifications 2228 should be generated for this interface. 2230 Value of true(1) indicates that efmCuPmeDeviceFault 2231 notification is enabled. Value of false(2) indicates that 2232 the notification is disabled." 2234 ::= { efmCuPmeConfEntry 8 } 2236 efmCuPmeConfigInitFailEnable OBJECT-TYPE 2237 SYNTAX TruthValue 2238 MAX-ACCESS read-write 2239 STATUS current 2240 DESCRIPTION 2241 "Indicates whether efmCuPmeConfigInitFailure notifications 2242 should be generated for this interface. 2244 Value of true(1) indicates that efmCuPmeConfigInitFailure 2245 notification is enabled. Value of false(2) indicates that 2246 the notification is disabled." 2247 ::= { efmCuPmeConfEntry 9 } 2249 efmCuPmeProtocolInitFailEnable OBJECT-TYPE 2250 SYNTAX TruthValue 2251 MAX-ACCESS read-write 2252 STATUS current 2253 DESCRIPTION 2254 "Indicates whether efmCuPmeProtocolInitFailure notifications 2255 should be generated for this interface. 2257 Value of true(1) indicates that efmCuPmeProtocolInitFailure 2258 notification is enabled. Value of false(2) indicates that 2259 the notification is disabled." 2260 ::= { efmCuPmeConfEntry 10 } 2262 efmCuPmeCapabilityTable OBJECT-TYPE 2263 SYNTAX SEQUENCE OF EfmCuPmeCapabilityEntry 2264 MAX-ACCESS not-accessible 2265 STATUS current 2266 DESCRIPTION 2267 "Table for Configuration of common aspects for EFMCu 2268 2BASE-TL/10PASS-TS PME ports (modems). Configuration of 2269 aspects specific to 2BASE-TL or 10PASS-TS PME types is 2270 represented in efmCuPme2BConfTable and efmCuPme10PConfTable 2271 respectively. 2273 Entries in this table MUST be maintained in a persistent 2274 manner." 2275 ::= { efmCuPme 2 } 2277 efmCuPmeCapabilityEntry OBJECT-TYPE 2278 SYNTAX EfmCuPmeCapabilityEntry 2279 MAX-ACCESS not-accessible 2280 STATUS current 2281 DESCRIPTION 2282 "An entry in the EFMCu PME Capability table. 2283 Each entry represents common aspects of an EFMCu PME port 2284 indexed by the ifIndex. Note that an EFMCu PME port can be 2285 stacked below a single PCS port, also indexed by ifIndex, 2286 possibly together with other PME ports if PAF is enabled." 2287 INDEX { ifIndex } 2288 ::= { efmCuPmeCapabilityTable 1 } 2290 EfmCuPmeCapabilityEntry ::= 2291 SEQUENCE { 2292 efmCuPmeSubTypesSupported BITS 2293 } 2295 efmCuPmeSubTypesSupported OBJECT-TYPE 2296 SYNTAX BITS { 2297 ieee2BaseTLO(0), 2298 ieee2BaseTLR(1), 2299 ieee10PassTSO(2), 2300 ieee10PassTSR(3) 2301 } 2302 MAX-ACCESS read-only 2303 STATUS current 2304 DESCRIPTION 2305 "PME supported sub-types. This is a bitmap of possible 2306 sub-types. The various bit positions are: 2307 ieee2BaseTLO - PME is capable of operating as 2BaseTL-O 2308 ieee2BaseTLR - PME is capable of operating as 2BaseTL-R 2309 ieee10PassTSO - PME is capable of operating as 10PassTS-O 2310 ieee10PassTSR - PME is capable of operating as 10PassTS-R 2312 An desired mode of operation is determined by 2313 efmCuPmeAdminSubType, while efmCuPmeOperSubType reflects the 2314 current operating mode. 2316 If a Clause 45 MDIO Interface to the PCS is present, then this 2317 object combines the 10PASS-TS capable and 2BASE-TL capable 2318 bits in the 10P/2B PMA/PMD speed ability register and the 2319 CO supported and CPE supported bits in the 10P/2B PMA/PMD 2320 status register" 2321 REFERENCE 2322 "[802.3ah] 61.1, 45.2.1.4.1, 45.2.1.4.2, 45.2.1.12.2, 2323 45.2.1.12.3" 2324 ::= { efmCuPmeCapabilityEntry 1 } 2326 efmCuPmeStatusTable OBJECT-TYPE 2327 SYNTAX SEQUENCE OF EfmCuPmeStatusEntry 2328 MAX-ACCESS not-accessible 2329 STATUS current 2330 DESCRIPTION 2331 "This table provides common status information of EFMCu 2332 2BASE-TL/10PASS-TS PME ports. Status information specific 2333 to 10PASS-TS PME is represented in efmCuPme10PStatusTable. 2335 This table contains live data from the equipment. As such, 2336 it is NOT persistent." 2337 ::= { efmCuPme 3 } 2339 efmCuPmeStatusEntry OBJECT-TYPE 2340 SYNTAX EfmCuPmeStatusEntry 2341 MAX-ACCESS not-accessible 2342 STATUS current 2343 DESCRIPTION 2344 "An entry in the EFMCu PME Status table. 2345 Each entry represents common aspects of an EFMCu PME port 2346 indexed by the ifIndex. Note that an EFMCu PME port can be 2347 stacked below a single PCS port, also indexed by ifIndex, 2348 possibly together with other PME ports if PAF is enabled." 2349 INDEX { ifIndex } 2350 ::= { efmCuPmeStatusTable 1 } 2352 EfmCuPmeStatusEntry ::= 2353 SEQUENCE { 2354 efmCuPmeOperStatus INTEGER, 2355 efmCuPmeFltStatus BITS, 2356 efmCuPmeOperSubType INTEGER, 2357 efmCuPmeOperProfile ProfileIndexOrZero, 2358 efmCuPmeSnrMgn Integer32, 2359 efmCuPmePeerSnrMgn Integer32, 2360 efmCuPmeLineAtn Integer32, 2361 efmCuPmePeerLineAtn Integer32, 2362 efmCuPmeEquivalentLength Unsigned32, 2363 efmCuPmeTCCodingErrors Counter32, 2364 efmCuPmeTCCrcErrors Counter32 2365 } 2367 efmCuPmeOperStatus OBJECT-TYPE 2368 SYNTAX INTEGER { 2369 up(1), 2370 downNotReady(2), 2371 downReady(3), 2372 init(4) 2373 } 2374 MAX-ACCESS read-only 2375 STATUS current 2376 DESCRIPTION 2377 "Current PME link Operational Status. Possible values are: 2378 up(1) - link is Up and ready to pass 64/65B 2379 encoded frames or fragments. 2380 downNotReady(2) - link is Down and the PME does not detect 2381 Handshake tones from its peer. This value 2382 may indicate a possible problem with 2383 the peer PME. 2384 downReady(3) - link is Down and the PME detects Handshake 2385 tones from its peer. 2386 init(4) - link is initializing, as a result of 2387 ifAdminStatus being set to 'up' for a 2388 particular PME or a PCS the PME is 2389 connected to. 2391 This object is intended to supplement Down state of 2392 ifOperStatus. 2394 This object partially maps to the Clause 30 attribute 2395 aPMEStatus. 2397 If a Clause 45 MDIO Interface to the PME is present, then this 2398 object partially maps to PMA/PMD link status bits in 10P/2B 2399 PMA/PMD status register." 2400 REFERENCE 2401 "[802.3ah] 30.11.2.1.3, 45.2.1.12.4" 2402 ::= { efmCuPmeStatusEntry 1 } 2404 efmCuPmeFltStatus OBJECT-TYPE 2405 SYNTAX BITS { 2406 lossOfFraming(0), 2407 snrMgnDefect(1), 2408 lineAtnDefect(2), 2409 deviceFault(3), 2410 configInitFailure(4), 2411 protocolInitFailure(5) 2412 } 2413 MAX-ACCESS read-only 2414 STATUS current 2415 DESCRIPTION 2416 "Current/Last PME link Fault Status. This is a bitmap of 2417 possible conditions. The various bit positions are: 2419 lossOfFraming - Loss of Framing for 10P or 2420 Loss of Sync word for 2B PMD or 2421 Loss of 64/65B Framing 2422 snrMgnDefect - SNR Margin dropped below the Threshold 2423 lineAtnDefect - Line Attenuation exceeds the Threshold 2424 deviceFault - Indicates a vendor-dependent 2425 diagnostic or self-test fault 2426 has been detected. 2427 configInitFailure - Configuration initialization failure, 2428 due to inability of the PME link to 2429 support configuration profile, 2430 requested during initialization. 2431 protocolInitFailure - Protocol initialization failure, 2432 due to incompatible protocol used by 2433 the Peer PME during init (that could 2434 happen if a peer PMD is a regular 2435 G.SDHSL/VDSL modem instead of a 2436 2BASE-TL/10PASS-TS PME). 2438 This object is intended to supplement ifOperStatus in IF-MIB. 2440 This object holds information about the last fault. 2441 efmCuPmeFltStatus is cleared by the device restart. 2442 In addition lossOfFraming, configInitFailure and 2443 protocolInitFailure are cleared by PME init. 2444 deviceFault is cleared by successful diagnostics/test. 2445 snrMgnDefect and lineAtnDefect are cleared by SNR Margin 2446 and line Attenuation respectively returning to norm and by 2447 PME init. 2449 This object partially maps to the Clause 30 attribute 2450 aPMEStatus. 2452 If a Clause 45 MDIO Interface to the PME is present, then this 2453 object consolidates information from various PMA/PMD 2454 registers, namely: Fault bit in PMA/PMD status 1 register, 2455 10P/2B PMA/PMD link loss register, 2456 10P outgoing indicator bits status register, 2457 10P incoming indicator bits status register, 2458 2B state defects register." 2459 REFERENCE 2460 "[802.3ah] 30.11.2.1.3, 45.2.1.2.1, 45.2.1.38, 2461 45.2.1.39, 45.2.1.54" 2462 ::= { efmCuPmeStatusEntry 2 } 2464 efmCuPmeOperSubType OBJECT-TYPE 2465 SYNTAX INTEGER { 2466 ieee2BaseTLO(1), 2467 ieee2BaseTLR(2), 2468 ieee10PassTSO(3), 2469 ieee10PassTSR(4) 2470 } 2471 MAX-ACCESS read-only 2472 STATUS current 2473 DESCRIPTION 2474 "Current operational sub-type of the PME. 2475 Possible values are: 2476 ieee2BaseTLO - PME operates as 2BaseTL-O 2477 ieee2BaseTLR - PME operates as 2BaseTL-R 2478 ieee10PassTSO - PME operates as 10PassTS-O 2479 ieee10PassTSR - PME operates as 10PassTS-R 2481 The operational sub type of the PME can be configured via 2482 efmCuPmeAdminSubType variable. 2484 If a Clause 45 MDIO Interface to the PMA/PMD is present, then 2485 this object combines values of the Port sub-type select 2486 bits, the PMA/PMD type selection bits in the 10P/2B 2487 PMA/PMD control register and the PMA/PMD link status bits in 2488 the 10P/2B PMA/PMD status register." 2489 REFERENCE 2490 "[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7, 45.2.1.12.4" 2491 ::= { efmCuPmeStatusEntry 3 } 2493 efmCuPmeOperProfile OBJECT-TYPE 2494 SYNTAX ProfileIndexOrZero 2495 MAX-ACCESS read-only 2496 STATUS current 2497 DESCRIPTION 2498 "PME current operating Profile. This object is a pointer to 2499 an entry in either efmCuPme2BProfileTable or 2500 efmCuPme10PProfileTable, depending on the current 2501 operating SubType of the PME as indicated by 2502 efmCuPmeOperSubType. 2503 Note that a profile entry, to which efmCuPmeOperProfile is 2504 pointing to, can be created automatically, to reflect achieved 2505 parameters in adaptive (not fixed) initialization, 2506 i.e. values of efmCuPmeOperProfile and efmCuAdminProfile or 2507 efmCuPmeAdminProfile MAY differ. 2508 The value of zero indicates that PME is down or initializing. 2510 This object partially maps to the aOperatingProfile 2511 attribute in Clause 30." 2512 REFERENCE 2513 "[802.3ah] 30.11.2.1.7" 2514 ::= { efmCuPmeStatusEntry 4 } 2516 efmCuPmeSnrMgn OBJECT-TYPE 2517 SYNTAX Integer32(-127..128|65535) 2518 UNITS "dB" 2519 MAX-ACCESS read-only 2520 STATUS current 2521 DESCRIPTION 2522 "The current Signal-to-Noise Ratio (SNR) margin with respect 2523 to the received signal as perceived by the local PME. 2524 The value of 65535 is returned when PME is down or 2525 initializing. 2527 This object maps to the aPMESNRMgn attribute in Clause 30. 2529 If a Clause 45 MDIO Interface is present, then this 2530 object maps to the 10P/2B RX SNR margin register." 2531 REFERENCE 2532 "[802.3ah] 30.11.2.1.4, 45.2.1.16" 2533 ::= { efmCuPmeStatusEntry 5 } 2535 efmCuPmePeerSnrMgn OBJECT-TYPE 2536 SYNTAX Integer32(-127..128|65535) 2537 UNITS "dB" 2538 MAX-ACCESS read-only 2539 STATUS current 2540 DESCRIPTION 2541 "The current SNR margin in dB with respect to the received 2542 signal, as perceived by the remote (link partner) PME. 2543 The value of 65535 is returned when PME is down or 2544 initializing. 2546 This object is not supported by -R PME subtypes. 2548 If a Clause 45 MDIO Interface is present, then this 2549 object maps to the 10P/2B link partner RX SNR margin 2550 register." 2551 REFERENCE 2552 "[802.3ah] 45.2.1.17" 2553 ::= { efmCuPmeStatusEntry 6} 2555 efmCuPmeLineAtn OBJECT-TYPE 2556 SYNTAX Integer32(-127..128|65535) 2557 UNITS "dB" 2558 MAX-ACCESS read-only 2559 STATUS current 2560 DESCRIPTION 2561 "The current Line Attenuation in dB as perceived by the local 2562 PME. 2563 The value of 65535 is returned when PME is down or 2564 initializing. 2566 If a Clause 45 MDIO Interface is present, then this 2567 object maps to the Line Attenuation register" 2569 REFERENCE 2570 "[802.3ah] 45.2.1.18" 2571 ::= { efmCuPmeStatusEntry 7 } 2573 efmCuPmePeerLineAtn OBJECT-TYPE 2574 SYNTAX Integer32(-127..128|65535) 2575 UNITS "dB" 2576 MAX-ACCESS read-only 2577 STATUS current 2578 DESCRIPTION 2579 "The current Line Attenuation in dB as perceived by the remote 2580 (link partner) PME. 2581 The value of 65535 is returned when PME is down or 2582 initializing. 2584 This object is not supported by CPE port subtypes. 2586 If a Clause 45 MDIO Interface is present, then this 2587 object maps to the 20P/2B link partner Line Attenuation 2588 register." 2589 REFERENCE 2590 "[802.3ah] 45.2.1.19" 2591 ::= { efmCuPmeStatusEntry 8 } 2593 efmCuPmeEquivalentLength OBJECT-TYPE 2594 SYNTAX Unsigned32(0..8192|65535) 2595 UNITS "m" 2596 MAX-ACCESS read-only 2597 STATUS current 2598 DESCRIPTION 2599 "An estimate of the equivalent loop's Physical Length in 2600 meters, as perceived by the PME after the link is established. 2601 An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a 2602 perfect square root attenuation characteristic, without any 2603 bridged taps. 2604 The value of 65535 is returned if the link is Down or 2605 Initializing or the PME is unable to estimate the Equivalent 2606 Length. 2608 For 10BASE-TL PME, if a Clause 45 MDIO Interface to the PME is 2609 present, then this object maps to the 10P Electrical Length 2610 register" 2611 REFERENCE 2612 "[802.3ah] 45.2.1.21" 2613 ::= { efmCuPmeStatusEntry 9 } 2615 efmCuPmeTCCodingErrors OBJECT-TYPE 2616 SYNTAX Counter32 2617 MAX-ACCESS read-only 2618 STATUS current 2619 DESCRIPTION 2620 "A number of 64/65-octet encapsulation errors. This counter is 2621 incremented for each 64/65-octet encapsulation error detected 2622 by the 64/65-octet receive function. 2624 This object maps to aTCCodingViolations attribute in 2625 clause 30. 2627 If a Clause 45 MDIO Interface to the PME TC is present, then 2628 this object maps to the TC coding violations register 2629 (see 45.2.6.12). 2631 Discontinuities in the value of this counter can occur at 2632 re-initialization of the management system, and at other times 2633 as indicated by the value of ifCounterDiscontinuityTime, 2634 defined in IF-MIB." 2635 REFERENCE 2636 "[802.3ah] 61.3.3.1, 30.11.2.1.5, 45.2.6.12" 2637 ::= { efmCuPmeStatusEntry 10 } 2639 efmCuPmeTCCrcErrors OBJECT-TYPE 2640 SYNTAX Counter32 2641 MAX-ACCESS read-only 2642 STATUS current 2643 DESCRIPTION 2644 "A number of TC-CRC errors. This counter is incremented for 2645 each TC-CRC error detected by the 64/65-octet receive function 2646 (see 61.3.3.3 and Figure 61-19). 2648 This object maps to aTCCRCErrors attribute in 2649 clause 30. 2651 If a Clause 45 MDIO Interface to the PCME TC is present, then 2652 this object maps to the TC CRC error register 2653 (see 45.2.6.11). 2655 Discontinuities in the value of this counter can occur at 2656 re-initialization of the management system, and at other times 2657 as indicated by the value of ifCounterDiscontinuityTime, 2658 defined in IF-MIB." 2659 REFERENCE 2660 "[802.3ah] 61.3.3.3, 30.11.2.1.10, 45.2.6.11" 2661 ::= { efmCuPmeStatusEntry 11 } 2663 -- 2BASE-TL specific PME group 2664 efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 } 2666 efmCuPme2BProfileTable OBJECT-TYPE 2667 SYNTAX SEQUENCE OF EfmCuPme2BProfileEntry 2668 MAX-ACCESS not-accessible 2669 STATUS current 2670 DESCRIPTION 2671 "This table supports definitions of administrative and 2672 operating Profiles for 2BASE-TL PMEs. 2673 First 14 entries in this table SHALL always be defined as 2674 follows (see 802.3ah Annex 63A): 2675 -------+-------+-------+-----+------+------------------ 2676 Profile MinRate MaxRate Power Region Constellation 2677 index (Kbps) (Kbps) (dBm) 2678 -------+-------+-------+-----+------+------------------ 2679 1 5696 5696 13.5 1 32-TCPAM (default) 2680 2 3072 3072 13.5 1 32-TCPAM 2681 3 2048 2048 13.5 1 16-TCPAM 2682 4 1024 1024 13.5 1 16-TCPAM 2683 5 704 704 13.5 1 16-TCPAM 2684 6 512 512 13.5 1 16-TCPAM 2685 7 5696 5696 14.5 2 32-TCPAM 2686 8 3072 3072 14.5 2 32-TCPAM 2687 9 2048 2048 14.5 2 16-TCPAM 2688 10 1024 1024 13.5 2 16-TCPAM 2689 11 704 704 13.5 2 16-TCPAM 2690 12 512 512 13.5 2 16-TCPAM 2691 13 192 5696 0 1 0 (best effort) 2692 14 192 5696 0 2 0 (best effort) 2694 These default entries SHALL be created during agent 2695 initialization and MUST NOT be deleted. 2697 Entries following the first 14, can be dynamically created and 2698 deleted, to provide custom administrative (configuration) 2699 profiles and automatic operating profiles. 2701 This table MUST be maintained in a persistent manner." 2702 REFERENCE 2703 "[802.3ah] Annex 63A, 30.11.2.1.6" 2704 ::= { efmCuPme2B 2 } 2706 efmCuPme2BProfileEntry OBJECT-TYPE 2707 SYNTAX EfmCuPme2BProfileEntry 2708 MAX-ACCESS not-accessible 2709 STATUS current 2710 DESCRIPTION 2711 "Each entry corresponds to a single 2BASE-TL PME profile. 2713 Each profile contains a set of parameters, used either for 2714 configuration or representation of a 2BASE-TL PME. 2715 In case a particular profile is referenced via 2716 efmCuPmeAdminProfile object (or efmCuAdminProfile if 2717 efmCuPmeAdminProfile is zero), it represent the desired 2718 parameters the 2BaseTL-O PME initialization. 2719 If a profile is referenced via efmCuPmeOperProfile object, 2720 it represents current operating parameters of the 2721 operational PME. 2723 Profiles may be created/deleted using the row creation/ 2724 deletion mechanism via efmCuPme2BProfileRowStatus. If an 2725 active entry is referenced, the entry MUST remain 'active' 2726 until all references are removed. 2727 Default entries MUST NOT be removed." 2728 INDEX { efmCuPme2BProfileIndex } 2729 ::= { efmCuPme2BProfileTable 1 } 2731 EfmCuPme2BProfileEntry ::= 2732 SEQUENCE { 2733 efmCuPme2BProfileIndex ProfileIndex, 2734 efmCuPme2BProfileDescr SnmpAdminString, 2735 efmCuPme2BRegion INTEGER, 2736 efmCuPme2BsMode ProfileIndexOrZero, 2737 efmCuPme2BMinDataRate Unsigned32, 2738 efmCuPme2BMaxDataRate Unsigned32, 2739 efmCuPme2BPower Unsigned32, 2740 efmCuPme2BConstellation INTEGER, 2741 efmCuPme2BProfileRowStatus RowStatus 2742 } 2744 efmCuPme2BProfileIndex OBJECT-TYPE 2745 SYNTAX ProfileIndex 2746 MAX-ACCESS not-accessible 2747 STATUS current 2748 DESCRIPTION 2749 "2BASE-TL PME Profile index. 2750 This object is the unique index associated with this profile. 2751 Entries in this table are referenced via efmCuAdminProfile 2752 or efmCuPmeAdminProfile objects." 2753 ::= { efmCuPme2BProfileEntry 1 } 2755 efmCuPme2BProfileDescr OBJECT-TYPE 2756 SYNTAX SnmpAdminString 2757 MAX-ACCESS read-create 2758 STATUS current 2759 DESCRIPTION 2760 "A textual string containing information about 2BASE-TL PME 2761 Profile. The string MAY include information about data rate 2762 and spectral limitations of this particular profile." 2763 ::= { efmCuPme2BProfileEntry 2 } 2765 efmCuPme2BRegion OBJECT-TYPE 2766 SYNTAX INTEGER { 2767 region1(1), 2768 region2(2) 2769 } 2770 MAX-ACCESS read-create 2771 STATUS current 2772 DESCRIPTION 2773 "Regional settings for 2BASE-TL PME, as specified in the 2774 relevant Regional Annex of [G.991.2]. 2775 Regional settings specify Power Spectral Density (PSD) mask, 2776 Power Back-Off (PBO) values and place limitations on the max 2777 allowed data rate, power and constellation. 2779 Possible values for this object are: 2780 region1 - Annexes A and F (e.g. North America) 2781 region2 - Annexes B and G (e.g. Europe) 2783 Annex A/B specify regional settings for data rates 192-2304 2784 Kbps using 16-TCPAM encoding. 2785 Annex F/G specify regional settings for rates 2320-3840 Kbps 2786 using 16-TCPAM encoding and 768-5696 Kbps using 32-TCPAM 2787 encoding. 2789 If a Clause 45 MDIO Interface to the PME is present, then this 2790 object partially maps to the Region bits in the 2B general 2791 parameter register." 2792 REFERENCE 2793 "[802.3ah] 45.2.1.42; [G.991.2] Annexes A, B, F and G" 2794 ::= { efmCuPme2BProfileEntry 3 } 2796 efmCuPme2BsMode OBJECT-TYPE 2797 SYNTAX ProfileIndexOrZero 2798 MAX-ACCESS read-create 2799 STATUS current 2800 DESCRIPTION 2801 "Desired custom Spectral Mode for 2BASE-TL PME. This object 2802 is a pointer to an entry in efmCuPme2BsModeTable and a block 2803 of entries in efmCuPme2BRateReachTable, which together define 2804 (country-specific) reach dependent rate limitations in 2805 addition to those defined by efmCuPme2BRegion. 2807 The value of this object is the index of the referenced 2808 spectral mode. 2810 The value of zero (default) indicates that no specific 2811 spectral mode is applicable. 2813 Attempts to set this object to a value that is not the value 2814 of the index for an active entry in the corresponding spectral 2815 mode table, MUST be rejected." 2816 REFERENCE 2817 "efmCuPme2BsModeTable, efmCuPme2BRateReachTable" 2818 DEFVAL { 0 } 2819 ::= { efmCuPme2BProfileEntry 4 } 2821 efmCuPme2BMinDataRate OBJECT-TYPE 2822 SYNTAX Unsigned32(192..5696) 2823 UNITS "Kbps" 2824 MAX-ACCESS read-create 2825 STATUS current 2826 DESCRIPTION 2827 "Minimum Data Rate for the 2BASE-TL PME. 2828 This object can take values of (n x 64)Kbps, 2829 where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM encoding. 2831 The data rate of the 2BASE-TL PME is considered 'fixed' when 2832 the value of this object equals that of efmCuPme2BMaxDataRate. 2833 If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in 2834 the administrative profile, the data rate is considered 2835 'adaptive', and SHALL be set to the maximum attainable rate 2836 not exceeding efmCuPme2BMaxDataRate, under the spectral 2837 limitations placed by the efmCuPme2BRegion and 2838 efmCuPme2BsMode. 2840 Note that current operational data rate of the PME is 2841 represented by ifSpeed object of IF-MIB. 2843 If a Clause 45 MDIO Interface to the PME is present, then this 2844 object maps to the Min Data Rate1 bits in the 2B PMD 2845 parameters register. 2847 This object MUST be maintained in a persistent manner." 2848 REFERENCE 2849 "[802.3ah] 45.2.1.43" 2850 ::= { efmCuPme2BProfileEntry 5 } 2852 efmCuPme2BMaxDataRate OBJECT-TYPE 2853 SYNTAX Unsigned32(192..5696) 2854 UNITS "Kbps" 2855 MAX-ACCESS read-create 2856 STATUS current 2857 DESCRIPTION 2858 "Maximum Data Rate for the 2BASE-TL PME. 2859 This object can take values of (n x 64)Kbps, 2860 where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM encoding. 2862 The data rate of the 2BASE-TL PME is considered 'fixed' when 2863 the value of this object equals that of efmCuPme2BMinDataRate. 2864 If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in 2865 the administrative profile, the data rate is considered 2866 'adaptive', and SHALL be set to the maximum attainable rate 2867 not exceeding efmCuPme2BMaxDataRate, under the spectral 2868 limitations placed by the efmCuPme2BRegion and 2869 efmCuPme2BsMode. 2871 Note that current operational data rate of the PME is 2872 represented by ifSpeed object of IF-MIB. 2874 If a Clause 45 MDIO Interface to the PME is present, then this 2875 object maps to the Max Data Rate1 bits in the 2B PMD 2876 parameters register. 2878 This object MUST be maintained in a persistent manner." 2879 REFERENCE 2880 "[802.3ah] 45.2.1.43" 2881 ::= { efmCuPme2BProfileEntry 6 } 2883 efmCuPme2BPower OBJECT-TYPE 2884 SYNTAX Unsigned32(0|10..42) 2885 UNITS "0.5 dBm" 2886 MAX-ACCESS read-create 2887 STATUS current 2888 DESCRIPTION 2889 "Signal Transmit Power. Multiple of 0.5dBm. 2890 The value of 0 in the administrative profile means that the 2891 signal transmit power is not fixed and SHALL be set to 2892 maximize the attainable rate, under the spectral limitations 2893 placed by the efmCuPme2BRegion and efmCuPme2BsMode. 2895 If a Clause 45 MDIO Interface to the PME is present, then this 2896 object maps to the Power1 bits in the 2B PMD parameters 2897 register" 2898 REFERENCE 2899 "[802.3ah] 45.2.1.43" 2900 ::= { efmCuPme2BProfileEntry 7 } 2902 efmCuPme2BConstellation OBJECT-TYPE 2903 SYNTAX INTEGER { 2904 adaptive(0), 2905 tcpam16(1), 2906 tcpam32(2) 2907 } 2908 MAX-ACCESS read-create 2909 STATUS current 2910 DESCRIPTION 2911 "TCPAM Constellation of the 2BASE-TL PME. 2912 The possible values are: 2913 adaptive(0) - either 16- or 32-TCPAM 2914 tcpam16(1) - 16-TCPAM 2915 tcpam32(2) - 32-TCPAM 2917 The value of adaptive(0) in the administrative profile means 2918 that the constellation is not fixed and SHALL be set to 2919 maximize the attainable rate, under the spectral limitations 2920 placed by the efmCuPme2BRegion and efmCuPme2BsMode. 2922 If a Clause 45 MDIO Interface to the PME is present, then this 2923 object maps to the Constellation1 bits in the 2B general 2924 parameter register." 2925 REFERENCE 2926 "[802.3ah] 45.2.1.43" 2927 ::= { efmCuPme2BProfileEntry 8 } 2929 efmCuPme2BProfileRowStatus OBJECT-TYPE 2930 SYNTAX RowStatus 2931 MAX-ACCESS read-create 2932 STATUS current 2933 DESCRIPTION 2934 "This object controls creation/deletion of the associated 2935 entry in efmCuPme2BProfileTable per the semantics of 2936 RowStatus. 2937 If an 'active' entry is referenced via efmCuAdminProfile or 2938 efmCuPmeAdminProfile, the entry MUST remain 'active' until all 2939 references are removed." 2940 ::= { efmCuPme2BProfileEntry 9 } 2942 efmCuPme2BsModeTable OBJECT-TYPE 2943 SYNTAX SEQUENCE OF EfmCuPme2BsModeEntry 2944 MAX-ACCESS not-accessible 2945 STATUS current 2946 DESCRIPTION 2947 "This table, together with efmCu2BReachRateTable, supports 2948 definition of administrative custom spectral modes for 2949 2BASE-TL PMEs, describing spectral limitations in addition to 2950 those specified by efmCuPme2BRegion. 2952 Some countries spectral regulations (e.g. UK ANFP) limit the 2953 length of the loops for certain data rates. This table allows 2954 these country-specific limitations to be specified. 2956 Entries in this table referenced by the efmCuPme2BsMode 2957 MUST NOT be deleted until all the active references are 2958 removed. 2960 This table MUST be maintained in a persistent manner." 2961 REFERENCE 2962 "efmCu2BReachRateTable" 2963 ::= { efmCuPme2B 3 } 2965 efmCuPme2BsModeEntry OBJECT-TYPE 2966 SYNTAX EfmCuPme2BsModeEntry 2967 MAX-ACCESS not-accessible 2968 STATUS current 2969 DESCRIPTION 2970 "Each entry specifies spectral mode description and its index, 2971 which is used to reference corresponding entries in the 2972 efmCu2BReachRateTable. 2974 Entries may be created/deleted using the row creation/ 2975 deletion mechanism via efmCuPme2BsModeRowStatus." 2976 INDEX { efmCuPme2BsModeIndex } 2977 ::= { efmCuPme2BsModeTable 1 } 2979 EfmCuPme2BsModeEntry ::= 2980 SEQUENCE { 2981 efmCuPme2BsModeIndex ProfileIndex, 2982 efmCuPme2BsModeDescr SnmpAdminString, 2983 efmCuPme2BsModeRowStatus RowStatus 2984 } 2986 efmCuPme2BsModeIndex OBJECT-TYPE 2987 SYNTAX ProfileIndex 2988 MAX-ACCESS not-accessible 2989 STATUS current 2990 DESCRIPTION 2991 "2BASE-TL PME Spectral Mode index. 2992 This object is the unique index associated with this spectral 2993 mode. 2994 Entries in this table are referenced via efmCuPme2BsMode 2995 object." 2996 ::= { efmCuPme2BsModeEntry 1 } 2998 efmCuPme2BsModeDescr OBJECT-TYPE 2999 SYNTAX SnmpAdminString 3000 MAX-ACCESS read-create 3001 STATUS current 3002 DESCRIPTION 3003 "A textual string containing information about 2BASE-TL PME 3004 spectral mode. The string MAY include information about 3005 corresponding (country-specific) spectral regulations 3006 and rate/reach limitations of this particular spectral mode." 3007 ::= { efmCuPme2BsModeEntry 2 } 3009 efmCuPme2BsModeRowStatus OBJECT-TYPE 3010 SYNTAX RowStatus 3011 MAX-ACCESS read-create 3012 STATUS current 3013 DESCRIPTION 3014 "This object controls creation/deletion of the associated 3015 entry in efmCuPme2BsModeTable per the semantics of 3016 RowStatus. 3017 If an 'active' entry is referenced via efmCuPme2BsMode, the 3018 entry MUST remain 'active' until all references are removed." 3019 ::= { efmCuPme2BsModeEntry 3 } 3021 efmCuPme2BReachRateTable OBJECT-TYPE 3022 SYNTAX SEQUENCE OF EfmCuPme2BReachRateEntry 3023 MAX-ACCESS not-accessible 3024 STATUS current 3025 DESCRIPTION 3026 "This table supports definition of administrative custom 3027 spectral modes for 2BASE-TL PMEs, providing spectral 3028 limitations in addition to those specified by 3029 efmCuPme2BRegion. 3031 The spectral regulations in some countries (e.g. UK ANFP) 3032 limit the length of the loops for certain data rates. 3033 This table allows these country-specific limitations to be 3034 specified. 3036 Below is an example of this table for [ANFP]: 3037 ----------+-------+-------+ 3038 Equivalent MaxRate MaxRate 3039 Length PAM16 PAM32 3040 (m) (Kbps) (Kbps) 3041 ----------+-------+-------+ 3042 975 2304 5696 3043 1125 2304 5504 3044 1275 2304 5120 3045 1350 2304 4864 3046 1425 2304 4544 3047 1500 2304 4288 3048 1575 2304 3968 3049 1650 2304 3776 3050 1725 2304 3520 3051 1800 2304 3264 3052 1875 2304 3072 3053 1950 2048 2688 3054 2100 1792 2368 3055 2250 1536 0 3056 2400 1408 0 3057 2550 1280 0 3058 2775 1152 0 3059 2925 1152 0 3060 3150 1088 0 3061 3375 1024 0 3062 ----------+-------+-------+ 3064 Entries in this table referenced by the efmCuPme2BsMode 3065 MUST NOT be deleted until all the active references are 3066 removed. 3068 This table MUST be maintained in a persistent manner." 3069 REFERENCE 3070 "[ANFP]" 3071 ::= { efmCuPme2B 4 } 3073 efmCuPme2BReachRateEntry OBJECT-TYPE 3074 SYNTAX EfmCuPme2BReachRateEntry 3075 MAX-ACCESS not-accessible 3076 STATUS current 3077 DESCRIPTION 3078 "Each entry specifies maximum 2BASE-TL PME data rates 3079 allowed for a certain equivalent loop length, when using 3080 16-TCPAM or 32-TCPAM encoding. 3082 When 2BASE-TL PME is initialized, its data rate MUST NOT 3083 exceed one of the following limitations: 3084 - the value of efmCuPme2BMaxDataRate 3085 - maximum data rate allowed by efmCuPme2BRegion and 3086 efmCuPme2BPower 3087 - maximum data rate for a given encoding specified in the 3088 efmCuPme2BsModeEntry, corresponding to the equivalent loop 3089 length, estimated by the PME. 3091 It is RECOMMENDED that the efmCuPme2BEquivalentLength values 3092 are assigned in the increasing order, starting from the 3093 minimum value. 3095 Entries may be created/deleted using the row creation/ 3096 deletion mechanism via efmCuPme2ReachRateRowStatus." 3097 INDEX { efmCuPme2BsModeIndex, efmCuPme2BReachRateIndex } 3098 ::= { efmCuPme2BReachRateTable 1 } 3100 EfmCuPme2BReachRateEntry ::= 3101 SEQUENCE { 3102 efmCuPme2BReachRateIndex ProfileIndex, 3103 efmCuPme2BEquivalentLength Unsigned32, 3104 efmCuPme2BMaxDataRatePam16 Unsigned32, 3105 efmCuPme2BMaxDataRatePam32 Unsigned32, 3106 efmCuPme2BReachRateRowStatus RowStatus 3107 } 3109 efmCuPme2BReachRateIndex OBJECT-TYPE 3110 SYNTAX ProfileIndex 3111 MAX-ACCESS not-accessible 3112 STATUS current 3113 DESCRIPTION 3114 "2BASE-TL custom spectral mode Reach-Rate table index. 3115 This object is the unique index associated with each enry." 3116 ::= { efmCuPme2BReachRateEntry 1 } 3118 efmCuPme2BEquivalentLength OBJECT-TYPE 3119 SYNTAX Unsigned32(0..8192) 3120 UNITS "m" 3121 MAX-ACCESS read-create 3122 STATUS current 3123 DESCRIPTION 3124 "Maximum allowed Equivalent loop's Physical Length in meters 3125 for the specified data rates. 3126 An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a 3127 perfect square root attenuation characteristic, without any 3128 bridged taps." 3129 ::= { efmCuPme2BReachRateEntry 2 } 3131 efmCuPme2BMaxDataRatePam16 OBJECT-TYPE 3132 SYNTAX Unsigned32(0|192..5696) 3133 UNITS "Kbps" 3134 MAX-ACCESS read-create 3135 STATUS current 3136 DESCRIPTION 3137 "Maximum data rate for 2BASE-TL PME at the specified 3138 Equivalent loop's Length using TC-PAM16 encoding. 3139 The value of zero means that TC-PAM16 encoding should not be 3140 used at this distance." 3141 ::= { efmCuPme2BReachRateEntry 3 } 3143 efmCuPme2BMaxDataRatePam32 OBJECT-TYPE 3144 SYNTAX Unsigned32(0|192..5696) 3145 UNITS "Kbps" 3146 MAX-ACCESS read-create 3147 STATUS current 3148 DESCRIPTION 3149 "Maximum data rate for 2BASE-TL PME at the specified 3150 Equivalent loop's Length using TC-PAM32 encoding. 3151 The value of zero means that TC-PAM32 encoding should not be 3152 used at this distance." 3153 ::= { efmCuPme2BReachRateEntry 4 } 3155 efmCuPme2BReachRateRowStatus OBJECT-TYPE 3156 SYNTAX RowStatus 3157 MAX-ACCESS read-create 3158 STATUS current 3159 DESCRIPTION 3160 "This object controls creation/deletion of the associated 3161 entry in efmCuPme2BReachRateTable per the semantics of 3162 RowStatus. 3163 If an 'active' entry is referenced via efmCuPme2BsMode, the 3164 entry MUST remain 'active' until all references are removed." 3165 ::= { efmCuPme2BReachRateEntry 5 } 3167 -- 10PASS-TS specific PME group 3169 efmCuPme10P OBJECT IDENTIFIER ::= { efmCuPme 6 } 3171 efmCuPme10PProfileTable OBJECT-TYPE 3172 SYNTAX SEQUENCE OF EfmCuPme10PProfileEntry 3173 MAX-ACCESS not-accessible 3174 STATUS current 3175 DESCRIPTION 3176 "This table supports definitions of configuration profiles for 3177 10PassTL PMEs. 3178 First 22 entries in this table SHALL always be defined as 3179 follows (see 802.3ah Annex 62B.3): 3180 -------+--------+----+---------+-----+------------ 3181 Profile Bandplan UPBO BandNotch DRate URate 3182 Index PSDMask# p# p# p# p# 3183 -------+--------+----+---------+-----+------------ 3184 1 1 3 2,6,10,11 20 20(default) 3185 2 13 5 0 20 20 3186 3 1 1 0 20 20 3187 4 16 0 0 100 100 3188 5 16 0 0 70 50 3189 6 6 0 0 50 10 3190 7 17 0 0 30 30 3191 8 8 0 0 30 5 3192 9 4 0 0 25 25 3193 10 4 0 0 15 15 3194 11 23 0 0 10 10 3195 12 23 0 0 5 5 3196 13 16 0 2,5,9,11 100 100 3197 14 16 0 2,5,9,11 70 50 3198 15 6 0 2,6,10,11 50 10 3199 16 17 0 2,5,9,11 30 30 3200 17 8 0 2,6,10,11 30 5 3201 18 4 0 2,6,10,11 25 25 3202 19 4 0 2,6,10,11 15 15 3203 20 23 0 2,5,9,11 10 10 3204 21 23 0 2,5,9,11 5 5 3205 22 30 0 0 200 50 3207 These default entries SHALL be created by during agent 3208 initialization and MUST NOT be deleted. 3210 Entries following the first 22, can be dynamically created and 3211 deleted, to provide custom administrative (configuration) 3212 profiles and automatic operating profiles. 3214 This table MUST be maintained in a persistent manner." 3215 REFERENCE 3216 "[802.3ah] Annex 62B.3, 30.11.2.1.6" 3217 ::= { efmCuPme10P 1 } 3219 efmCuPme10PProfileEntry OBJECT-TYPE 3220 SYNTAX EfmCuPme10PProfileEntry 3221 MAX-ACCESS not-accessible 3222 STATUS current 3223 DESCRIPTION 3224 "Each entry corresponds to a single 10PASS-TS PME 3225 profile. 3226 Each profile contains a set of parameters, used either for 3227 configuration or representation of a 10PASS-TS PME. 3228 In case a particular profile is referenced via 3229 efmCuPmeAdminProfile object (or efmCuAdminProfile if 3230 efmCuPmeAdminProfile is zero), it represent the desired 3231 parameters the 10PassTS-O PME initialization. 3232 If a profile is referenced via efmCuPmeOperProfile object, 3233 it represents current operating parameters of the PME. 3235 Profiles may be created/deleted using the row creation/ 3236 deletion mechanism via efmCuPme10PProfileRowStatus. If an 3237 'active' entry is referenced, the entry MUST remain 'active' 3238 until all references are removed. 3240 Default entries MUST NOT be removed." 3241 INDEX { efmCuPme10PProfileIndex } 3242 ::= { efmCuPme10PProfileTable 1 } 3244 EfmCuPme10PProfileEntry ::= 3245 SEQUENCE { 3246 efmCuPme10PProfileIndex ProfileIndex, 3247 efmCuPme10PProfileDescr SnmpAdminString, 3248 efmCuPme10PBandplanPSDMskProfile INTEGER, 3249 efmCuPme10PUPBOReferenceProfile INTEGER, 3250 efmCuPme10PBandNotchProfiles BITS, 3251 efmCuPme10PPayloadURateProfile INTEGER, 3252 efmCuPme10PPayloadDRateProfile INTEGER, 3253 efmCuPme10PProfileRowStatus RowStatus 3254 } 3256 efmCuPme10PProfileIndex OBJECT-TYPE 3257 SYNTAX ProfileIndex 3258 MAX-ACCESS not-accessible 3259 STATUS current 3260 DESCRIPTION 3261 "10PASS-TS PME Profile Index. 3262 This object is the unique index associated with this profile. 3263 Entries in this table are referenced via efmCuAdminProfile or 3264 efmCuPmeAdminProfile." 3265 ::= { efmCuPme10PProfileEntry 1 } 3267 efmCuPme10PProfileDescr OBJECT-TYPE 3268 SYNTAX SnmpAdminString 3269 MAX-ACCESS read-create 3270 STATUS current 3271 DESCRIPTION 3272 "A textual string containing information about 10PASS-TS PME 3273 Profile. The string MAY include information about data rate 3274 and spectral limitations of this particular profile." 3275 ::= { efmCuPme10PProfileEntry 2 } 3277 efmCuPme10PBandplanPSDMskProfile OBJECT-TYPE 3278 SYNTAX INTEGER { 3279 profile1(1), 3280 profile2(2), 3281 profile3(3), 3282 profile4(4), 3283 profile5(5), 3284 profile6(6), 3285 profile7(7), 3286 profile8(8), 3287 profile9(9), 3288 profile10(10), 3289 profile11(11), 3290 profile12(12), 3291 profile13(13), 3292 profile14(14), 3293 profile15(15), 3294 profile16(16), 3295 profile17(17), 3296 profile18(18), 3297 profile19(19), 3298 profile20(20), 3299 profile21(21), 3300 profile22(22), 3301 profile23(23), 3302 profile24(24), 3303 profile25(25), 3304 profile26(26), 3305 profile27(27), 3306 profile28(28), 3307 profile29(29) 3308 } 3309 MAX-ACCESS read-create 3310 STATUS current 3311 DESCRIPTION 3312 "10PASS-TS PME Bandplan and PSD Mask profile, 3313 as specified in 802.3ah Annex 62A. Possible values are: 3314 --------------+------------------------+-----------+--------- 3315 Profile Name PSD Mask Bands Bandplan 3316 --------------+------------------------+-----------+--------- 3317 profile1(1) - T1.424/T-U P1 FTTCab.M1 x/D/U/D/U A 3318 profile2(2) - T1.424/T-U P1 FTTEx.M1 3319 profile3(3) - T1.424/T-U P1 FTTCab.M2 3320 profile4(4) - T1.424/T-U P1 FTTEx.M2 3321 profile5(5) - T1.424/T-U P1 FTTCab.M1 D/D/U/D/U 3322 profile6(6) - T1.424/T-U P1 FTTEx.M1 3323 profile7(7) - T1.424/T-U P1 FTTCab.M2 3324 profile8(8) - T1.424/T-U P1 FTTEx.M2 3325 profile9(9) - T1.424/T-U P1 FTTCab.M1 U/D/U/D/x 3326 profile10(10) - T1.424/T-U P1 FTTEx.M1 3327 profile11(11) - T1.424/T-U P1 FTTCab.M2 3328 profile12(12) - T1.424/T-U P1 FTTEx.M2 3329 profile13(13) - TS1 101 270-1 Pcab.M1.A x/D/U/D/U B 3330 profile14(14) - TS1 101 270-1 Pcab.M1.B 3331 profile15(15) - TS1 101 270-1 Pex.P1.M1 3332 profile16(16) - TS1 101 270-1 Pex.P2.M1 3333 profile17(17) - TS1 101 270-1 Pcab.M2 3334 profile18(18) - TS1 101 270-1 Pex.P1.M2 3335 profile19(19) - TS1 101 270-1 Pex.P2.M2 3336 profile20(20) - TS1 101 270-1 Pcab.M1.A U/D/U/D/x 3337 profile21(21) - TS1 101 270-1 Pcab.M1.B 3338 profile22(22) - TS1 101 270-1 Pex.P1.M1 3339 profile23(23) - TS1 101 270-1 Pex.P2.M1 3340 profile24(24) - TS1 101 270-1 Pcab.M2 3341 profile25(25) - TS1 101 270-1 Pex.P1.M2 3342 profile26(26) - TS1 101 270-1 Pex.P2.M2 3343 profile27(27) - G.993.1 F.1.2.1 (VDSLoPOTS) x/D/U/D/U F 3344 profile28(28) - G.993.1 F.1.2.2 (VDSLoTCM-ISDN) 3345 profile29(29) - G.993.1 F.1.2.3 (PSD reduction) 3347 This object maps to the aBandplanPSDMaskProfile attribute 3348 in Clause 30." 3349 REFERENCE 3350 "[802.3ah] Annex 62A, 30.5.1.1.22" 3351 ::= { efmCuPme10PProfileEntry 3 } 3353 efmCuPme10PUPBOReferenceProfile OBJECT-TYPE 3354 SYNTAX INTEGER { 3355 profile1(1), 3356 profile2(2), 3357 profile3(3), 3358 profile4(4), 3359 profile5(5), 3360 profile6(6), 3361 profile7(7), 3362 profile8(8), 3363 profile9(9) 3364 } 3365 MAX-ACCESS read-create 3366 STATUS current 3367 DESCRIPTION 3368 "10PASS-TS PME Upstream Power Back-Off (UPBO) Reference PSD 3369 Profile, as specified in 802.3ah Annex 62A. Possible values 3370 are: 3371 profile1(1) - T1.424/T-U Noise A M1 3372 profile2(2) - T1.424/T-U Noise A M2 3373 profile3(3) - T1.424/T-U Noise F M1 3374 profile4(4) - T1.424/T-U Noise F M2 3375 profile5(5) - ETSI TS 101 270-1 Noise A&B 3376 profile6(6) - ETSI TS 101 270-1 Noise C 3377 profile7(7) - ETSI TS 101 270-1 Noise D 3378 profile8(8) - ETSI TS 101 270-1 Noise E 3379 profile9(9) - ETSI TS 101 270-1 Noise F 3381 This object maps to the aUPBOReferenceProfile attribute 3382 in Clause 30." 3383 REFERENCE 3384 "[802.3ah] Annex 62A.3.4, 30.5.1.1.23" 3385 ::= { efmCuPme10PProfileEntry 4 } 3387 efmCuPme10PBandNotchProfiles OBJECT-TYPE 3388 SYNTAX BITS { 3389 profile0(0), 3390 profile1(1), 3391 profile2(2), 3392 profile3(3), 3393 profile4(4), 3394 profile5(5), 3395 profile6(6), 3396 profile7(7), 3397 profile8(8), 3398 profile9(9), 3399 profile10(10), 3400 profile11(11) 3401 } 3402 MAX-ACCESS read-create 3403 STATUS current 3404 DESCRIPTION 3405 "10PASS-TS PME Egress Control Band Notch Profile bitmap, 3406 as specified in 802.3ah Annex 62A. Possible values are: 3407 --------------+---------+----------+-----------+------+----- 3408 Profile Name G.991.3 T1.424/T-U TS101 270-1 StartF EndF 3409 Table Table Table (MHz) (MHz) 3410 --------------+---------+----------+-----------+------+----- 3411 profile0(0) - no profile 3412 profile1(1) - F-5 #01 - - 1.810 1.825 3413 profile2(2) - 6-2 15-1 17 1.810 2.000 3414 profile3(3) - F-5 #02 - - 1.907 1.912 3415 profile4(4) - F-5 #03 - - 3.500 3.575 3416 profile5(5) - 6-2 - 17 3.500 3.800 3417 profile6(6) - - 15-1 - 3.500 4.000 3418 profile7(7) - F-5 #04 - - 3.747 3.754 3419 profile8(8) - F-5 #05 - - 3.791 3.805 3420 profile9(9) - 6-2 - 17 7.000 7.100 3421 profile10(10) - F-5 #06 15-1 - 7.000 7.300 3422 profile11(11) - 6-2 15-1 1 10.100 10.150 3424 Any combination of profiles can be specified by ORing 3425 individual profiles, for example value of 0x0622 selects 3426 profiles 2,6,10 and 11. 3428 This object maps to the aBandNotchProfile attribute 3429 in Clause 30." 3430 REFERENCE 3431 "[802.3ah] Annex 62A.3.5, 30.5.1.1.19" 3433 ::= { efmCuPme10PProfileEntry 5 } 3435 efmCuPme10PPayloadURateProfile OBJECT-TYPE 3436 SYNTAX INTEGER { 3437 profile5(5), 3438 profile10(10), 3439 profile15(15), 3440 profile20(20), 3441 profile25(25), 3442 profile30(30), 3443 profile50(50), 3444 profile70(70), 3445 profile100(100) 3446 } 3447 MAX-ACCESS read-create 3448 STATUS current 3449 DESCRIPTION 3450 "10PASS-TS PME Upstream Payload Rate Profile, 3451 as specified in 802.3ah Annex 62A. Possible values are: 3452 profile5(5) - 2.5 Mbps 3453 profile10(10) - 5 Mbps 3454 profile15(15) - 7.5 Mbps 3455 profile20(20) - 10 Mbps 3456 profile25(25) - 12.5 Mbps 3457 profile30(30) - 15 Mbps 3458 profile50(50) - 25 Mbps 3459 profile70(70) - 35 Mbps 3460 profile100(100) - 50 Mbps 3462 Each value represents a target for the PME's Upstream Payload 3463 Bitrate as seen at the MII. If the payload rate of the 3464 selected profile cannot be achieved based on the loop 3465 environment, bandplan and PSD mask, the PME initialization 3466 SHALL fail. 3468 This object maps to the aPayloadRateProfileUpstream 3469 attribute in Clause 30." 3470 REFERENCE 3471 "[802.3ah] Annex 62A.3.6, 30.5.1.1.20" 3472 ::= { efmCuPme10PProfileEntry 6 } 3474 efmCuPme10PPayloadDRateProfile OBJECT-TYPE 3475 SYNTAX INTEGER { 3476 profile5(5), 3477 profile10(10), 3478 profile15(15), 3479 profile20(20), 3480 profile25(25), 3481 profile30(30), 3482 profile50(50), 3483 profile70(70), 3484 profile100(100), 3485 profile140(140), 3486 profile200(200) 3487 } 3488 MAX-ACCESS read-create 3489 STATUS current 3490 DESCRIPTION 3491 "10PASS-TS PME Downstream Payload Rate Profile, 3492 as specified in 802.3ah Annex 62A. Possible values are: 3493 profile5(5) - 2.5 Mbps 3494 profile10(10) - 5 Mbps 3495 profile15(15) - 7.5 Mbps 3496 profile20(20) - 10 Mbps 3497 profile25(25) - 12.5 Mbps 3498 profile30(30) - 15 Mbps 3499 profile50(50) - 25 Mbps 3500 profile70(70) - 35 Mbps 3501 profile100(100) - 50 Mbps 3502 profile140(140) - 70 Mbps 3503 profile200(200) - 100 Mbps 3505 Each value represents a target for the PME's Downstream 3506 Payload Bitrate as seen at the MII. If the payload rate of 3507 the selected profile cannot be achieved based on the loop 3508 environment, bandplan and PSD mask, the PME initialization 3509 SHALL fail. 3511 This object maps to the aPayloadRateProfileDownstream 3512 attribute in Clause 30." 3513 REFERENCE 3514 "[802.3ah] Annex 62A.3.6, 30.5.1.1.21" 3515 ::= { efmCuPme10PProfileEntry 7 } 3517 efmCuPme10PProfileRowStatus OBJECT-TYPE 3518 SYNTAX RowStatus 3519 MAX-ACCESS read-create 3520 STATUS current 3521 DESCRIPTION 3522 "This object controls creation/deletion of the associated 3523 entry in efmCuPme10PProfileTable per the semantics of 3524 RowStatus. 3525 If an active entry is referenced via efmCuAdminProfile or 3526 efmCuPmeAdminProfile, the entry MUST remain 'active' until 3527 all references are removed." 3528 ::= { efmCuPme10PProfileEntry 8 } 3530 efmCuPme10PStatusTable OBJECT-TYPE 3531 SYNTAX SEQUENCE OF EfmCuPme10PStatusEntry 3532 MAX-ACCESS not-accessible 3533 STATUS current 3534 DESCRIPTION 3535 "Table reflecting status of EFMCu 10PASS-TS PMEs (modems)." 3536 ::= { efmCuPme10P 2 } 3538 efmCuPme10PStatusEntry OBJECT-TYPE 3539 SYNTAX EfmCuPme10PStatusEntry 3540 MAX-ACCESS not-accessible 3541 STATUS current 3542 DESCRIPTION 3543 "An entry in the EFMCu 10PASS-TS PME Status table." 3544 AUGMENTS { efmCuPmeStatusEntry } 3545 ::= { efmCuPme10PStatusTable 1 } 3547 EfmCuPme10PStatusEntry ::= 3548 SEQUENCE { 3549 efmCuPme10PFECCorrectedBlocks Counter32, 3550 efmCuPme10PFECUncorrectedBlocks Counter32 3551 } 3553 efmCuPme10PFECCorrectedBlocks OBJECT-TYPE 3554 SYNTAX Counter32 3555 MAX-ACCESS read-only 3556 STATUS current 3557 DESCRIPTION 3558 "A count of received and corrected FEC codewords in 10PASS-TS 3559 PME. 3561 This object maps to aPMEFECCorrectedBlocks attribute in 3562 clause 30. 3564 If a Clause 45 MDIO Interface to the PMA/PMD is present, 3565 then this object maps to the 10P FEC correctable errors 3566 register 3568 Discontinuities in the value of this counter can occur at 3569 re-initialization of the management system, and at other times 3570 as indicated by the value of ifCounterDiscontinuityTime, 3571 defined in IF-MIB." 3572 REFERENCE 3573 "[802.3ah] 45.2.1.22, 30.11.2.1.8" 3574 ::= { efmCuPme10PStatusEntry 1 } 3576 efmCuPme10PFECUncorrectedBlocks OBJECT-TYPE 3577 SYNTAX Counter32 3578 MAX-ACCESS read-only 3579 STATUS current 3580 DESCRIPTION 3581 "A count of received FEC codewords in 10PASS-TS PME, which are 3582 uncorrectable. 3584 This object maps to aPMEFECUncorrectableBlocks attribute in 3585 clause 30. 3587 If a Clause 45 MDIO Interface to the PMA/PMD is present, 3588 then this object maps to the 10P FEC uncorrectable errors 3589 register 3591 Discontinuities in the value of this counter can occur at 3592 re-initialization of the management system, and at other times 3593 as indicated by the value of ifCounterDiscontinuityTime, 3594 defined in IF-MIB." 3595 REFERENCE 3596 "[802.3ah] 45.2.1.23, 30.11.2.1.9" 3597 ::= { efmCuPme10PStatusEntry 2 } 3599 -- 3600 -- Conformance Statements 3601 -- 3603 efmCuGroups OBJECT IDENTIFIER ::= { efmCuConformance 1 } 3605 efmCuCompliances OBJECT IDENTIFIER ::= { efmCuConformance 2 } 3607 -- Object Groups 3609 efmCuBasicGroup OBJECT-GROUP 3610 OBJECTS { 3611 efmCuPAFSupported, 3612 efmCuAdminProfile, 3613 efmCuTargetDataRate, 3614 efmCuTargetSnrMgn, 3615 efmCuAdaptiveSpectra, 3616 efmCuPortSide, 3617 efmCuFltStatus 3618 } 3619 STATUS current 3620 DESCRIPTION 3621 "A collection of objects required for all of EFMCu ports." 3622 ::= { efmCuGroups 1 } 3624 efmCuPAFGroup OBJECT-GROUP 3625 OBJECTS { 3626 efmCuPeerPAFSupported, 3627 efmCuPAFCapacity, 3628 efmCuPeerPAFCapacity, 3629 efmCuPAFAdminState, 3630 efmCuPAFDiscoveryCode, 3631 efmCuPAFRemoteDiscoveryCode, 3632 efmCuNumPMEs 3633 } 3634 STATUS current 3635 DESCRIPTION 3636 "A collection of objects required for OPTIONAL PME 3637 Aggregation Function (PAF) and PAF discovery in EFMCu ports." 3638 ::= { efmCuGroups 2 } 3640 efmCuPAFErrorsGroup OBJECT-GROUP 3641 OBJECTS { 3642 efmCuPAFInErrors, 3643 efmCuPAFInSmallFragments, 3644 efmCuPAFInLargeFragments, 3645 efmCuPAFInBadFragments, 3646 efmCuPAFInLostFragments, 3647 efmCuPAFInLostStarts, 3648 efmCuPAFInLostEnds, 3649 efmCuPAFInOverflows 3650 } 3651 STATUS current 3652 DESCRIPTION 3653 "A collection of objects supporting OPTIONAL error counters 3654 of PAF on EFMCu ports." 3655 ::= { efmCuGroups 3 } 3657 efmCuPmeGroup OBJECT-GROUP 3658 OBJECTS { 3659 efmCuPmeAdminProfile, 3660 efmCuPmeOperStatus, 3661 efmCuPmeFltStatus, 3662 efmCuPmeSubTypesSupported, 3663 efmCuPmeAdminSubType, 3664 efmCuPmeOperSubType, 3665 efmCuPAFRemoteDiscoveryCode, 3666 efmCuPmeOperProfile, 3667 efmCuPmeSnrMgn, 3668 efmCuPmePeerSnrMgn, 3669 efmCuPmeLineAtn, 3670 efmCuPmePeerLineAtn, 3671 efmCuPmeEquivalentLength, 3672 efmCuPmeTCCodingErrors, 3673 efmCuPmeTCCrcErrors, 3674 efmCuPmeThreshLineAtn, 3675 efmCuPmeThreshSnrMgn 3676 } 3677 STATUS current 3678 DESCRIPTION 3679 "A collection of objects providing information about 3680 a 2BASE-TL/10PASS-TS PME." 3681 ::= { efmCuGroups 4 } 3683 efmCuAlarmConfGroup OBJECT-GROUP 3684 OBJECTS { 3685 efmCuThreshLowRate, 3686 efmCuLowRateCrossingEnable, 3687 efmCuPmeThreshLineAtn, 3688 efmCuPmeLineAtnCrossingEnable, 3689 efmCuPmeThreshSnrMgn, 3690 efmCuPmeSnrMgnCrossingEnable, 3691 efmCuPmeDeviceFaultEnable, 3692 efmCuPmeConfigInitFailEnable, 3693 efmCuPmeProtocolInitFailEnable 3694 } 3695 STATUS current 3696 DESCRIPTION 3697 "A collection of objects required for configuration of alarm 3698 thresholds and notifications in EFMCu ports." 3699 ::= { efmCuGroups 5 } 3701 efmCuNotificationGroup NOTIFICATION-GROUP 3702 NOTIFICATIONS { 3703 efmCuLowRateCrossing, 3704 efmCuPmeLineAtnCrossing, 3705 efmCuPmeSnrMgnCrossing, 3706 efmCuPmeDeviceFault, 3707 efmCuPmeConfigInitFailure, 3708 efmCuPmeProtocolInitFailure 3709 -- efmCuPmeDeviceFault, 3710 -- efmCuPmeLocalPowerLoss 3711 } 3712 STATUS current 3713 DESCRIPTION 3714 "This group supports notifications of significant conditions 3715 associated with EFMCu ports." 3716 ::= { efmCuGroups 6 } 3718 efmCuPme2BProfileGroup OBJECT-GROUP 3719 OBJECTS { 3720 efmCuPme2BProfileDescr, 3721 efmCuPme2BRegion, 3722 efmCuPme2BsMode, 3723 efmCuPme2BMinDataRate, 3724 efmCuPme2BMaxDataRate, 3725 efmCuPme2BPower, 3726 efmCuPme2BConstellation, 3727 efmCuPme2BProfileRowStatus, 3728 efmCuPme2BsModeDescr, 3729 efmCuPme2BsModeRowStatus, 3730 efmCuPme2BEquivalentLength, 3731 efmCuPme2BMaxDataRatePam16, 3732 efmCuPme2BMaxDataRatePam32, 3733 efmCuPme2BReachRateRowStatus 3734 } 3735 STATUS current 3736 DESCRIPTION 3737 "A collection of objects that constitute a configuration 3738 profile for configuration of 2BASE-TL ports." 3739 ::= { efmCuGroups 7} 3741 efmCuPme10PProfileGroup OBJECT-GROUP 3742 OBJECTS { 3743 efmCuPme10PProfileDescr, 3744 efmCuPme10PBandplanPSDMskProfile, 3745 efmCuPme10PUPBOReferenceProfile, 3746 efmCuPme10PBandNotchProfiles, 3747 efmCuPme10PPayloadURateProfile, 3748 efmCuPme10PPayloadDRateProfile, 3749 efmCuPme10PProfileRowStatus 3750 } 3751 STATUS current 3752 DESCRIPTION 3753 "A collection of objects that constitute a configuration 3754 profile for configuration of 10PASS-TS ports." 3755 ::= { efmCuGroups 8 } 3757 efmCuPme10PStatusGroup OBJECT-GROUP 3758 OBJECTS { 3759 efmCuPme10PFECCorrectedBlocks, 3760 efmCuPme10PFECUncorrectedBlocks 3761 } 3762 STATUS current 3763 DESCRIPTION 3764 "A collection of objects providing status information 3765 specific to 10PASS-TS PMEs." 3766 ::= { efmCuGroups 9 } 3768 -- Compliance Statements 3769 efmCuCompliance MODULE-COMPLIANCE 3770 STATUS current 3771 DESCRIPTION 3772 "The compliance statement for 2BASE-TL/10PASS-TS interfaces. 3773 Compliance with the following external compliance statements 3774 is REQUIRED: 3776 MIB Module Compliance Statement 3777 ---------- -------------------- 3778 IF-MIB ifCompliance3 3779 EtherLike-MIB dot3Compliance2 3780 MAU-MIB mauModIfCompl3 3782 Compliance with the following external compliance statements 3783 is OPTIONAL for implementations supporting PME Aggregation 3784 Function (PAF) with flexible cross-connect between the PCS 3785 and PME ports: 3787 MIB Module Compliance Statement 3788 ---------- -------------------- 3789 IF-INVERTED-STACK-MIB ifInvCompliance 3790 IF-CAP-STACK-MIB ifCapStackCompliance" 3792 MODULE -- this module 3793 MANDATORY-GROUPS { 3794 efmCuBasicGroup, 3795 efmCuPmeGroup, 3796 efmCuAlarmConfGroup, 3797 efmCuNotificationGroup 3798 } 3800 GROUP efmCuPme2BProfileGroup 3801 DESCRIPTION 3802 "Support for this group is only required for implementations 3803 supporting 2BASE-TL Phy." 3805 GROUP efmCuPme10PProfileGroup 3806 DESCRIPTION 3807 "Support for this group is only required for implementations 3808 supporting 10PASS-TS Phy." 3810 GROUP efmCuPAFGroup 3811 DESCRIPTION 3812 "Support for this group is only required for 3813 implementations supporting PME Aggregation Function (PAF)." 3815 GROUP efmCuPAFErrorsGroup 3816 DESCRIPTION 3817 "Support for this group is OPTIONAL for implementations 3818 supporting PME Aggregation Function (PAF)." 3820 GROUP efmCuPme10PStatusGroup 3821 DESCRIPTION 3822 "Support for this group is OPTIONAL for implementations 3823 supporting 10PASS-TS Phy." 3825 OBJECT efmCuPmeSubTypesSupported 3826 SYNTAX BITS { 3827 ieee2BaseTLO(0), 3828 ieee2BaseTLR(1), 3829 ieee10PassTSO(2), 3830 ieee10PassTSR(3) 3831 } 3832 DESCRIPTION 3833 "Support for all subtypes is not required. However at least 3834 one value SHALL be supported" 3836 OBJECT efmCuPmeAdminSubType 3837 MIN-ACCESS read-only 3838 DESCRIPTION 3839 "Write access is not required (needed only for PMEs 3840 supporting more than a single subtype, e.g. 3841 ieee2BaseTLO and ieee2BaseTSR or ieee2BaseTLR and 3842 ieee10PassTSR)" 3844 OBJECT efmCuTargetSnrMgn 3845 MIN-ACCESS read-only 3846 DESCRIPTION 3847 "Write access is OPTIONAL. For PHYs without write access 3848 the target SNR margin SHALL be fixed at 5dB for 2BASE-TL 3849 and 6dB for 10PASS-TS." 3851 OBJECT efmCuAdaptiveSpectra 3852 MIN-ACCESS read-only 3853 DESCRIPTION 3854 "Write access is OPTIONAL. For PHYs without write access 3855 the default value SHOULD be false." 3857 ::= { efmCuCompliances 1 } 3858 END 3860 7. Security Considerations 3862 There is a number of managed objects defined in the EFM-CU-MIB module 3863 that have a MAX-ACCESS clause of read-write or read-create. Most 3864 objects are writeable only when the link is Down. Writing to these 3865 objects can have potentially disruptive effects on network operation, 3866 for example: 3868 o Changing of efmCuPmeAdminSubType MAY lead to a potential locking 3869 of the link, as peer PMEs of the same sub-type cannot exchange 3870 handshake messages. 3872 o Changing of efmCuPAFAdminState to enabled MAY lead to a potential 3873 locking of the link, if the peer Phy does not support PAF. 3875 o Changing of efmCuPAFDiscoveryCode, before the discovery operation, 3876 MAY lead to a wrongful discovery, for example when two -O ports 3877 are connected to the same multi-PME -R port and both -O ports have 3878 the same Discovery register value. 3880 o Changing PCS or PME configuration parameters (e.g. profile of a 3881 PCS or PME via efmCuAdminProfile or efmCuPmeAdminProfile) MAY lead 3882 to anything from link quality and rate degradation to a complete 3883 link initialization failure, as ability of an EFMCu port to 3884 support a particular configuration depends on the copper 3885 environment. 3887 o Activation of a PME can cause a severe degradation of service for 3888 another EFMCu Phy, whose PME(s) MAY be affected by the cross-talk 3889 from the newly activated PME. 3891 o Removal of a PME from an operationally 'up' EFMCu port, 3892 aggregating several PMEs, MAY cause port's rate degradation 3894 The user of the EFM-CU-MIB module must therefore be aware that 3895 support for SET operations in a non-secure environment without proper 3896 protection can have a negative effect on network operations. 3898 The readable objects in the EFM-CU-MIB module (i.e., those with MAX- 3899 ACCESS other than not-accessible) may be considered sensitive in some 3900 environments since, collectively, they provide information about the 3901 performance of network interfaces and can reveal some aspects of 3902 their configuration. In particular since EFMCu can be carried over 3903 Unshielded Twisted Pair (UTP) voice grade copper in a bundle with 3904 other pairs belonging to another operator/customer, it is 3905 theoretically possible to evasdrop to an EFMCu transmission simply by 3906 "listening" to a cross-talk from an EFMCu pair, especially if the 3907 parameters of the EFMCu link in question are known. In such 3908 environments it is important to control even GET and NOTIFY access to 3909 these objects and possibly even to encrypt their values when sending 3910 them over the network via SNMP. 3912 SNMP versions prior to SNMPv3 did not include adequate security. 3913 Even if the network itself is secure (for example by using IPSec), 3914 even then, there is no control as to who on the secure network is 3915 allowed to access and GET/SET (read/change/create/delete) the objects 3916 in these MIB modules. 3918 It is RECOMMENDED that implementers consider the security features as 3919 provided by the SNMPv3 framework (see [RFC3410], section 8), 3920 including full support for the SNMPv3 cryptographic mechanisms (for 3921 authentication and privacy). 3923 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3924 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3925 enable cryptographic security. It is then a customer/operator 3926 responsibility to ensure that the SNMP entity giving access to an 3927 instance of these MIB modules is properly configured to give access 3928 to the objects only to those principals (users) that have legitimate 3929 rights to indeed GET or SET (change/create/delete) them. 3931 8. IANA Considerations 3933 The two new values of dot3MauType (dot3MauType2BaseTL and 3934 dot3MauType10PassTS) and corresponding IANAifMauTypeListBits bit 3935 definitions (b2BaseTL and b10PassTS), as well as the new values for 3936 IANAifMauMediaAvailable (availableReduced and ready) SHALL be defined 3937 by the IANA in the IANA-MAU-MIB module (see [I-D.ietf-hubmib- 3938 rfc3636bis]) before this document is published as an RFC. 3940 9. Acknowledgments 3942 This document was produced by the IETF Ethernet Interfaces and Hub 3943 MIB Working Group, whose efforts were greatly advanced by the 3944 contributions of the following people (in alphabetical order): 3946 Dan Romascanu 3948 Marina Popilov 3950 Mathias Riess 3952 Matt Squire 3953 Mike Heard 3955 Udi Ashkenazi 3957 10. References 3959 10.1. Normative References 3961 [802.3] IEEE, "IEEE Standard for Information technology - 3962 Telecommunications and information exchange between 3963 systems - Local and metropolitan area networks - Specific 3964 requirements - Part 3: Carrier Sense Multiple Access with 3965 Collision Detection (CSMA/CD) Access Method and Physical 3966 Layer Specifications", IEEE Std 802.3-2005, December 2005. 3968 [802.3ah] IEEE, "IEEE Standard for Information technology - 3969 Telecommunications and information exchange between 3970 systems - Local and metropolitan area networks - Specific 3971 requirements - Part 3: Carrier Sense Multiple Access with 3972 Collision Detection (CSMA/CD) Access Method and Physical 3973 Layer Specifications - Amendment: Media Access Control 3974 Parameters, Physical Layers and Management Parameters for 3975 Subscriber Access Networks", IEEE Std 802.3ah-2004, 3976 September 2004. 3978 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3979 Requirement Levels", BCP 14, RFC 2119, March 1997. 3981 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3982 McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of 3983 Management Information Version 2 (SMIv2)", STD 58, 3984 RFC 2578, April 1999. 3986 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3987 McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 3988 Conventions for SMIv2", STD 58, RFC 2579, April 1999. 3990 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3991 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3992 April 1999. 3994 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3995 "Introduction and Applicability Statements for Internet- 3996 Standard Management Framework", RFC 3410, December 2002. 3998 10.2. Informative References 4000 [ANFP] Network Interoperability Consultative Committee (NICC), 4001 "Specification of the Access Network Frequency Plan (ANFP) 4002 applicable to transmission systems used on the BT Access 4003 Network", NICC Document ND1602:2005/08, August 2005. 4005 [G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber Line 4006 (SHDSL) transceivers", ITU-T Recommendation G.991.2, 4007 December 2003. 4009 [G.993.1] ITU-T, "Very High speed Digital Subscriber Line 4010 transceivers", ITU-T Recommendation G.993.1, June 2004. 4012 [I-D.ietf-hubmib-efm-epon-mib] 4013 Khermosh, L., "Managed Objects of EPON", 4014 draft-ietf-hubmib-efm-epon-mib-05 (work in progress), 4015 July 2006. 4017 [I-D.ietf-hubmib-efm-mib] 4018 Squire, M., "Definitions and Managed Objects for OAM 4019 Functions on Ethernet Like Interfaces", 4020 draft-ietf-hubmib-efm-mib-04 (work in progress), 4021 March 2006. 4023 [I-D.ietf-hubmib-rfc3636bis] 4024 Beili, E., "Definitions of Managed Objects for IEEE 802.3 4025 Medium Attachment Units (MAUs)", 4026 draft-ietf-hubmib-rfc3636bis-05 (work in progress), 4027 July 2006. 4029 [IANAifType-MIB] 4030 Internet Assigned Numbers Authority (IANA), "IANAifType 4031 Textual Convention definition", 4032 http://www.iana.org/assignments/ianaiftype-mib. 4034 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 4035 MIB", RFC 2863, June 2000. 4037 [RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table 4038 Extension to the Interfaces Group MIB", RFC 2864, 4039 June 2000. 4041 [RFC3635] Flick, J., "Definitions of Managed Objects for the 4042 Ethernet-like Interface Types", RFC 3635, September 2003. 4044 [RFC4070] Dodge, M. and B. Ray, "Definitions of Managed Object 4045 Extensions for Very High Speed Digital Subscriber Lines 4046 (VDSL) Using Multiple Carrier Modulation (MCM) Line 4047 Coding", RFC 4070, May 2005. 4049 [RFC4319] Sikes, C., Ray, B., and R. Abbi, "Definitions of Managed 4050 Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and 4051 Single-Pair High-Speed Digital Subscriber Line (SHDSL) 4052 Lines", RFC 4319, December 2005. 4054 Author's Address 4056 Edward Beili 4057 Actelis Networks 4058 Bazel 25 4059 Petach-Tikva 4060 Israel 4062 Phone: +972-3-924-3491 4063 Email: edward.beili@actelis.com 4065 Intellectual Property Statement 4067 The IETF takes no position regarding the validity or scope of any 4068 Intellectual Property Rights or other rights that might be claimed to 4069 pertain to the implementation or use of the technology described in 4070 this document or the extent to which any license under such rights 4071 might or might not be available; nor does it represent that it has 4072 made any independent effort to identify any such rights. Information 4073 on the procedures with respect to rights in RFC documents can be 4074 found in BCP 78 and BCP 79. 4076 Copies of IPR disclosures made to the IETF Secretariat and any 4077 assurances of licenses to be made available, or the result of an 4078 attempt made to obtain a general license or permission for the use of 4079 such proprietary rights by implementers or users of this 4080 specification can be obtained from the IETF on-line IPR repository at 4081 http://www.ietf.org/ipr. 4083 The IETF invites any interested party to bring to its attention any 4084 copyrights, patents or patent applications, or other proprietary 4085 rights that may cover technology that may be required to implement 4086 this standard. Please address the information to the IETF at 4087 ietf-ipr@ietf.org. 4089 Disclaimer of Validity 4091 This document and the information contained herein are provided on an 4092 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 4093 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 4094 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 4095 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 4096 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 4097 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 4099 Copyright Statement 4101 Copyright (C) The Internet Society (2006). This document is subject 4102 to the rights, licenses and restrictions contained in BCP 78, and 4103 except as set forth therein, the authors retain all their rights. 4105 Acknowledgment 4107 Funding for the RFC Editor function is currently provided by the 4108 Internet Society.