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