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