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