idnits 2.17.1 draft-ietf-hubmib-efm-cu-mib-03.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.a on line 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 3394. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 3371. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 3378. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 3384. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: This document is an Internet-Draft and is subject to all provisions of Section 3 of RFC 3667. By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 26 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: These default entries SHALL be created during agent initialization and MUST not be deleted. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: Profiles may be created/deleted using the row creation/ deletion mechanism via efmCuPme2BProfileRowStatus. If an active entry is referenced, the entry MUST remain 'active' until all references are removed. Default entries MUST not be removed." INDEX { efmCuPme2BProfileIndex } ::= { efmCuPme2BProfileTable 1 } == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: These default entries SHALL be created by during agent initialization and MUST not be deleted. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: Profiles may be created/deleted using the row creation/ deletion mechanism via efmCuPme10PProfileRowStatus. If an 'active' entry is referenced, the entry MUST remain 'active' until all references are removed. Default entries MUST not be removed." INDEX { efmCuPme10PProfileIndex } ::= { efmCuPme10PProfileTable 1 } -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (April 4, 2005) is 6955 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC3411' is mentioned on line 580, but not defined == Missing Reference: 'IF-MIB' is mentioned on line 2794, but not defined ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Downref: Normative reference to an Informational RFC: RFC 3410 == Outdated reference: A later version (-11) exists of draft-ietf-adslmib-gshdslbis-09 == Outdated reference: A later version (-06) exists of draft-ietf-hubmib-efm-epon-mib-03 == Outdated reference: A later version (-06) exists of draft-ietf-hubmib-efm-mib-03 == Outdated reference: A later version (-05) exists of draft-ietf-hubmib-rfc3636bis-00 Summary: 7 errors (**), 0 flaws (~~), 14 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group E. Beili 2 Internet-Draft Actelis Networks 3 Expires: October 3, 2005 April 4, 2005 5 Ethernet in the First Mile Copper (EFMCu) Interfaces MIB 6 draft-ietf-hubmib-efm-cu-mib-03.txt 8 Status of this Memo 10 This document is an Internet-Draft and is subject to all provisions 11 of section 3 of RFC 3667. By submitting this Internet-Draft, each 12 author represents that any applicable patent or other IPR claims of 13 which he or she is aware have been or will be disclosed, and any of 14 which he or she become aware will be disclosed, in accordance with 15 RFC 3668. 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 20 Internet-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 October 3, 2005. 35 Copyright Notice 37 Copyright (C) The Internet Society (2005). 39 Abstract 41 This document defines a Management Information Base (MIB) module for 42 use with network management protocols in TCP/IP based internets. 43 This document proposes an extension to the Ethernet-like Interfaces 44 MIB and MAU MIB modules with a set of objects for managing an 45 Ethernet in the First Mile Copper (EFMCu) interfaces 10PASS-TS and 46 2BASE-TL, defined in IEEE Std 802.3ah-2004. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 2. The Internet-Standard Management Framework . . . . . . . . . . 3 52 3. Relation to other MIB modules . . . . . . . . . . . . . . . . 4 53 3.1 Relation to Interfaces Group MIB module . . . . . . . . . 4 54 3.1.1 Layering Model . . . . . . . . . . . . . . . . . . . . 4 55 3.1.2 PME Aggregation Function (PAF) . . . . . . . . . . . . 6 56 3.1.3 Discovery Operation . . . . . . . . . . . . . . . . . 6 57 3.1.4 EFMCu ports initialization . . . . . . . . . . . . . . 8 58 3.1.5 Usage of ifTable . . . . . . . . . . . . . . . . . . . 8 59 3.2 Relation to SHDSL MIB module . . . . . . . . . . . . . . . 9 60 3.3 Relation to VDSL MIB module . . . . . . . . . . . . . . . 10 61 3.4 Relation to Ethernet-Like and MAU MIB modules . . . . . . 10 62 4. MIB Structure . . . . . . . . . . . . . . . . . . . . . . . . 11 63 4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 11 64 4.2 PME Profiles . . . . . . . . . . . . . . . . . . . . . . . 11 65 4.3 Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . 12 66 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 13 67 6. Security Considerations . . . . . . . . . . . . . . . . . . . 67 68 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 69 69 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 69 70 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69 71 9.1 Normative References . . . . . . . . . . . . . . . . . . . . 69 72 9.2 Informative References . . . . . . . . . . . . . . . . . . . 70 73 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 71 74 Intellectual Property and Copyright Statements . . . . . . . . 72 76 1. Introduction 78 New Ethernet-like interfaces have been defined in the Institute of 79 Electrical and Electronics Engineers (IEEE) Standard 802.3ah-2004 80 [802.3ah], a.k.a. Ethernet in the First Mile (EFM). In particular 81 2BASE-TL and 10PASS-TS physical interfaces (PHYs), defined over 82 voice-grade copper pairs, have been specified for the long and short 83 reach respectively. These interfaces, collectively called EFMCu, are 84 based on ITU-T G.SHDSL [G.991.2] and VDSL [G.993.1] specifications 85 and support variable rates and optional Physical Medium Entity (PME) 86 aggregation (a.k.a. multi-pair bonding). 88 2BASE-TL PHY is capable of providing at least 2Mbps over 2700 m long 89 single copper pair with a mean Bit Error Rate (BER) of 10^-7 (using 90 5dB target noise margin). 92 10PASS-TS PHY is capable of providing at least 10Mbps over 750 m long 93 single copper pair with a mean BER of 10^-7 (using 6dB target noise 94 margin). 96 This memo defines a Management Information Base (MIB) module for use 97 with network management protocols in the Internet community to manage 98 EFMCu interfaces. 100 Note that managed objects for Operation, Administration and 101 Management (OAM) and Ethernet over Passive Optical Networks (EPON) 102 clauses of IEEE 802.3ah are defined in EFM-COMMON-MIB 103 [I-D.ietf-hubmib-efm-mib] and EFM-EPON-MIB 104 [I-D.ietf-hubmib-efm-epon-mib] respectively. 106 2. The Internet-Standard Management Framework 108 For a detailed overview of the documents that describe the current 109 Internet-Standard Management Framework, please refer to section 7 of 110 RFC 3410 [RFC3410]. 112 Managed objects are accessed via a virtual information store, termed 113 the Management Information Base or MIB. MIB objects are generally 114 accessed through the Simple Network Management Protocol (SNMP). 115 Objects in the MIB are defined using the mechanisms defined in the 116 Structure of Management Information (SMI). This memo specifies a MIB 117 module that is compliant to the SMIv2, which is described in STD 58, 118 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 119 [RFC2580]. A detailed introduction to the current SNMP Management 120 Framework can be found in RFC 2570 [RFC2570]. 122 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 123 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 124 document are to be interpreted as described in RFC 2119 [RFC2119]. 126 3. Relation to other MIB modules 128 This section outlines the relationship of this MIB with other MIB 129 modules described in the relevant RFCs. Specifically, Interfaces 130 Group MIB (IF-MIB), Ethernet-Like (EtherLike-MIB), MAU (MAU-MIB), 131 SHDSL (HDSL2-SHDSL-LINE-MIB) and VDSL (VDSL-LINE-EXT-MCM-MIB) are 132 discussed. 134 3.1 Relation to Interfaces Group MIB module 136 2BASE-TL and 10PASS-TS PHY's specified in this MIB module are stacked 137 Ethernet interfaces and as such are managed using generic interface 138 management objects defined in the IF-MIB [RFC2863]. The stack 139 management is done via the ifStackTable, as defined in the IF-MIB 140 [RFC2863] and ifInvStackTable, as defined in the 141 IF-INVERTED-STACK-MIB [RFC2864]. 143 3.1.1 Layering Model 145 An EFMCu interface can aggregate up to 32 Physical Medium Entity 146 (PME) sub-layer devices (modems), using so called PME Aggregation 147 Function (PAF). 149 A generic EFMCu device can have a number of Physical Coding Sublayer 150 (PCS) ports, connected to a MAC via Medium Independent Interface 151 (MII) at the upper layer, and cross-connected to a number of 152 underlying PMEs, with a single PCS per PME relationship, see clause 153 61.1 of [802.3ah] for more details. 155 Each PME in the aggregated EFMCu port is represented in the Interface 156 table (ifTable) as a separate port with ifType of shdsl(169) for 157 2BASE-TL or vdsl(97) for 10PASS-TS. The ifType values are defined in 158 [IANAifType-MIB]. 160 ifSpeed for each PME SHALL return the actual data bitrate of the 161 active PME (e.g. for 2BaseTL PMEs it is a multiple of 64Kbps). Zero 162 value SHALL be returned when PME is initializing or down. 164 The ifSpeed of the PCS is the sum of the current operating data rates 165 of all PMEs in the aggregation group, without the 64/65B 166 encapsulation overhead and PAF overhead, but acounting for the 167 Inter-Frame Gaps (IFG). 169 When using the stated definition of ifSpeed for the PCS, there would 170 be no frame loss in the following configuration (the test-sets are 171 configured to generate 100% of back to back traffic, i.e. minimal 172 IFG, at 10 or 100Mbps, with min and max frame sizes; the EFM 173 interfaces are obviously aggregated): 175 [testset]--10BaseT--[CO]--2BaseTL--[CPE]--10BaseT--[testset] 176 ifSpeed= 10Mbps 10Mbps 10Mbps 178 [testset]--100BaseT--[CO]--10PassTS--[CPE]--100BaseT--[testset] 179 ifSpeed= 100Mbps 100Mbps 100Mbps 181 Figure 1: Example configuration with no frame loss 183 The following figure shows the layering diagram and corresponding use 184 of ifTable and ifMauTable: 186 _________________________ _ 187 | LLC | | 188 +-------------------------+ | 1 ifEntry 189 | MAC | | ifType: ethernetCsmacd(6) 190 +-------------------------+ > ifMauEntry 191 | Reconsiliation | | ifMauType: dot3MauType2BaseTL or 192 +-------------------------+ | dot3MauType10PassTS 193 | PCS | | 194 +-------------+---+-------+ + 195 | TC \ | | | | 196 +-----\ | | | | 197 | PMA > PME 1 |...| PME N | > N ifEntry (N=1..32) 198 +-----/ | | | | ifType: shdsl(169) or vdsl(97) 199 | PMD/ | | | | 200 -------------+---+------- - 202 Figure 2: Use of ifTable and ifMauTable for EFMCu ports 204 The ifStackTable is indexed by the ifIndex values of the aggregated 205 EFMCu port (PCS) and the PMEs connected to it. ifStackTable allows a 206 Network Management application to determine which PMEs are connected 207 to a particular PCS and change connections (if supported by the 208 application). The ifInvStackTable, being an inverted version of the 209 ifStackTable, provides an efficient means for a Network Management 210 application to read a subset of the ifStackTable and thereby 211 determine which PCS runs on top of a particular PME. 213 A new table ifAvailableStackTable defined in this MIB module, 214 specifies for each PCS a list of PMEs, which can possibly be 215 cross-connected to that PCS, determined by the cross-connect 216 capability of the device. This table, modeled after ifStackTable, is 217 read only, reflecting current cross-connect capability, which can be 218 dynamic in some implementations (e.g. if PMEs are located on a 219 pluggable module and the module is pulled out). Note that PME 220 availability per PCS, described by ifAvailableStackTable, can be 221 constrained by other parameters, for example by aggregation capacity 222 of a PCS or by the PME in question being already connected to another 223 PCS. So, in order to ensure that a particular PME can be connected 224 to the PCS, all respective parameters (e.g. ifAvailableStackTable, 225 ifStackTable and efmCuPAFCapacity) SHALL be inspected. 227 3.1.2 PME Aggregation Function (PAF) 229 The PME Aggregation Function (PAF) allows a number of PMEs to be 230 aggregated onto a PCS port, by fragmenting the Ethernet frames, 231 transmitting the fragments over multiple PMEs and assembling the 232 original frames at the remote port. PAF is OPTIONAL, meaning that a 233 device with a single PME MAY perform fragmentation and re-assembly if 234 this function is supported by the device. Note however that the 235 agent is REQUIRED to report on the PAF capability for all EFMCu ports 236 (2BASE-TL and 10PASS-TS). 238 This MIB module allows a Network Management application to query PAF 239 capability and enable/disable it if supported. Note that enabling 240 PAF effectively turns on fragmentation and re-assembly, even on a 241 single-PME port. 243 3.1.3 Discovery Operation 245 The EFMCu ports may optionally support discovery operation, whereby 246 PMEs, during initialization, exchange information about their 247 respective aggregation groups (PCS). This information can then be 248 used to detect copper missconnections or for an automatic assignment 249 of the local PMEs into aggregation groups instead of fixed 250 pre-configuration. 252 This MIB module allows a Network Management application to control 253 EFM Discovery mechanism and query its results. Note that the 254 Discovery mechanism can work only if PAF is supported and enabled. 256 Two tables are used by Discovery mechanism: ifStackTable and 257 ifAvailableStackTable defined. The following pseudo-code defines an 258 example of Discovery and automatic PME assignment for a generic PAF 259 enabled multi-PCS EFMCu device, located at Central Office (CO), using 260 objects defined in this MIB module. [Note that automatic PME 261 assignment is only shown here for the purposes of the example. Fixed 262 PME pre-assignment, manual assignment or auto-assignment by an 263 alternative internal algorithm may be chosen by a particular 264 implementation]: 266 FOREACH pcs[i] IN co_device 267 { // Discover only on PAF enabled ports with room for more PMEs 268 IF ( pcs[i].PAFSupported AND pcs[i].NumPMEs < pcs[i].PAFCapacity ) 269 { dc = pcs[i].DiscoveryCode = MAC[i]; // unique 6 Byte per PCS 270 // go over all currently disconnected PMEs, which can 271 // pottentially be connected to PCS[i] 272 FOREACH pme[j] IN ifAvailableStackTable[pcs[i]] AND 273 NOT IN ifInvStackTable[pme[j]] // unassigned 274 { pme[j].RemoteDiscoveryCode = dc; // Set if Clear 275 r = pme[j].RemoteDiscoveryCode; // Get 276 IF ( r == dc AND pcs[i].NumPMEs < pcs[i].PAFCapacity) 277 { // Remote CPE connected via PME[j] is/was a peer for 278 // PCS[i]. Connect this PME to the PCS (there's room) 279 ADD pme[j] TO ifStackTable[pcs[i]]; 280 pcs[i].NumPMEs = pcs[i].NumPMEs + 1; 281 // Discover all other currently disconnected PMEs, 282 // attached to the same CPE and connect them to the PCS 283 // provided there is enough room for more PMEs. 284 FOREACH pme[k] IN ifAvailableStackTable[pcs[i]] and 285 NOT IN ifInvStackTable[pme[k]] 286 { r = pme[k].RemoteDiscoveryCode; // Get 287 IF ( r == dc AND 288 pcs[i].NumPMEs < pcs[i].PAFCapacity) 289 { ADD pme[k] TO ifStackTable[pcs[i]]; 290 pcs[i].NumPMEs = pcs[i].NumPMEs + 1; 291 } 292 } 293 } 294 // Discovered all PMEs which lead to the same CPE and 295 // connected them to PCS[i]. Go to the next PCS. 296 BREAK; 297 } 298 } 299 } 301 The SNMP Agent builds efmCuStackTable according to the information 302 contained in the Clause 45 PME_Available_register (see [802.3ah] 303 61.1.5.3 and 45.2.3.20). 305 Adding a PME to the ifStackTable row for a specific PCS, involves 306 actual connection of the PME to the PCS, which can be done by 307 modifying Clause 45 PME_Aggregate_register (see [802.3ah] 61.1.5.3 308 and 45.2.3.21). 310 Note that PCS port does not have to be operationally 'down' for the 311 connection to succeed. In fact, a dynamic PME addition (and removal) 312 MAY be implemented whith an available PME being initialized first (by 313 setting its ifAdminStatus to 'up') and then added to an operationally 314 'up' PCS port, by modifying a respective ifStackTable entry. 316 It is RECOMMENDED that a removal of the last operationally 'up' PME 317 from an operationally 'up' PCS would be rejected by the 318 implementation, as this action would completely drop the link. 320 3.1.4 EFMCu ports initialization 322 EFMCu ports being built on top of xDSL technology, require a lengthy 323 initialization or 'training' process, before any data can pass. 324 During this initialization both ends of a link (peers) work 325 cooperatively to achieve required data rate on a particular copper 326 pair. Sometimes, when the copper line is too long or the noise 327 environment on the line is too high, that 'training' process may fail 328 to achieve a specific target rate with required characteristics. 330 The ifAdminStatus object from the IF-MIB, controls the desired state 331 of a PCS and a PME port. Setting this object to 'up' instructs a 332 particular PCS or PME to start initialization process, which may take 333 tens of seconds for EFMCu ports, especially if PAF is involved. The 334 ifOperStatus object shows the operational state of an interface 335 (extended by efmCuPmeOperStatus defined in this MIB module for PME 336 interfaces). 338 A disconnected PME may be initialized by changing the ifAdminState 339 from 'down' to 'up'. Changing the ifAdminState to 'up' on the PCS 340 initializes all PMEs connected to that particular PCS. Note that in 341 case of PAF some interfaces may fail to initialize while others 342 succeed. The PCS is considered operationally 'up' if at least one 343 PME aggregated by its PAF is operationally 'up'. When all PMEs 344 connected to the PCS are 'down' the PCS SHALL be considered 345 operationally 'lowerLayerDown'. The PCS SHALL be considered 346 operationally 'notPresent' if it is not connected to any PME. The 347 PCS/PME interface SHALL remain operationally 'down' during 348 initialization. 350 The efmCuPmeOperStatus defined in this MIB module expands PME's 351 ifOperStatus value of 'down' to 'downReady', 'downNotReady' and 352 'init' values, indicating various EFMCu PME specific states. 354 3.1.5 Usage of ifTable 356 Both PME and PCS interfaces of the EFMCu PHY are managed using 357 interface specific management objects defined in this MIB module and 358 generic interface objects from the ifTable of IF-MIB, with all 359 management table entries referenced by the interface index ifIndex. 361 The following table summarizes EFMCu specific interpretations for 362 some of the ifTable objects specified by the mandatory 363 ifGeneralInformationGroup: 365 +---------------------------------+---------------------------------+ 366 | IF-MIB object | EFMCu interpretation | 367 +---------------------------------+---------------------------------+ 368 | ifIndex | Interface index. Note that each | 369 | | PME and each PCS in the EFMCu | 370 | | PHY MUST have a unique index, | 371 | | as there some PCS and PME | 372 | | specific attributes accessible | 373 | | only on the PCS or PME level. | 374 | ifType | ethernetCsmacd(6) for PCS, | 375 | | shdsl(169) for 2BASE-TL PME, | 376 | | vdsl(97) for 10PASS-TS PME | 377 | ifSpeed | Operating data rate for the | 378 | | PME. For the PCS it is the sum | 379 | | of the current operating data | 380 | | rates of all PMEs in the | 381 | | aggregation group, without the | 382 | | 64/65B encapsulation overhead | 383 | | and PAF overhead, but acounting | 384 | | for the Inter-Frame Gaps (IFG) | 385 | ifAdminStatus | Setting this object to 'up' | 386 | | instructs a particular PCS | 387 | | (with all PMEs connected to it) | 388 | | or PME to start initialization | 389 | | process | 390 | ifOperStatus | efmCuPmeOperStatus supplements | 391 | | the 'down' value of | 392 | | ifOperStatus for PMEs. | 393 +---------------------------------+---------------------------------+ 395 Table 1 397 3.2 Relation to SHDSL MIB module 399 G.SHDSL.bis modems, similar to PME(s) comprising a 2BASE-TL port, are 400 described in HDSL2-SHDSL-LINE-MIB [I-D.ietf-adslmib-gshdslbis]. Note 401 that not all attributes of G.SHDSL modems reflected in 402 HDSL2-SHDSL-LINE-MIB have adequate management objects (Clause 30 403 attributes and Clause 45 registers) in the EFM standard. 405 Because of these differences and for the purposes of simplicity, 406 unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs 407 and name consistency (e.g. prefixing the 2BASE-TL PME related 408 objects with 'efmCuPme2B' instead of 'hdsl2shdsl'), it was decided 409 not to reference HDSL2-SHDSL-LINE-MIB objects, but define all the 410 relevant objects in this MIB module. 412 However, if some functionality, not available in this MIB module, is 413 required and supported by the PME, e.g. performance monitoring, 414 relevant HDSL2-SHDSL-LINE-MIB groups MAY be included and aplied for 415 PMEs of 2BASE-TL subtype. 417 3.3 Relation to VDSL MIB module 419 VDSL (DMT) modems, similar to the PME(s) comprising a 10PASS-TS port, 420 are described in VDSL-LINE-EXT-MCM-MIB 421 [I-D.ietf-adslmib-vdsl-ext-mcm]. Note that not all attributes of 422 VDSL modems reflected in VDSL-LINE-EXT-MCM-MIB have adequate 423 management objects (Clause 30 attributes and Clause 45 registers) in 424 the EFM standard. 426 Because of these differences and for the purposes of simplicity, 427 unification of attributes common to both 2BASE-TL and 10PASS-TS PMEs 428 and name consistency, it was decided not to reference 429 VDSL-LINE-EXT-MCM-MIB objects, but define all the relevant objects in 430 this MIB module. 432 However, if some functionality, not available in this MIB module, is 433 required and supported by the PME, relevant VDSL-LINE-EXT-MCM-MIB 434 groups MAY be included and applied for PMEs of 10PASS-TS subtype. 436 3.4 Relation to Ethernet-Like and MAU MIB modules 438 The implementation of EtherLike-MIB [RFC3635] and MAU-MIB 439 [I-D.ietf-hubmib-rfc3636bis] is REQUIRED for the EFMCu interfaces. 441 Two new values of ifMauType (OBJECT-IDENTITIES of dot3MauType) and 442 corresponding bit definitions of ifMauTypeListBits 443 (IANAifMauTypeListBits) have been defined in the IANA-MAU-TC-MIB 444 [I-D.ietf-hubmib-rfc3636bis] for the EFMCu MAUs: 446 o dot3MauType2BaseTL and b2BaseTL - for 2BASE-TL MAU 448 o dot3MauType10PassTS and b10PassTS - for 10PASS-TS MAU 450 As an EtherLike interface every EFMCu port (an ifEntry representing a 451 consolidation of LLC, MAC and PCS (sub)layers) SHALL return an ifType 452 of ethernetCsmacd(6). While most of the MAU characteristics are not 453 applicable to the EFMCu ports (no auto-negotiation, media available, 454 false carriers or jabber), they SHALL return an appropriate ifMauType 455 (dot3MauType2BaseTL or dot3mauType10PassTS) in order to direct the 456 management software to look in the EFM-CU-MIB for the desired 457 information. For example the information on the particular EFMCu 458 flavor that an EFMCu port is running is available from 459 efmCuOperSubType, defined in this MIB module. 461 Since EFMCu PMEs are not EtherLike interfaces, they cannot be 462 instantiated as MAU interface objects. 464 4. MIB Structure 466 4.1 Overview 468 The main management objects defined in this MIB module are split into 469 2 groups: 471 o efmCuPort - containing objects for configuration, capabilities, 472 status and notifications, common to all EFMCu PHYs. 474 o efmCuPme - containing objects for configuration, capabilities, 475 status and notifications of EFMCu PMEs. 477 In addition the ifAvailableStackTable is defined at the same level. 479 The efmCuPme group in turn contains efmCuPme2B and efmCuPme10P 480 groups, which define PME Profiles specific to 2BASE-TL and 10PASS-TS 481 PMEs respectively, as well as PME specific status information. 483 4.2 PME Profiles 485 Since a managed node can have a large number of EFMCu PHYs, 486 provisioning every parameter on every EFMCu PHY may become 487 burdensome. Moreover, most PMEs are provisioned identically with the 488 same set of parameters. To simplify the provisioning process, this 489 MIB module makes use of configuration profiles, similar to 490 HDSL2-SHDSL-LINE-MIB and VDSL-LINE-EXT-MCM-MIB. A profile is a set 491 of parameters, used either for configuration or representation of a 492 PME. The same profile can be shared by multiple PME ports, using the 493 same configuration. 495 The PME profiles are defined in efmCuPme2BProfileTable and 496 efmCu10PProfileTable for 2BASE-TL and 10PASS-TS PMEs respectively. 497 There are 12 predefined standard profiles for 2BASE-TL and 22 498 standard profiles for 10PASS-TS, defined in 802.3ah and dedicated for 499 rapid provisioning of EFMCu PHYs in most scenarios. An ability to 500 define new configuration profiles is also provided to allow for EFMCu 501 deployment tailored to specific copper environment and spectral 502 regulations. 504 A specific configuration or administrative profile is assigned to a 505 specific PME via efmCuPmeAdminProfile object. If 506 efmCuPmeAdminProfile is zero, then efmCuAdminProfile object of the 507 PCS port, connected to the PME, determines the configuration profile 508 (or a list of possible profiles) for that PME. This mechanism allows 509 to specify a common profile(s) for all PMEs connected to the PCS 510 port, with an ability to change individual PME profiles by setting 511 efmCuPmeAdminProfile objects, which overwrites profile set by 512 efmCuAdminProfile. 514 A current operating PME profile is pointed to by efmCuPmeOperProfile 515 object. Note that this profile entry, can be created automatically, 516 to reflect achieved parameters in adaptive (not fixed) 517 initialization. 519 4.3 Mapping of IEEE 802.3ah Managed Objects 521 This section contains the mapping between managed objects 522 (attributes) defined in [802.3ah] Clause 30, and managed objects 523 defined in this document and in associated MIB modules, i.e., the 524 IF-MIB [RFC2863]. 526 Note that majority of the objects defined in this MIB module do not 527 have direct counterparts in Clause 30 and instead refer to Clause 45 528 registers. 530 *EdNote: It would be a good idea to update Clause 30 of 802.3ah after 531 this MIB module is approved. I guess this should be done via a 532 maintanence request. * 533 +---------------------------------+---------------------------------+ 534 | IEEE 802.3 Managed Object | Corresponding SNMP Object | 535 +---------------------------------+---------------------------------+ 536 | oPAF - Basic Package | | 537 | (Mandatory) | | 538 | aPAFID | ifIndex (IF-MIB) | 539 | aPhyEnd | efmCuPhySide | 540 | aPHYCurrentStatus | efmCuStatus | 541 | aPAFSupported | efmCuPAFSupported | 542 | oPAF - PME Aggregation Package | | 543 | (Optional) | | 544 | aPAFAdminState | efmCuPAFAdminState | 545 | aLocalPAFCapacity | efmCuPAFCapacity | 546 | aLocalPMEAvailable | ifAvailableStackTable | 547 | aLocalPMEAggregate | ifStackTable (IF-MIB) | 548 | aRemotePAFSupported | efmCuRemotePAFSupported | 549 | aRemotePAFCapacity | efmCuRemotePAFCapacity | 550 | aRemotePMEAggregate | | 551 | oPME - 10P/2B Package | | 552 | (Mandatory) | | 553 | aPMEID | ifIndex (IF-MIB) | 554 | aPMEAdminState | ifAdminState (IF-MIB) | 555 | aPMEStatus | efmCuPmeStatus | 556 | aPMESNRMgn | efmCuPmeSnrMgn | 557 | aTCCodingViolations | efmCuPmeTCCodingErrors | 558 | aProfileSelect | efmCuAdminProfile, | 559 | | efmCuPmeAdminProfile | 560 | aOperatingProfile | efmCuPmeOperProfile | 561 | aPMEFECCorrectedBlocks | efmCuPme10PFECCorrectedBlocks | 562 | aPMEFECUncorrectableBlocks | efmCuPme10PFECUncorrectedBlocks | 563 +---------------------------------+---------------------------------+ 565 Table 2 567 5. Definitions 569 EFM-CU-MIB DEFINITIONS ::= BEGIN 571 IMPORTS 572 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32, 573 Unsigned32, Counter32, mib-2 574 FROM SNMPv2-SMI -- [RFC2578] 575 TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress 576 FROM SNMPv2-TC -- [RFC2579] 577 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 578 FROM SNMPv2-CONF -- [RFC2580] 579 SnmpAdminString 580 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 581 ifIndex, ifSpeed, InterfaceIndex 582 FROM IF-MIB -- [RFC2863] 583 ; 585 efmCuMIB MODULE-IDENTITY 586 LAST-UPDATED "200504040000Z" -- April 04, 2005 587 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" 588 CONTACT-INFO 589 "WG charter: 590 http://www.ietf.org/html.charters/hubmib-charter.html 592 Mailing Lists: 593 General Discussion: hubmib@ietf.org 594 To Subscribe: hubmib-request@ietf.org 595 In Body: subscribe your_email_address 597 Chair: Dan Romascanu 598 Postal: Avaya 599 Atidim Technology Park, Bldg. 3 600 Tel Aviv 61131 601 Israel 602 Tel: +972 3 645 8414 603 E-mail: dromasca@avaya.com 605 Editor: Edward Beili 606 Postal: Actelis Networks Inc. 607 25 Bazel St., P.O.B. 10173 608 Petach-Tikva 10173 609 Israel 610 Tel: +972-3-924-3491 611 E-mail: edward.beili@actelis.com" 613 DESCRIPTION 614 "The objects in this MIB module are used to manage 615 the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces 616 2BASE-TL and 10PASS-TS, defined in IEEE Draft P802.3ah/D3.3. 618 The following reference is used throughout this MIB module: 620 [802.3ah] refers to: 621 IEEE Std 802.3ah-2004: 'IEEE Standard for Information 622 technology - Telecommunications and information exchange 623 between systems - Local and metropolitan area networks - 624 Specific requirements - 625 Part 3: Carrier Sense Multiple Access with Collision 626 Detection (CSMA/CD) Access Method and Physical Layer 627 Specifications - 628 Amendment: Media Access Control Parameters, Physical 629 Layers and Management Parameters for Subscriber Access 630 Networks', 07 September 2004. 632 Of particular interest are Clause 61, 'Physical Coding 633 Sublayer (PCS) and common specifications, type 10PASS-TS and 634 type 2BASE-TL', Clause 30, 'Management', Clause 45, 635 'Management Data Input/Output (MDIO) Interface', Annex 62A, 636 'PMD profiles for 10PASS-TS' and Annex 63A, 'PMD profiles for 637 2BASE-TL'. 639 Naming Conventions: 640 Atn - Attenuation 641 CO - Central Office 642 CPE - Customer Premises Equipment 643 EFM - Ethernet in the First Mile 644 EFMCu - EFM Copper 645 MDIO - Management Data Input/Output 646 Mgn - Margin 647 PAF - PME Aggregation Function 648 PCS - Physical Coding Sublayer 649 PMD - Physical Medium Dependent 650 PME - Physical Medium Entity 651 PSD - Power Spectral Density 652 SNR - Signal to Noise Ratio 653 TCPAM - Trellis Coded Pulse Amplitude Modulation 655 Copyright (C) The Internet Society (2004). This version 656 of this MIB module is part of RFC XXXX; see the RFC 657 itself for full legal notices." 659 -- EdNote: Replace XXXX with the actual RFC number & 660 -- remove this note 662 REVISION "200504040000Z" -- April 04, 2005 663 DESCRIPTION "Initial version, published as RFC XXXX." 665 ::= { mib-2 160 } 667 -- EdNote: Replace YYY with a real OID once it is 668 -- allocated & remove this note. 670 -- Sections of the module 672 efmCuObjects OBJECT IDENTIFIER ::= { efmCuMIB 1 } 674 efmCuConformance OBJECT IDENTIFIER ::= { efmCuMIB 2 } 675 -- Groups in the module 677 efmCuPort OBJECT IDENTIFIER ::= { efmCuObjects 1 } 679 efmCuPme OBJECT IDENTIFIER ::= { efmCuObjects 2 } 681 -- Textual Conventions 683 ProfileIndex ::= TEXTUAL-CONVENTION 684 DISPLAY-HINT "d" 685 STATUS current 686 DESCRIPTION 687 "A unique value, greater than zero, for each PME configuration 688 profile in the managed EFMCu port. It is recommended that 689 values are assigned contiguously starting from 1. The value 690 for each profile must remain constant at least from one 691 re-initialization of the entity's network management system 692 to the next re-initialization." 693 SYNTAX Unsigned32 (1..255) 695 ProfileIndexOrZero ::= TEXTUAL-CONVENTION 696 DISPLAY-HINT "d" 697 STATUS current 698 DESCRIPTION 699 "This textual convention is an extension of the ProfileIndex 700 convention. The latter defines a greater than zero value used 701 to identify a PME profile in the managed EFMCu port. This 702 extension permits the additional value of zero. The value of 703 zero is object-specific and must therefore be defined as part 704 of the description of any object which uses this syntax. 705 Examples of the usage of zero value migh include situations 706 where current operational profile is unknown." 707 SYNTAX Unsigned32 (0..255) 709 ProfileIndexList ::= TEXTUAL-CONVENTION 710 DISPLAY-HINT "1d:" 711 STATUS current 712 DESCRIPTION 713 "Represents a list of up to 6 ProfileIndex's. 714 The ProfileIndex textual convention defines a greater than 715 zero value used to identify a PME profile in the managed EFMCu 716 port. The value of this object is a concatenation of one or 717 more (up to 6) octets, where each octet contains an 8-bit 718 ProfileIndex value. 719 The ProfileIndexList specifies a list of alternative 720 profiles, any of which can be chosen for configuration of an 721 PME." 722 SYNTAX OCTET STRING (SIZE(1..6)) 724 TruthValueOrUnknown ::= TEXTUAL-CONVENTION 725 STATUS current 726 DESCRIPTION 727 "This textual convention is an extension of the TruthValue 728 convention. The latter defines a boolean value with 729 possible values of true(1) and false(2). This 730 extension permits the additional value of unknown(0), which 731 can be returned as a result of GET operation, when an exact 732 true or false value of the object cannot be determined." 733 SYNTAX INTEGER { unknown(0), true(1), false(2) } 735 -- Port Notifications Group 737 efmCuPortNotifications OBJECT IDENTIFIER ::= { efmCuPort 0 } 739 efmCuLowBandwidth NOTIFICATION-TYPE 740 OBJECTS { 741 -- ifIndex is not needed here since we are under specific PCS 742 ifSpeed, 743 efmCuThreshLowBandwidth 744 } 745 STATUS current 746 DESCRIPTION 747 "This notification indicates that EFMCu port's data rate 748 reached or dropped below a Low Bandwidth Threshold 749 (i.e. bandwidth degradation happening in case of PAF when one 750 or more PMEs drop)." 751 -- EdNote: add throttling limitations here 752 ::= { efmCuPortNotifications 1 } 754 -- PCS Port group 756 efmCuPortConfTable OBJECT-TYPE 757 SYNTAX SEQUENCE OF EfmCuPortConfEntry 758 MAX-ACCESS not-accessible 759 STATUS current 760 DESCRIPTION 761 "Table for Configuration of EFMCu 2BASE-TL/10PASS-TS (PCS) 762 Ports. Entries in this table MUST be maintained in a 763 persistent manner" 764 ::= { efmCuPort 1 } 766 efmCuPortConfEntry OBJECT-TYPE 767 SYNTAX EfmCuPortConfEntry 768 MAX-ACCESS not-accessible 769 STATUS current 770 DESCRIPTION 771 "An entry in the EFMCu Port Configuration table. 773 Each entry represents an EFMCu port indexed by the ifIndex. 774 Note that an EFMCu PCS port runs on top of a single 775 or multiple PME port(s), which are also indexed by ifIndex." 776 INDEX { ifIndex } 777 ::= { efmCuPortConfTable 1 } 779 EfmCuPortConfEntry ::= 780 SEQUENCE { 781 efmCuPAFAdminState INTEGER, 782 efmCuPAFDiscoveryCode PhysAddress, 783 efmCuAdminProfile ProfileIndexList, 784 efmCuTargetDataRate Unsigned32, 785 efmCuTargetSnrMgn Unsigned32, 786 efmCuThreshLowBandwidth Unsigned32, 787 efmCuLowBandwidthEnable TruthValue 788 } 790 efmCuPAFAdminState OBJECT-TYPE 791 SYNTAX INTEGER { 792 enabled(1), 793 disabled(2) 794 } 795 MAX-ACCESS read-write 796 STATUS current 797 DESCRIPTION 798 "Administrative (desired) state of the PAF of the EFMCu port 799 (PCS). 800 When 'disabled', PME Aggregation will not be performed by the 801 PCS. No more than a single PME can be assigned to this PCS in 802 this case. 803 When 'enabled', PAF will be performed by the PCS when the link 804 is Up, even on a single attached PME, if PAF is supported. 806 PCS ports incapable of supporting PAF SHALL return a value of 807 'disabled'. Attempts to 'enable' such ports SHALL be ignored. 809 PAF 'enabled' port with multiple PMEs assigned cannot be 810 'disabled'. Attempts to 'disable' such port SHALL be rejected, 811 until at most one PME is left assigned. 813 Changing PAFAdminState is a traffic disruptive operation and 814 as such SHALL be done when the link is Down. Attempts to 815 change this object SHALL be ignored if the link is Up or 816 Initializing. 818 This object maps to the Clause 30 attribute aPAFAdminState. 820 If a Clause 45 MDIO Interface to the PCS is present, then this 821 object maps to the PAF enable bit in the 10P/2B PCS control 822 register. 824 This object MUST be maintained in a persistent manner." 825 REFERENCE 826 "[802.3ah] 61.2.2, 45.2.3.18.3" 827 ::= { efmCuPortConfEntry 1 } 829 efmCuPAFDiscoveryCode OBJECT-TYPE 830 SYNTAX PhysAddress 831 MAX-ACCESS read-write 832 STATUS current 833 DESCRIPTION 834 "PAF Discovery Code of the EFMCu port (PCS). 835 A unique 6 Byte long code used by the Discovery function, when 836 PAF is supported. 837 PCS ports incapable of supporting PAF SHALL return a value of 838 all zeroes. Attempts to change this object SHALL be ignored in 839 this case. 840 This object MUST be instantiated for the -O subtype PCS before 841 writing operations on the efmCuPAFRemoteDiscoveryCode 842 (Set_if_Clear and Clear_if_Same) are performed by PMEs 843 associated with the PCS. 844 The value of this object is read-only for -R port subtypes. 845 The initial value of this object for -R ports after reset 846 is 0. This value may be changed as a result of writing 847 operation on efmCuPAFRemoteDiscoveryCode variable of remote 848 PME of -O subtype, connected to one of the local PMEs 849 associated with the PCS. 851 Discovery MUST be performed when the link is Down. 852 Attempts to change this object MUST be rejected with the error 853 inconsistentValue if the link is Up or Initializing. 855 The PAF Discovery code maps to the local Discovery code 856 variable in PAF (note that it does not have a corresponding 857 Clause 45 register)" 858 REFERENCE 859 "[802.3ah] 61.2.2.8.3, 61.2.2.8.4, 45.2.6.6.1" 860 ::= { efmCuPortConfEntry 2 } 862 efmCuAdminProfile OBJECT-TYPE 863 SYNTAX ProfileIndexList 864 MAX-ACCESS read-write 865 STATUS current 866 DESCRIPTION 867 "Desired configuration Profile(s), common for all PMEs in the 868 EFMCu port. This object is a list of pointers to entries in 869 either efmCuPme2BProfileTable or 870 efmCuPme10PProfileTable, depending on the current 871 operating SubType of the EFMCu port as indicated by 872 efmCuPortSide. 873 The value of this object is a list of up to 6 indices of 874 Profiles. If this list consists of a single Profile index, 875 then all PMEs assigned to this EFMCu port SHALL be configured 876 according to the Profile referenced by that index, unless it 877 is overwritten by corresponding non-zero efmCuPmeAdminProfile, 878 which takes precedence over efmCuAdminProfile. 879 The list, consisting of more than one index, allows each PME 880 in the port to be configured according to any Profile 881 specified in the list. 882 By default this object has a single profile index 1, 883 referencing 1st entry in efmCuPme2BProfileTable/ 884 efmCuPme2BProfileTable. 886 This object is writable and readable for the -O subtype 887 (2BaseTL-O or 10PassTS-O) EFMCu ports. It is unavailable for 888 the -R subtype (2BaseTL-R or 10PassTS-R) ports. 890 Note that current operational Profile value is available via 891 efmCuPmeOperProfile object. 893 Modification of this object must be performed when the link is 894 Down. Attempts to change this object MUST be rejected, if the 895 link is Up or Initializing. 896 Attempts to set this object to a list with a member 897 value, that is not the value of the index for an active entry 898 in the corresponding profile table, MUST be rejected. 900 This object MUST be maintained in a persistent manner." 901 REFERENCE 902 "[802.3ah] 30.11.2.1.6" 903 DEFVAL { '01'H } 904 ::= { efmCuPortConfEntry 3 } 906 efmCuTargetDataRate OBJECT-TYPE 907 SYNTAX Unsigned32(1..100000|999999) 908 UNITS "Kbps" 909 MAX-ACCESS read-write 910 STATUS current 911 DESCRIPTION 912 "Desired EFMCu port 'net' (as seen across MII) Data Rate in 913 Kbps, to be achieved during initialization, under spectral 914 restrictions placed on each PME via efmCuAdminProfile or 915 efmCuPmeAdminProfile, with the desired SNR Margin specified by 916 efmCuTargetSnrMgn. 918 In case of PAF, this object represents a sum of individual PME 919 data rates, modified to compensate for fragmentation and 920 64/65B framing overhead (e.g. target data rate of 10Mbps 921 shall allow lossless transmission of full-duplex 10Mbps 922 Ethernet frame stream with minimal inter-frame gap). 924 The value is limited above by 100Mbps as this is the max 925 burst rate across MII for EFMCu ports. 927 The value between 1 and 100000 indicates that the total data 928 rate (ifSpeed) of the EFMCu port after initialization should 929 be equal to the target data rate or less, if the target data 930 rate cannot be achieved under spectral restrictions specified 931 by efmCuAdminProfile/efmCuPmeAdminProfile and with desired SNR 932 margin. In case the copper environment allows to achieve 933 higher total data rate than specified by the target, the 934 excess capability SHALL be converted to additional SNR margin 935 and spread evenly across all active PMEs assigned to the (PCS) 936 port. 938 The value of 999999 means that the target data rate is not 939 fixed and should be set to the maximum attainable rate during 940 initialization (Best Effort), under specified spectral 941 restrictions and with desired SNR Margin. 943 This object is read-write for the -O subtype EFMCu ports 944 (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. 946 Changing of the Target Data Rate MUST be performed when the 947 link is Down. Attempts to change this object MUST be rejected 948 with the error inconsistentValue, if the link is Up or 949 Initializing. 951 Note that current Data Rate of the EFMCu port is represented 952 by ifSpeed object of IF-MIB. 954 This object MUST be maintained in a persistent manner." 955 ::= { efmCuPortConfEntry 4 } 957 efmCuTargetSnrMgn OBJECT-TYPE 958 SYNTAX Unsigned32(0..21) 959 UNITS "dB" 960 MAX-ACCESS read-write 961 STATUS current 962 DESCRIPTION 963 "Desired EFMCu port SNR Margin to be achieved on all PMEs 964 assigned to the port, during initializiation. (The SNR margin 965 is the difference between the desired SNR and the actual SNR). 967 Note that 802.3ah recommends using default Target SNR Margin 968 of 5dB for 2BASE-TL ports and 6dB for 10PASS-TS ports in order 969 to achieve mean Bit Error Rate (BER) of 10^-7 at the PMA 970 service interface. 972 This object is read-write for the -O subtype EFMCu ports 973 (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. 975 Changing of the Target SNR Margin MUST be performed when the 976 link is Down. Attempts to change this object MUST be rejected 977 with the error inconsistentValue, if the link is Up or 978 Initializing. 980 Note that current SNR Margin of the PMEs comprising the EFMCu 981 port is represented by efmCuPmeSnrMgn. 983 This object MUST be maintained in a persistent manner." 984 REFERENCE 985 "[802.3ah] 61.1.2" 986 ::= { efmCuPortConfEntry 5 } 988 efmCuThreshLowBandwidth OBJECT-TYPE 989 SYNTAX Unsigned32(0..100000) 990 UNITS "Kbps" 991 MAX-ACCESS read-write 992 STATUS current 993 DESCRIPTION 994 "This object configures the EFMCu port Low Bandwidth alarm 995 threshold. When the current value of ifSpeed for this port 996 reaches or drops below this threshold, an 997 efmCuLowBandwidth notification MAY be generated if enabled by 998 efmCuLowBandwidthEnable. 1000 The value of 0 means no efmCuLowBandwidth notifications 1001 SHALL ever be generated. 1003 This object is read-write for the -O subtype EFMCu ports 1004 (2BaseTL-O/10PassTS-O) and not available for the -R subtypes. 1006 This object MUST be maintained in a persistent manner." 1007 ::= { efmCuPortConfEntry 6 } 1009 efmCuLowBandwidthEnable OBJECT-TYPE 1010 SYNTAX TruthValue 1011 MAX-ACCESS read-write 1012 STATUS current 1013 DESCRIPTION 1014 "Indicates whether efmCuLowBandwidth notifications should be 1015 generated for this interface. 1017 Value of true(1) indicates that efmCuLowBandwidth 1018 notification is enabled. Value of false(2) indicates that 1019 the notification is disabled. 1021 This object MUST be maintained in a persistent manner." 1022 ::= { efmCuPortConfEntry 7 } 1024 efmCuPortCapabilityTable OBJECT-TYPE 1025 SYNTAX SEQUENCE OF EfmCuPortCapabilityEntry 1026 MAX-ACCESS not-accessible 1027 STATUS current 1028 DESCRIPTION 1029 "Table for Capabilities of EFMCu 2BASE-TL/10PASS-TS (PCS) 1030 Ports. Entries in this table MUST be maintained in a 1031 persistent manner" 1032 ::= { efmCuPort 2 } 1034 efmCuPortCapabilityEntry OBJECT-TYPE 1035 SYNTAX EfmCuPortCapabilityEntry 1036 MAX-ACCESS not-accessible 1037 STATUS current 1038 DESCRIPTION 1039 "An entry in the EFMCu Port Capability table. 1040 Each entry represents an EFMCu port indexed by the ifIndex. 1041 Note that an EFMCu PCS port runs on top of a single 1042 or multiple PME port(s), which are also indexed by ifIndex." 1043 INDEX { ifIndex } 1044 ::= { efmCuPortCapabilityTable 1 } 1046 EfmCuPortCapabilityEntry ::= 1047 SEQUENCE { 1048 efmCuPAFSupported TruthValue, 1049 efmCuPeerPAFSupported TruthValueOrUnknown, 1050 efmCuPAFCapacity Unsigned32, 1051 efmCuPeerPAFCapacity Unsigned32 1052 } 1054 efmCuPAFSupported OBJECT-TYPE 1055 SYNTAX TruthValue 1056 MAX-ACCESS read-only 1057 STATUS current 1058 DESCRIPTION 1059 "PME Aggregation Function (PAF) Capability of the EFMCu port 1060 (PCS). 1061 This object has a value of true(1) when the PCS can perform 1062 PME aggregation on the available PMEs. 1063 Ports incapable of PAF SHALL return a value of false(2). 1065 This object maps to the Clause 30 attribute aPAFSupported. 1067 If a Clause 45 MDIO Interface to the PCS is present, 1068 then this object maps to the PAF available bit in the 1069 10P/2B capability register." 1070 REFERENCE 1071 "[802.3ah] 61.2.2, 30.11.1.1.4, 45.2.3.17.1" 1072 ::= { efmCuPortCapabilityEntry 1 } 1074 efmCuPeerPAFSupported OBJECT-TYPE 1075 SYNTAX TruthValueOrUnknown 1076 MAX-ACCESS read-only 1077 STATUS current 1078 DESCRIPTION 1079 "PME Aggregation Function (PAF) Capability of the EFMCu port 1080 (PCS) link partner. 1081 This object has a value of true(1) when the remote PCS can 1082 perform PME aggregation on its available PMEs. 1083 Ports whose peers are incapable of PAF, SHALL return a value 1084 of false(2). 1085 Ports whose peers cannot be reached because of the link 1086 state, SHALL return a value if unknown(0). 1088 This object maps to the Clause 30 attribute 1089 aRemotePAFSupported. 1091 If a Clause 45 MDIO Interface to the PCS is present, then 1092 this object maps to the Remote PAF supported bit in the 1093 10P/2B capability register." 1094 REFERENCE 1095 "[802.3ah] 61.2.2, 30.11.1.1.9, 45.2.3.17.2" 1096 ::= { efmCuPortCapabilityEntry 2 } 1098 efmCuPAFCapacity OBJECT-TYPE 1099 SYNTAX Unsigned32 (1..32) 1100 MAX-ACCESS read-only 1101 STATUS current 1102 DESCRIPTION 1103 "Number of PMEs that can be aggregated by the local PAF. 1104 The number of PMEs currently assigned to a particular 1105 EFMCu port (efmCuNumPMEs) is never greater than 1106 efmCuPAFCapacity. 1108 This object maps to the Clause 30 attribute 1109 aLocalPAFCapacity." 1111 REFERENCE 1112 "[802.3ah] 61.2.2, 30.11.1.1.6" 1113 ::= { efmCuPortCapabilityEntry 3 } 1115 efmCuPeerPAFCapacity OBJECT-TYPE 1116 SYNTAX Unsigned32 (0|1..32) 1117 MAX-ACCESS read-only 1118 STATUS current 1119 DESCRIPTION 1120 "Number of PMEs that can be aggregated by the PAF of the peer 1121 Phy (PCS port). 1122 Value of 0 is returned when peer PAF Capacity is unknown 1123 (peer cannot be reached). 1125 This object maps to the Clause 30 attribute 1126 aRemotePAFCapacity." 1127 REFERENCE 1128 "[802.3ah] 61.2.2, 30.11.1.1.10" 1129 ::= { efmCuPortCapabilityEntry 4 } 1131 efmCuPortStatusTable OBJECT-TYPE 1132 SYNTAX SEQUENCE OF EfmCuPortStatusEntry 1133 MAX-ACCESS not-accessible 1134 STATUS current 1135 DESCRIPTION 1136 "This table provides overall status information of EFMCu 1137 2BASE-TL/10PASS-TS ports. This table contains live data from 1138 the equipment. As such, it is NOT persistent." 1139 ::= { efmCuPort 3 } 1141 efmCuPortStatusEntry OBJECT-TYPE 1142 SYNTAX EfmCuPortStatusEntry 1143 MAX-ACCESS not-accessible 1144 STATUS current 1145 DESCRIPTION 1146 "An entry in the EFMCu Port Status table. 1147 Each entry represents an EFMCu port indexed by the ifIndex. 1148 Note that an EFMCu PCS port runs on top of a single 1149 or multiple PME port(s), which are also indexed by ifIndex." 1150 INDEX { ifIndex } 1151 ::= { efmCuPortStatusTable 1 } 1153 EfmCuPortStatusEntry ::= 1154 SEQUENCE { 1155 efmCuFltStatus BITS, 1156 efmCuPortSide INTEGER, 1157 efmCuNumPMEs Unsigned32, 1158 efmCuPAFInErrors Counter32, 1159 efmCuPAFInSmallFragments Counter32, 1160 efmCuPAFInLargeFragments Counter32, 1161 efmCuPAFInBadFragments Counter32, 1162 efmCuPAFInLostFragments Counter32, 1163 efmCuPAFInLostStarts Counter32, 1164 efmCuPAFInLostEnds Counter32, 1165 efmCuPAFInOverflows Counter32 1166 } 1168 efmCuFltStatus OBJECT-TYPE 1169 SYNTAX BITS { 1170 noPeer(0), 1171 pmeSubTypeMismatch(1), 1172 lowBandwidth(2) 1173 } 1174 MAX-ACCESS read-only 1175 STATUS current 1176 DESCRIPTION 1177 "EFMCu (PCS) port Fault Status. This is a bitmap of possible 1178 conditions. The various bit positions are: 1179 noPeer - peer PHY cannot be reached (e.g. 1180 no PMEs attached, all PMEs are Down 1181 etc.) More info is available in 1182 efmCuPmeFltStatus. 1183 pmeSubTypeMismatch - local PMEs in the aggregation group 1184 are not of the same sub-type, e.g. 1185 some PMEs in the local device are -O 1186 while others are -R subtype. 1187 lowBandwidth - ifSpeed of the port reached or droped 1188 below efmCuThreshLowBandwidth 1190 This object is intended to supplement ifOperStatus object 1191 in IF-MIB. 1192 Additional information is available via efmCuPmeFltStatus 1193 object for each PME in the aggregation group (single PME if 1194 PAF is disabled)." 1195 REFERENCE 1196 "ifOperStatus in IF-MIB; efmCuPmeFltStatus" 1197 ::= { efmCuPortStatusEntry 1 } 1199 efmCuPortSide OBJECT-TYPE 1200 SYNTAX INTEGER { 1201 subscriber(1), 1202 office(2), 1203 unknown(3) 1204 } 1205 MAX-ACCESS read-only 1206 STATUS current 1207 DESCRIPTION 1208 "EFM port mode of operation (subtype). 1209 The value of 'subscriber' indicates the port is designated as 1210 '-R' subtype (all PMEs assigned to this port are of subtype 1211 '-R'). 1212 The value of the 'office' indicates that the port is 1213 designated as '-O' subtype (all PMEs assigned to this port are 1214 of subtype '-O'). 1215 The value of 'unknown' indicates that the port has no assigned 1216 PMEs yet or that the assigned PMEs are not of the same side 1217 (subTypePMEMismatch). 1219 This object partially maps to the Clause 30 attribute 1220 aPhyEnd" 1221 REFERENCE 1222 "[802.3ah] 61.1, 30.11.1.1.2" 1223 ::= { efmCuPortStatusEntry 2 } 1225 efmCuNumPMEs OBJECT-TYPE 1226 SYNTAX Unsigned32 (0..32) 1227 MAX-ACCESS read-only 1228 STATUS current 1229 DESCRIPTION 1230 "Number of PMEs that is currently aggregated by the local PAF 1231 (assigned to the EFMCu port using ifStackTable). 1232 This number is never greater than efmCuPAFCapacity. 1234 This object SHALL be automatically incremented or decremented 1235 when a PME is added or deleted to/from the EFMCu port using 1236 ifStackTable." 1237 REFERENCE 1238 "[802.3ah] 61.2.2, 30.11.1.1.6" 1239 ::= { efmCuPortStatusEntry 3 } 1241 efmCuPAFInErrors OBJECT-TYPE 1242 SYNTAX Counter32 1243 MAX-ACCESS read-only 1244 STATUS current 1245 DESCRIPTION 1246 "A number of fragments that have been received across the 1247 gamma interface with RxErr asserted and discarded. 1248 This read-only counter is inactive (not incremented) when the 1249 PAF is unsupported or disabled. Upon disabling the PAF, the 1250 counter retains its previous value. 1252 If a Clause 45 MDIO Interface to the PCS is present, then 1253 this object maps to the 10P/2B PAF RX error register." 1255 REFERENCE 1256 "[802.3ah] 45.2.3.21" 1257 ::= { efmCuPortStatusEntry 4 } 1259 efmCuPAFInSmallFragments OBJECT-TYPE 1260 SYNTAX Counter32 1261 MAX-ACCESS read-only 1262 STATUS current 1263 DESCRIPTION 1264 "A number of fragments smaller than minFragmentSize 1265 (64 Bytes), that have been received across the gamma interface 1266 and discarded. 1267 This read-only counter is inactive when the PAF is 1268 unsupported or disabled. Upon disabling the PAF, the counter 1269 retains its previous value. 1271 If a Clause 45 MDIO Interface to the PCS is present, then 1272 this object maps to the 10P/2B PAF small fragments 1273 register." 1274 REFERENCE 1275 "[802.3ah] 45.2.3.22" 1276 ::= { efmCuPortStatusEntry 5 } 1278 efmCuPAFInLargeFragments OBJECT-TYPE 1279 SYNTAX Counter32 1280 MAX-ACCESS read-only 1281 STATUS current 1282 DESCRIPTION 1283 "A number of fragments larger than maxFragmentSize 1284 (512 Bytes), that have been received across the gamma 1285 interface and discarded. 1286 This read-only counter is inactive when the PAF is 1287 unsupported or disabled. Upon disabling the PAF, the counter 1288 retains its previous value. 1290 If a Clause 45 MDIO Interface to the PCS is present, then 1291 this object maps to the 10P/2B PAF large fragments 1292 register." 1293 REFERENCE 1294 "[802.3ah] 45.2.3.23" 1295 ::= { efmCuPortStatusEntry 6 } 1297 efmCuPAFInBadFragments OBJECT-TYPE 1298 SYNTAX Counter32 1299 MAX-ACCESS read-only 1300 STATUS current 1301 DESCRIPTION 1302 "A number of fragments which do not fit into the sequence 1303 expected by the frame assembly function, that have been 1304 received across the gamma interface and discarded (the 1305 frame buffer is flushed to the next valid frame start). 1306 This read-only counter is inactive when the PAF is 1307 unsupported or disabled. Upon disabling the PAF, the counter 1308 retains its previous value. 1310 If a Clause 45 MDIO Interface to the PCS is present, then 1311 this object maps to the 10P/2B PAF bad fragments 1312 register." 1313 REFERENCE 1314 "[802.3ah] 45.2.3.25" 1315 ::= { efmCuPortStatusEntry 7 } 1317 efmCuPAFInLostFragments OBJECT-TYPE 1318 SYNTAX Counter32 1319 MAX-ACCESS read-only 1320 STATUS current 1321 DESCRIPTION 1322 "A number of gaps in the sequence of fragments, that have been 1323 received across the gamma interface (the frame buffer is 1324 flushed to the next valid frame start, when fragment/fragments 1325 expected by the frame assembly function is/are not received). 1326 This read-only counter is inactive when the PAF is 1327 unsupported or disabled. Upon disabling the PAF, the counter 1328 retains its previous value. 1330 If a Clause 45 MDIO Interface to the PCS is present, then 1331 this object maps to the 10P/2B PAF lost fragment 1332 register." 1333 REFERENCE 1334 "[802.3ah] 45.2.3.26" 1335 ::= { efmCuPortStatusEntry 8 } 1337 efmCuPAFInLostStarts OBJECT-TYPE 1338 SYNTAX Counter32 1339 MAX-ACCESS read-only 1340 STATUS current 1341 DESCRIPTION 1342 "A number of missing StartOfPacket indicators expected by the 1343 frame assembly function. 1344 This read-only counter is inactive when the PAF is 1345 unsupported or disabled. Upon disabling the PAF, the counter 1346 retains its previous value. 1348 If a Clause 45 MDIO Interface to the PCS is present, then 1349 this object maps to the 10P/2B PAF lost start of fragment 1350 register." 1352 REFERENCE 1353 "[802.3ah] 45.2.3.27" 1354 ::= { efmCuPortStatusEntry 9 } 1356 efmCuPAFInLostEnds OBJECT-TYPE 1357 SYNTAX Counter32 1358 MAX-ACCESS read-only 1359 STATUS current 1360 DESCRIPTION 1361 "A number of missing EndOfPacket indicators expected by the 1362 frame assembly function. 1363 This read-only counter is inactive when the PAF is 1364 unsupported or disabled. Upon disabling the PAF, the counter 1365 retains its previous value. 1367 If a Clause 45 MDIO Interface to the PCS is present, then 1368 this object maps to the 10P/2B PAF lost start of fragment 1369 register." 1370 REFERENCE 1371 "[802.3ah] 45.2.3.28" 1372 ::= { efmCuPortStatusEntry 10 } 1374 efmCuPAFInOverflows OBJECT-TYPE 1375 SYNTAX Counter32 1376 MAX-ACCESS read-only 1377 STATUS current 1378 DESCRIPTION 1379 "A number of fragements, received accross the gamma interface 1380 and discarded, which would have caused the frame assembly 1381 buffer to overflow. 1382 This read-only counter is inactive when the PAF is 1383 unsupported or disabled. Upon disabling the PAF, the counter 1384 retains its previous value. 1386 If a Clause 45 MDIO Interface to the PCS is present, then 1387 this object maps to the 10P/2B PAF overflow register." 1388 REFERENCE 1389 "[802.3ah] 45.2.3.24" 1390 ::= { efmCuPortStatusEntry 11 } 1392 -- PME Notifications Group 1394 efmCuPmeNotifications OBJECT IDENTIFIER ::= { efmCuPme 0 } 1396 -- EdNote: Should I add more notifications here, for example 1397 -- efmCuPmePerfES, 1398 -- efmCuPmePerfSES, 1399 -- efmCuPmePerfCRCanomalies, 1400 -- efmCuPmePerfLOSWS, 1401 -- efmCuPmePerfUAS, 1402 -- efmCuPmeDeviceFault, 1403 -- efmCuPmeLocalPowerLoss 1404 -- Another option would be to reference HDSL2-SHDSL-LINE-MIB 1405 -- or VDSL-LINE-EXT-MCM-MIB, reusing notifications defined there. 1407 efmCuPmeLineAtnCrossing NOTIFICATION-TYPE 1408 OBJECTS { 1409 efmCuPmeLineAtn, 1410 efmCuPmeThreshLineAtn 1411 } 1412 STATUS current 1413 DESCRIPTION 1414 "This notification indicates that the loop attenuation 1415 threshold (as per the efmCuPmeThreshLineAtn 1416 value) has been reached/exceeded for the 2BASE-TL/10PASS-TS 1417 PME. This notification MAY be send on the crossing event in 1418 both directions: from normal to exceeded and from exceeded 1419 to normal. 1421 Generation of this notification is controlled by the 1422 efmCuPmeLineAtnCrossingEnable object." 1423 -- EdNote: add throttling limitations here, with 10 sec 1424 -- debouncing on clear to prevenmt intermittent alarms 1425 ::= { efmCuPmeNotifications 1 } 1427 efmCuPmeSnrMgnCrossing NOTIFICATION-TYPE 1428 OBJECTS { 1429 efmCuPmeSnrMgn, 1430 efmCuPmeThreshSnrMgn 1431 } 1432 STATUS current 1433 DESCRIPTION 1434 "This notification indicates that the SNR margin threshold 1435 (as per the efmCuPmeThreshSnrMgn value) has been 1436 reached/exceeded for the 2BASE-TL/10PASS-TS PME. 1437 This notification MAY be send on the crossing event in 1438 both directions: from normal to exceeded and from exceeded 1439 to normal. 1441 Generation of this notification is controlled by the 1442 efmCuPmeSnrMgnCrossingEnable object." 1443 -- EdNote: add throttling limitations here, with 10 sec 1444 -- debouncing on clear to prevenmt intermittent alarms 1445 ::= { efmCuPmeNotifications 2 } 1447 efmCuPmeDeviceFault NOTIFICATION-TYPE 1448 OBJECTS { 1449 efmCuPmeFltStatus 1450 } 1451 STATUS current 1452 DESCRIPTION 1453 "This notification indicates that a fault in the PME has been 1454 detected by a vendor specific diagnostic or a self-test. 1456 Generation of this notification is controlled by the 1457 efmCuPmeDeviceFaultEnable object." 1458 ::= { efmCuPmeNotifications 3 } 1460 efmCuPmeConfigInitFailure NOTIFICATION-TYPE 1461 OBJECTS { 1462 efmCuPmeFltStatus, 1463 efmCuAdminProfile, 1464 efmCuPmeAdminProfile 1465 } 1466 STATUS current 1467 DESCRIPTION 1468 "This notification indicates that PME initialization has 1469 failed, due to inability of the PME link to achieve requested 1470 configuration profile. 1472 Generation of this notification is controlled by the 1473 efmCuPmeConfigInitFailEnable object." 1474 ::= { efmCuPmeNotifications 4 } 1476 efmCuPmeProtocolInitFailure NOTIFICATION-TYPE 1477 OBJECTS { 1478 efmCuPmeFltStatus, 1479 efmCuPmeOperSubType 1480 } 1481 STATUS current 1482 DESCRIPTION 1483 "This notification indicates that peer PME was using 1484 incompatible protocol during initialization. 1486 Generation of this notification is controlled by the 1487 efmCuPmeProtocolInitFailEnable object." 1488 ::= { efmCuPmeNotifications 5 } 1490 -- The PME group 1492 efmCuPmeConfTable OBJECT-TYPE 1493 SYNTAX SEQUENCE OF EfmCuPmeConfEntry 1494 MAX-ACCESS not-accessible 1495 STATUS current 1496 DESCRIPTION 1497 "Table for Configuration of common aspects for EFMCu 1498 2BASE-TL/10PASS-TS PME ports (modems). Configuration of 1499 aspects specific to 2BASE-TL or 10PASS-TS PME types is 1500 represented in efmCuPme2BConfTable and efmCuPme10PConfTable 1501 respectively. 1503 Entries in this table MUST be maintained in a persistent 1504 manner." 1505 ::= { efmCuPme 1 } 1507 efmCuPmeConfEntry OBJECT-TYPE 1508 SYNTAX EfmCuPmeConfEntry 1509 MAX-ACCESS not-accessible 1510 STATUS current 1511 DESCRIPTION 1512 "An entry in the EFMCu PME Configuration table. 1513 Each entry represents common aspects of an EFMCu PME port 1514 indexed by the ifIndex. Note that an EFMCu PME port can be 1515 stacked below a single PCS port, also indexed by ifIndex, 1516 possibly together with other PME ports if PAF is enabled." 1517 INDEX { ifIndex } 1518 ::= { efmCuPmeConfTable 1 } 1520 EfmCuPmeConfEntry ::= 1521 SEQUENCE { 1522 efmCuPmeAdminSubType INTEGER, 1523 efmCuPmeAdminProfile ProfileIndexOrZero, 1524 efmCuPAFRemoteDiscoveryCode PhysAddress, 1525 efmCuPmeThreshLineAtn Integer32, 1526 efmCuPmeThreshSnrMgn Integer32, 1527 efmCuPmeLineAtnCrossingEnable TruthValue, 1528 efmCuPmeSnrMgnCrossingEnable TruthValue, 1529 efmCuPmeDeviceFaultEnable TruthValue, 1530 efmCuPmeConfigInitFailEnable TruthValue, 1531 efmCuPmeProtocolInitFailEnable TruthValue 1532 } 1534 efmCuPmeAdminSubType OBJECT-TYPE 1535 SYNTAX INTEGER { 1536 ieee2BaseTLO(1), 1537 ieee2BaseTLR(2), 1538 ieee10PassTSO(3), 1539 ieee10PassTSR(4), 1540 ieee2BaseTLor10PassTSR(5), 1541 ieee2BaseTLor10PassTSO(6), 1542 ieee10PassTSor2BaseTLO(7) 1543 } 1544 MAX-ACCESS read-write 1545 STATUS current 1546 DESCRIPTION 1547 "Administrative (desired) sub-type of the PME. 1548 Possible values are: 1549 ieee2BaseTLO - PME shall operate as 2BaseTL-O 1550 ieee2BaseTLR - PME shall operate as 2BaseTL-R 1551 ieee10PassTSO - PME shall operate as 10PassTS-O 1552 ieee10PassTSR - PME shall operate as 10PassTS-R 1553 ieee2BaseTLor10PassTSR - PME shall operate as 2BaseTL-R or 1554 10PassTS-R. Actual value will be 1555 set by -O link partner during 1556 initialization (handshake). 1557 ieee2BaseTLor10PassTSO - PME shall operate as 2BaseTL-O 1558 (preferred) or 10PassTS-O. Actual 1559 value will be set during 1560 initialization depending on -R 1561 link partner capability (i.e. if 1562 -R is incapable of the preferred 1563 2BaseTL mode, 10PassTS will be 1564 used). 1565 ieee10PassTSor2BaseTLO - PME shall operate as 10PassTS-O 1566 (preferred) or 2BaseTL-O. Actual 1567 value will be set during 1568 initialization depending on -R 1569 link partner capability (i.e. if 1570 -R is incapable of the preferred 1571 10PassTS mode, 2BaseTL will be 1572 used). 1574 Changing efmCuPmeAdminSubType is a traffic disruptive 1575 operation and as such SHALL be done when the link is Down. 1576 Attempts to change this object SHALL be ignored if the link 1577 is Up or Initializing. 1578 Attempts to change this object to an unsupported subtype 1579 (see efmCuPmeSubTypesSupported) SHALL be rejected. 1581 The current operational sub type is indicated by 1582 efmCuPmeOperSubType variable. 1584 If a Clause 45 MDIO Interface to the PMA/PMD is present, then 1585 this object combines values of the Port sub-type select 1586 bits and the PMA/PMD type selection bits in the 10P/2B 1587 PMA/PMD control register" 1588 REFERENCE 1589 "[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7" 1590 ::= { efmCuPmeConfEntry 1 } 1592 efmCuPmeAdminProfile OBJECT-TYPE 1593 SYNTAX ProfileIndexOrZero 1594 MAX-ACCESS read-write 1595 STATUS current 1596 DESCRIPTION 1597 "Desired PME configuration Profile. This object is a pointer 1598 to an entry in either efmCuPme2BProfileTable or 1599 efmCuPme10PProfileTable, depending on the current 1600 operating SubType of the PME. The value of this object is the 1601 index of the referenced profile. 1602 The value of zero (default) indicates that the PME is 1603 configured via efmCuAdminProfile object for the PCS port, 1604 to which this PME is assigned. That is, the profile referenced 1605 by efmCuPmeAdminProfile takes precedence over the profile(s) 1606 referenced by efmCuAdminProfile. 1608 This object is writable and readable for the CO subtype PMEs 1609 (2BaseTL-O or 10PassTS-O). It is unavailable for the CPE 1610 subtype (2BaseTL-R or 10PassTS-R). 1612 Note that current operational Profile value is available via 1613 efmCuPmeOperProfile object. 1615 Modification of this object must be performed when the link is 1616 Down. Attempts to change this object MUST be rejected, if the 1617 link is Up or Initializing. 1618 Attempts to set this object to a value that is not the 1619 value of the index for an active entry in the corresponding 1620 profile table, MUST be rejected." 1621 REFERENCE 1622 "[802.3ah] 30.11.2.1.6" 1623 DEFVAL { 0 } 1624 ::= { efmCuPmeConfEntry 2 } 1626 efmCuPAFRemoteDiscoveryCode OBJECT-TYPE 1627 SYNTAX PhysAddress 1628 MAX-ACCESS read-write 1629 STATUS current 1630 DESCRIPTION 1631 "PAF Remote Discovery Code of the PME port at CO. 1632 A 6 Byte long Discovery Code of the peer PCS connected via 1633 the PME. 1634 Reading this object results in a Discovery Get operation. 1635 Writing a zero to this object results in a Discovery 1636 Clear_if_Same operation (the value of efmCuPAFDiscoveryCode 1637 at the peer PCS shall be the same as efmCuPAFDiscoveryCode of 1638 the local PCS associated with the PME for the operation to 1639 succeed). 1641 Writing a non-zero value to this object results in a 1642 Discovery Set_if_Clear operation. 1643 This object does not exist in CPE port subtypes. A zero length 1644 octet string SHALL be returned for CPE port subtypes and also 1645 when PAF aggregation is not enabled. 1647 Discovery MUST be performed when the link is Down. 1648 Attempts to change this object MUST be rejected with the error 1649 inconsistentValue, if the link is Up or Initializing. 1651 If a Clause 45 MDIO Interface to the PMA/PMD is present, then 1652 this object is a function of 10P/2B aggregation discovery 1653 control register, Discovery operation result bits in 10P/2B 1654 aggregation and discovery status register and 1655 10P/2B aggregation discovery code register" 1656 REFERENCE 1657 "[802.3ah] 61.2.2.8.4, 45.2.6.6-45.2.6.8" 1658 ::= { efmCuPmeConfEntry 3 } 1660 efmCuPmeThreshLineAtn OBJECT-TYPE 1661 SYNTAX Integer32(-127..128) 1662 UNITS "dB" 1663 MAX-ACCESS read-write 1664 STATUS current 1665 DESCRIPTION 1666 "Desired Line Attenuation Threshold for the 2B/10P PME. 1667 This object configures the line attenuation alarm threshold. 1668 When the current value of Line Attenuation reaches or 1669 exceeds this threshold, a efmCuPmeLineAtnCrossing 1670 notification MAY be generated, if enabled by 1671 efmCuPmeLineAtnCrossingEnable. 1673 This object is writable for the CO subtype PMEs (-O). 1674 It is read-only for the CPE subtype (-R). 1676 Changing of the Line Attenuation Threshold must be performed 1677 when the link is Down. Attempts to change this object MUST be 1678 rejected with the error inconsistentValue, if the link is Up 1679 or Initializing. 1681 If a Clause 45 MDIO Interface to the PME is present, then this 1682 object will map to the Loop attenuation threshold bits in 1683 the 2B PMD line quality thresholds register" 1684 REFERENCE 1685 "[802.3ah] 45.2.1.36" 1686 ::= { efmCuPmeConfEntry 4 } 1688 efmCuPmeThreshSnrMgn OBJECT-TYPE 1689 SYNTAX Integer32(-127..128) 1690 UNITS "dB" 1691 MAX-ACCESS read-write 1692 STATUS current 1693 DESCRIPTION 1694 "Desired SNR Margin Threshold for the 2B/10P PME. 1695 This object configures the SNR margin alarm threshold. 1696 When the current value of SNR Margin reaches 1697 or exceeds this threshold, a efmCuPmeSnrMgnCrossing 1698 notification MAY be generated, if enabled by 1699 efmCuPmeSnrMgnCrossingEnable. 1701 This object is writable for the CO subtype PMEs 1702 (2BaseTL-O/10PassTS-R). It is read-only for the CPE subtype 1703 (2BaseTL-R/10PassTS-R). 1705 Changing of the SNR Margin Threshold must be performed when 1706 the link is Down. Attempts to change this object MUST be 1707 rejected with the error inconsistentValue, if the link is Up 1708 or Initializing. 1710 If a Clause 45 MDIO Interface to the PME is present, then this 1711 object will map to the SNR margin threshold bits in the 1712 2B PMD line quality thresholds register" 1713 REFERENCE 1714 "[802.3ah] 45.2.1.36" 1715 ::= { efmCuPmeConfEntry 5 } 1717 efmCuPmeLineAtnCrossingEnable OBJECT-TYPE 1718 SYNTAX TruthValue 1719 MAX-ACCESS read-write 1720 STATUS current 1721 DESCRIPTION 1722 "Indicates whether efmCuPmeLineAtnCrossing notifications 1723 should be generated for this interface. 1725 Value of true(1) indicates that efmCuPmeLineAtnCrossing 1726 notification is enabled. Value of false(2) indicates that 1727 the notification is disabled." 1728 ::= { efmCuPmeConfEntry 6 } 1730 efmCuPmeSnrMgnCrossingEnable OBJECT-TYPE 1731 SYNTAX TruthValue 1732 MAX-ACCESS read-write 1733 STATUS current 1734 DESCRIPTION 1735 "Indicates whether efmCuPmeSnrMgnCrossing notifications 1736 should be generated for this interface. 1738 Value of true(1) indicates that efmCuPmeSnrMgnCrossing 1739 notification is enabled. Value of false(2) indicates that 1740 the notification is disabled." 1741 ::= { efmCuPmeConfEntry 7 } 1743 efmCuPmeDeviceFaultEnable OBJECT-TYPE 1744 SYNTAX TruthValue 1745 MAX-ACCESS read-write 1746 STATUS current 1747 DESCRIPTION 1748 "Indicates whether efmCuPmeDeviceFault notifications 1749 should be generated for this interface. 1751 Value of true(1) indicates that efmCuPmeDeviceFault 1752 notification is enabled. Value of false(2) indicates that 1753 the notification is disabled." 1754 ::= { efmCuPmeConfEntry 8 } 1756 efmCuPmeConfigInitFailEnable OBJECT-TYPE 1757 SYNTAX TruthValue 1758 MAX-ACCESS read-write 1759 STATUS current 1760 DESCRIPTION 1761 "Indicates whether efmCuPmeConfigInitFailure notifications 1762 should be generated for this interface. 1764 Value of true(1) indicates that efmCuPmeConfigInitFailure 1765 notification is enabled. Value of false(2) indicates that 1766 the notification is disabled." 1767 ::= { efmCuPmeConfEntry 9 } 1769 efmCuPmeProtocolInitFailEnable OBJECT-TYPE 1770 SYNTAX TruthValue 1771 MAX-ACCESS read-write 1772 STATUS current 1773 DESCRIPTION 1774 "Indicates whether efmCuPmeProtocolInitFailure notifications 1775 should be generated for this interface. 1777 Value of true(1) indicates that efmCuPmeProtocolInitFailure 1778 notification is enabled. Value of false(2) indicates that 1779 the notification is disabled." 1780 ::= { efmCuPmeConfEntry 10 } 1782 efmCuPmeCapabilityTable OBJECT-TYPE 1783 SYNTAX SEQUENCE OF EfmCuPmeCapabilityEntry 1784 MAX-ACCESS not-accessible 1785 STATUS current 1786 DESCRIPTION 1787 "Table for Configuration of common aspects for EFMCu 1788 2BASE-TL/10PASS-TS PME ports (modems). Configuration of 1789 aspects specific to 2BASE-TL or 10PASS-TS PME types is 1790 represented in efmCuPme2BConfTable and efmCuPme10PConfTable 1791 respectively. 1793 Entries in this table MUST be maintained in a persistent 1794 manner." 1795 ::= { efmCuPme 2 } 1797 efmCuPmeCapabilityEntry OBJECT-TYPE 1798 SYNTAX EfmCuPmeCapabilityEntry 1799 MAX-ACCESS not-accessible 1800 STATUS current 1801 DESCRIPTION 1802 "An entry in the EFMCu PME Capability table. 1803 Each entry represents common aspects of an EFMCu PME port 1804 indexed by the ifIndex. Note that an EFMCu PME port can be 1805 stacked below a single PCS port, also indexed by ifIndex, 1806 possibly together with other PME ports if PAF is enabled." 1807 INDEX { ifIndex } 1808 ::= { efmCuPmeCapabilityTable 1 } 1810 EfmCuPmeCapabilityEntry ::= 1811 SEQUENCE { 1812 efmCuPmeSubTypesSupported BITS 1813 } 1815 efmCuPmeSubTypesSupported OBJECT-TYPE 1816 SYNTAX BITS { 1817 ieee2BaseTLO(0), 1818 ieee2BaseTLR(1), 1819 ieee10PassTSO(2), 1820 ieee10PassTSR(3) 1821 } 1822 MAX-ACCESS read-only 1823 STATUS current 1824 DESCRIPTION 1825 "PME supported sub-types. This is a bitmap of possible 1826 sub-types. The various bit positions are: 1827 ieee2BaseTLO - PME is capable of operating as 2BaseTL-O 1828 ieee2BaseTLR - PME is capable of operating as 2BaseTL-R 1829 ieee10PassTSO - PME is capable of operating as 10PassTS-O 1830 ieee10PassTSR - PME is capable of operating as 10PassTS-R 1832 An desired mode of operation is determined by 1833 efmCuPmeAdminSubType, while efmCuPmeOperSubType relects the 1834 current operating mode. 1836 If a Clause 45 MDIO Interface to the PCS is present, then this 1837 object combines the 10PASS-TS capable and 2BASE-TL capable 1838 bits in the 10P/2B PMA/PMD speed ability register and the 1839 CO supported and CPE supported bits in the 10P/2B PMA/PMD 1840 status register" 1841 REFERENCE 1842 "[802.3ah] 61.1, 45.2.1.4.1, 45.2.1.4.2, 45.2.1.12.2, 1843 45.2.1.12.3" 1844 ::= { efmCuPmeCapabilityEntry 1 } 1846 efmCuPmeStatusTable OBJECT-TYPE 1847 SYNTAX SEQUENCE OF EfmCuPmeStatusEntry 1848 MAX-ACCESS not-accessible 1849 STATUS current 1850 DESCRIPTION 1851 "This table provides common status information of EFMCu 1852 2BASE-TL/10PASS-TS PME ports. Status information specific 1853 to 10PASS-TS PME is represented in efmCuPme10PStatusTable. 1855 This table contains live data from the equipment. As such, 1856 it is NOT persistent." 1857 ::= { efmCuPme 3 } 1859 efmCuPmeStatusEntry OBJECT-TYPE 1860 SYNTAX EfmCuPmeStatusEntry 1861 MAX-ACCESS not-accessible 1862 STATUS current 1863 DESCRIPTION 1864 "An entry in the EFMCu PME Status table. 1865 Each entry represents common aspects of an EFMCu PME port 1866 indexed by the ifIndex. Note that an EFMCu PME port can be 1867 stacked below a single PCS port, also indexed by ifIndex, 1868 possibly together with other PME ports if PAF is enabled." 1869 INDEX { ifIndex } 1870 ::= { efmCuPmeStatusTable 1 } 1872 EfmCuPmeStatusEntry ::= 1873 SEQUENCE { 1874 efmCuPmeOperStatus INTEGER, 1875 efmCuPmeFltStatus BITS, 1876 efmCuPmeOperSubType INTEGER, 1877 efmCuPmeOperProfile ProfileIndexOrZero, 1878 efmCuPmeSnrMgn Integer32, 1879 efmCuPmePeerSnrMgn Integer32, 1880 efmCuPmeLineAtn Integer32, 1881 efmCuPmePeerLineAtn Integer32, 1882 efmCuPmeTCCodingErrors Counter32 1883 } 1885 efmCuPmeOperStatus OBJECT-TYPE 1886 SYNTAX INTEGER { 1887 up(1), 1888 downNotReady(2), 1889 downReady(3), 1890 init(4) 1891 } 1892 MAX-ACCESS read-only 1893 STATUS current 1894 DESCRIPTION 1895 "Current PME link Operational Status. Possible values are: 1896 up(1) - link is Up and ready to pass 64/65B 1897 encoded frames or fragments. 1898 downNotReady(2) - link is Down and the PME does not detect 1899 Handshake tones from its peer. This value 1900 may indicate a possible problem with 1901 the peer PME. 1902 downReady(3) - link is Down and the PME detects Handshake 1903 tones from its peer. 1904 init(4) - link is initializing, as a result of 1905 ifAdminStatus being set to 'up' for a 1906 particular PME or a PCS the PME is 1907 connected to. 1909 This object is intended to supplement Down state of 1910 ifOperStatus. 1912 This object partially maps to the Clause 30 attribute 1913 aPMEStatus. 1915 If a Clause 45 MDIO Interface to the PME is present, then this 1916 object partially maps to PMA/PMD link status bits in 10P/2B 1917 PMA/PMD status register." 1918 REFERENCE 1919 "[802.3ah] 30.11.2.1.3, 45.2.1.12.4" 1920 ::= { efmCuPmeStatusEntry 1 } 1922 efmCuPmeFltStatus OBJECT-TYPE 1923 SYNTAX BITS { 1924 lossOfFraming(0), 1925 snrMgnDefect(1), 1926 lineAtnDefect(2), 1927 deviceFault(3), 1928 configInitFailure(4), 1929 protocolInitFailure(5) 1930 } 1931 MAX-ACCESS read-only 1932 STATUS current 1933 DESCRIPTION 1934 "Current/Last PME link Fault Status. This is a bitmap of 1935 possible conditions. The various bit positions are: 1937 lossOfFraming - Loss of Framing for 10P or 1938 Loss of Sync word for 2B PMD or 1939 Loss of 64/65B Framing 1940 snrMgnDefect - SNR Margin dropped below the Threshold 1941 lineAtnDefect - Line Attenuation exceeds the Threshold 1942 deviceFault - Indicates a vendor-dependent 1943 diagnostic or self-test fault 1944 has been detected. 1945 configInitFailure - Configuration initialization failure, 1946 due to inability of the PME link to 1947 support configuration profile, 1948 requested during initialization. 1949 protocolInitFailure - Protocol initialization failure, 1950 due to incompatible protocol used by 1951 the Peer PME during init (that could 1952 happen if a peer PMD is G.SDHSL/VDSL 1953 modem for 2BASE-TL/10PASS-TS PME 1954 respectively). 1956 This object is intended to supplement ifOperStatus in IF-MIB. 1958 The indications hold information about the last fault. 1959 efmCuPmeFltStatus is cleared by the device restart. 1960 In addition lossOfFraming, configInitFailure and 1961 protocolInitFailure are cleared by PME init. 1962 deviceFault is cleared by successful diagnostics/test. 1963 snrMgnDefect and lineAtnDefect are cleared by SNR Margin 1964 and line Attenuation respectively returning to norm and by 1965 PME init. 1967 This object partially maps to the Clause 30 attribute 1968 aPMEStatus. 1970 If a Clause 45 MDIO Interface to the PME is present, then this 1971 object consolidates information from various PMA/PMD 1972 registers, namely: Fault bit in PMA/PMD status 1 register, 1973 10P/2B PMA/PMD link loss register, 1974 10P outgoing indicator bits status register, 1975 10P incoming indicator bits status register, 1976 2B state defects register." 1977 REFERENCE 1978 "[802.3ah] 30.11.2.1.3, 45.2.1.2.1, 45.2.1.38, 1979 45.2.1.39, 45.2.1.54" 1980 ::= { efmCuPmeStatusEntry 2 } 1982 efmCuPmeOperSubType OBJECT-TYPE 1983 SYNTAX INTEGER { 1984 ieee2BaseTLO(1), 1985 ieee2BaseTLR(2), 1986 ieee10PassTSO(3), 1987 ieee10PassTSR(4) 1988 } 1989 MAX-ACCESS read-only 1990 STATUS current 1991 DESCRIPTION 1992 "Current operational sub-type of the PME. 1993 Possible values are: 1994 ieee2BaseTLO - PME operates as 2BaseTL-O 1995 ieee2BaseTLR - PME operates as 2BaseTL-R 1996 ieee10PassTSO - PME operates as 10PassTS-O 1997 ieee10PassTSR - PME operates as 10PassTS-R 1999 The operational sub type of the PME can be configured via 2000 efmCuPmeAdminSubType variable. 2002 If a Clause 45 MDIO Interface to the PMA/PMD is present, then 2003 this object combines values of the Port sub-type select 2004 bits, the PMA/PMD type selection bits in the 10P/2B 2005 PMA/PMD control register and the PMA/PMD link status bits in 2006 the 10P/2B PMA/PMD status register." 2007 REFERENCE 2008 "[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7, 45.2.1.12.4" 2009 ::= { efmCuPmeStatusEntry 3 } 2011 efmCuPmeOperProfile OBJECT-TYPE 2012 SYNTAX ProfileIndexOrZero 2013 MAX-ACCESS read-only 2014 STATUS current 2015 DESCRIPTION 2016 "PME current operating Profile. This object is a pointer to 2017 an entry in either efmCuPme2BProfileTable or 2018 efmCuPme10PProfileTable, depending on the current 2019 operating SubType of the PME as indicated by 2020 efmCuPmeOperSubType. 2021 Note that a profile entry, to which efmCuPmeOperProfile is 2022 pointing to, can be created automatically, to reflect achieved 2023 parameters in adaptive (not fixed) initialization, 2024 i.e. values of efmCuPmeOperProfile and efmCuAdminProfile or 2025 efmCuPmeAdminProfile MAY differ. 2026 The value of zero indicates that PME is down or initializing. 2028 This object partially maps to the aOperatingProfile 2029 attribute in Clause 30." 2030 REFERENCE 2031 "[802.3ah] 30.11.2.1.7" 2032 ::= { efmCuPmeStatusEntry 4 } 2034 efmCuPmeSnrMgn OBJECT-TYPE 2035 SYNTAX Integer32(-127..128|65535) 2036 UNITS "dB" 2037 MAX-ACCESS read-only 2038 STATUS current 2039 DESCRIPTION 2040 "The current Signal-to-Noise Ratio (SNR) margin with respect 2041 to the received signal as perceived by the local PME. 2042 The value of 65535 is returned when PME is down or 2043 initializing. 2045 This object maps to the aPMESNRMgn attribute in Clause 30. 2047 If a Clause 45 MDIO Interface is present, then this 2048 object maps to the 10P/2B RX SNR margin register." 2049 REFERENCE 2050 "[802.3ah] 30.11.2.1.4, 45.2.1.16" 2051 ::= { efmCuPmeStatusEntry 5 } 2053 efmCuPmePeerSnrMgn OBJECT-TYPE 2054 SYNTAX Integer32(-127..128|65535) 2055 UNITS "dB" 2056 MAX-ACCESS read-only 2057 STATUS current 2058 DESCRIPTION 2059 "The current SNR margin in dB with respect to the received 2060 signal, as perceived by the remote (link partner) PME. 2061 The value of 65535 is returned when PME is down or 2062 initializing. 2064 This object is not supported by -R PME subtypes. 2066 If a Clause 45 MDIO Interface is present, then this 2067 object maps to the 10P/2B link partner RX SNR margin 2068 register." 2069 REFERENCE 2070 "[802.3ah] 45.2.1.17" 2071 ::= { efmCuPmeStatusEntry 6} 2073 efmCuPmeLineAtn OBJECT-TYPE 2074 SYNTAX Integer32(-127..128|65535) 2075 UNITS "dB" 2076 MAX-ACCESS read-only 2077 STATUS current 2078 DESCRIPTION 2079 "The current Line Attenuation in dB as perceived by the local 2080 PME. 2081 The value of 65535 is returned when PME is down or 2082 initializing. 2084 If a Clause 45 MDIO Interface is present, then this 2085 object maps to the Line Attenuation register" 2086 REFERENCE 2087 "[802.3ah] 45.2.1.18" 2088 ::= { efmCuPmeStatusEntry 7 } 2090 efmCuPmePeerLineAtn OBJECT-TYPE 2091 SYNTAX Integer32(-127..128|65535) 2092 UNITS "dB" 2093 MAX-ACCESS read-only 2094 STATUS current 2095 DESCRIPTION 2096 "The current Line Attenuation in dB as perceived by the remote 2097 (link partner) PME. 2098 The value of 65535 is returned when PME is down or 2099 initializing. 2101 This object is not supported by CPE port subtypes. 2103 If a Clause 45 MDIO Interface is present, then this 2104 object maps to the 20P/2B link partner Line Attenuation 2105 register." 2106 REFERENCE 2107 "[802.3ah] 45.2.1.19" 2108 ::= { efmCuPmeStatusEntry 8 } 2110 efmCuPmeTCCodingErrors OBJECT-TYPE 2111 SYNTAX Counter32 2112 MAX-ACCESS read-only 2113 STATUS current 2114 DESCRIPTION 2115 "A number of 64/65-octet encapsulation errors. This counter is 2116 incremented for each 64/65-octet encapsulation error detected 2117 by the 64/65-octet receive function. 2118 The value of zero SHALL be returned when PME is down or 2119 initializing. 2121 If a Clause 45 MDIO Interface to the PME TC is present, then 2122 this object maps to the TC coding violations register 2123 (see 45.2.6.12)." 2124 REFERENCE 2125 "[802.3ah] 61.3.3.1, 45.2.6.12" 2126 ::= { efmCuPmeStatusEntry 9 } 2128 -- 2BASE-TL specific PME group 2130 efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 } 2132 efmCuPme2BProfileTable OBJECT-TYPE 2133 SYNTAX SEQUENCE OF EfmCuPme2BProfileEntry 2134 MAX-ACCESS not-accessible 2135 STATUS current 2136 DESCRIPTION 2137 "This table supports definitions of administrative and 2138 operating Profiles for 2BASE-TL PMEs. 2139 First 14 entries in this table SHALL always be defined as 2140 follows (see 802.3ah Annex 63A): 2141 -------+------+-----+--------+------------------ 2142 Profile Rate Power Region Constellation 2143 index (Kbps) (dBm) (G.991.2) 2144 -------+------+-----+--------+------------------ 2145 1 512 13.5 1 16-TCPAM (default) 2146 2 704 13.5 1 16-TCPAM 2147 3 1024 13.5 1 16-TCPAM 2148 4 2048 13.5 1 16-TCPAM 2149 5 3072 13.5 1 32-TCPAM 2150 6 5696 13.5 1 32-TCPAM 2151 7 512 13.5 2 16-TCPAM 2152 8 704 13.5 2 16-TCPAM 2153 9 1024 13.5 2 16-TCPAM 2154 10 2048 14.5 2 16-TCPAM 2155 11 3072 14.5 2 32-TCPAM 2156 12 5696 14.5 2 32-TCPAM 2157 13 0 0 1 0 (best effort) 2158 14 0 0 2 0 (best effort) 2160 These default entries SHALL be created during agent 2161 initialization and MUST not be deleted. 2163 Entries following the first 14, can be dynamically created and 2164 deleted, to provide custom administrative (configuration) 2165 profiles and automatic operating profiles. 2167 This table MUST be maintained in a persistent manner." 2168 REFERENCE 2169 "[802.3ah] Annex 63A, 30.11.2.1.6" 2170 ::= { efmCuPme2B 2 } 2172 efmCuPme2BProfileEntry OBJECT-TYPE 2173 SYNTAX EfmCuPme2BProfileEntry 2174 MAX-ACCESS not-accessible 2175 STATUS current 2176 DESCRIPTION 2177 "Each entry corresponds to a single 2BASE-TL PME profile. 2178 Each profile contains a set of parameters, used either for 2179 configuration or representation of a 2BASE-TL PME. 2180 In case a particular profile is referenced via 2181 efmCuPmeAdminProfile object (or efmCuAdminProfile if 2182 efmCuPmeAdminProfile is zero), it represent the desired 2183 parameters the 2BaseTL-O PME initialization. 2184 If a profile is referenced via efmCuPmeOperProfile object, 2185 it represents current operating parameters of the 2186 operational PME. 2188 Profiles may be created/deleted using the row creation/ 2189 deletion mechanism via efmCuPme2BProfileRowStatus. If an 2190 active entry is referenced, the entry MUST remain 'active' 2191 until all references are removed. 2192 Default entries MUST not be removed." 2193 INDEX { efmCuPme2BProfileIndex } 2194 ::= { efmCuPme2BProfileTable 1 } 2196 EfmCuPme2BProfileEntry ::= 2197 SEQUENCE { 2198 efmCuPme2BProfileIndex ProfileIndex, 2199 efmCuPme2BProfileDescr SnmpAdminString, 2200 efmCuPme2BRegion INTEGER, 2201 efmCuPme2BDataRate Unsigned32, 2202 efmCuPme2BPower Unsigned32, 2203 efmCuPme2BConstellation INTEGER, 2204 efmCuPme2BProfileRowStatus RowStatus 2205 } 2207 efmCuPme2BProfileIndex OBJECT-TYPE 2208 SYNTAX ProfileIndex 2209 MAX-ACCESS not-accessible 2210 STATUS current 2211 DESCRIPTION 2212 "2BASE-TL PME Profile index. 2213 This object is the unique index associated with this profile. 2214 Entries in this table are referenced via efmCuAdminProfile 2215 or efmCuPmeAdminProfile objects." 2216 ::= { efmCuPme2BProfileEntry 1 } 2218 efmCuPme2BProfileDescr OBJECT-TYPE 2219 SYNTAX SnmpAdminString (SIZE(0..255)) 2220 MAX-ACCESS read-create 2221 STATUS current 2222 DESCRIPTION 2223 "A textual string containing information about 2BASE-TL PME 2224 Profile. The string MAY include information about data rate 2225 and spectral limitations of this particular profile." 2226 ::= { efmCuPme2BProfileEntry 2 } 2228 efmCuPme2BRegion OBJECT-TYPE 2229 SYNTAX INTEGER { 2230 region1(1), 2231 region2(2) 2232 } 2233 MAX-ACCESS read-create 2234 STATUS current 2235 DESCRIPTION 2236 "Power Spectral Density (PSD) Regional settings as 2237 specified in the relevant Regional Annex of [G.991.2]. 2238 Regional settings place limitations on the max allowed 2239 data rate, power and constellation. 2241 Possible values for this object are: 2242 region1 -- Annexes A and F (e.g. North America) 2243 region2 -- Annexes B and G (e.g. Europe) 2245 Changing of the Region must be performed when the link is 2246 Down. 2247 Attempts to change this object MUST be rejected with 2248 the error inconsistentValue, if the link is Up or 2249 Initializing. 2251 If a Clause 45 MDIO Interface to the PME is present, then this 2252 object maps to the Region bits in the 2B general 2253 parameter register." 2254 REFERENCE 2255 "[802.3ah] 45.2.1.42" 2256 ::= { efmCuPme2BProfileEntry 3 } 2258 efmCuPme2BDataRate OBJECT-TYPE 2259 SYNTAX Unsigned32(0..5696) 2260 UNITS "Kbps" 2261 MAX-ACCESS read-create 2262 STATUS current 2263 DESCRIPTION 2264 "2BASE-TL PME Data Rate. 2265 The rate is fixed when the value of this object is n x 64Kbps, 2266 where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM. 2267 The value of 0 in the administrative profile means that data 2268 rate is not fixed but is adaptive and should be set to the 2269 maximum attainable rate during line probing, under the 2270 spectral limitations placed by the efmCuPme2BRegion. 2272 If a Clause 45 MDIO Interface to the PME is present, then this 2273 object maps to the Min/Max Data Rate1 bits in the 2B PMD 2274 parameters register. 2276 This object MUST be maintained in a persistent manner." 2277 REFERENCE 2278 "[802.3ah] 45.2.1.43" 2279 ::= { efmCuPme2BProfileEntry 4 } 2281 efmCuPme2BPower OBJECT-TYPE 2282 SYNTAX Unsigned32(0|10..42) 2283 UNITS "0.5 dBm" 2284 MAX-ACCESS read-create 2285 STATUS current 2286 DESCRIPTION 2287 "Signal Transmit Power. Multiple of 0.5dBm. 2288 The value of 0 in the administrative profile means that the 2289 signal transmit power is not fixed and should be set to 2290 maximize the attainable rate, under the spectral limitations 2291 placed by the efmCuPme2BRegion. 2293 Changing of the Signal Transmit Power must be performed when 2294 the link is Down. Attempts to change this object MUST be 2295 rejected with the error inconsistentValue, if the link is Up 2296 or Initializing. 2298 If a Clause 45 MDIO Interface to the PME is present, then this 2299 object will map to the Power1 bits in the 2B PMD 2300 parameters register" 2301 REFERENCE 2302 "[802.3ah] 45.2.1.43" 2303 ::= { efmCuPme2BProfileEntry 5 } 2305 efmCuPme2BConstellation OBJECT-TYPE 2306 SYNTAX INTEGER { 2307 adaptive(0), 2308 tcpam16(1), 2309 tcpam32(2) 2310 } 2311 MAX-ACCESS read-create 2312 STATUS current 2313 DESCRIPTION 2314 "TCPAM Constellation of the 2BASE-TL PME. 2315 The possible values are: 2316 adaptive(0) - either 16- or 32-TCPAM 2317 tcpam16(1) - 16-TCPAM 2318 tcpam32(2) - 32-TCPAM 2320 The value of adaptive(0) in the administrative profile means 2321 that the constellation is not fixed and should be set to 2322 maximize the attainable rate, under the spectral limitations 2323 placed by the efmCuPme2BRegion. 2325 If a Clause 45 MDIO Interface to the PME is present, then this 2326 object map to the Constellation1 bits in the 2B general 2327 parameter register." 2328 REFERENCE 2329 "[802.3ah] 45.2.1.43" 2330 ::= { efmCuPme2BProfileEntry 6 } 2332 efmCuPme2BProfileRowStatus OBJECT-TYPE 2333 SYNTAX RowStatus 2334 MAX-ACCESS read-create 2335 STATUS current 2336 DESCRIPTION 2337 "This object controls creation/deletion of the associated 2338 entry in efmCuPme2BProfileTable per the semantics of 2339 RowStatus. 2340 If an 'active' entry is referenced via efmCuAdminProfile or 2341 efmCuPmeAdminProfile, the entry MUST remain 'active' until all 2342 references are removed." 2343 ::= { efmCuPme2BProfileEntry 7 } 2345 -- 10PASS-TS specific PME group 2347 efmCuPme10P OBJECT IDENTIFIER ::= { efmCuPme 6 } 2349 efmCuPme10PProfileTable OBJECT-TYPE 2350 SYNTAX SEQUENCE OF EfmCuPme10PProfileEntry 2351 MAX-ACCESS not-accessible 2352 STATUS current 2353 DESCRIPTION 2354 "This table supports definitions of configuration profiles for 2355 10PassTL PMEs. 2356 First 22 entries in this table SHALL always be defined as 2357 follows (see 802.3ah Annex 62B.3): 2358 -------+--------+----+---------+-----+------------ 2359 Profile Bandplan UPBO BandNotch DRate URate 2360 Index PSDMask# p# p# p# p# 2361 -------+--------+----+---------+-----+------------ 2362 1 1 3 2,6,10,11 20 20(default) 2363 2 13 5 0 20 20 2364 3 1 1 0 20 20 2365 4 16 0 0 100 100 2366 5 16 0 0 70 50 2367 6 6 0 0 50 10 2368 7 17 0 0 30 30 2369 8 8 0 0 30 5 2370 9 4 0 0 25 25 2371 10 4 0 0 15 15 2372 11 23 0 0 10 10 2373 12 23 0 0 5 5 2374 13 16 0 2,5,9,11 100 100 2375 14 16 0 2,5,9,11 70 50 2376 15 6 0 2,6,10,11 50 10 2377 16 17 0 2,5,9,11 30 30 2378 17 8 0 2,6,10,11 30 5 2379 18 4 0 2,6,10,11 25 25 2380 19 4 0 2,6,10,11 15 15 2381 20 23 0 2,5,9,11 10 10 2382 21 23 0 2,5,9,11 5 5 2383 22 30 0 0 200 50 2385 These default entries SHALL be created by during agent 2386 initialization and MUST not be deleted. 2388 Entries following the first 22, can be dynamically created and 2389 deleted, to provide custom administrative (configuration) 2390 profiles and automatic operating profiles. 2392 This table MUST be maintained in a persistent manner." 2393 REFERENCE 2394 "[802.3ah] Annex 62B.3, 30.11.2.1.6" 2395 ::= { efmCuPme10P 1 } 2397 efmCuPme10PProfileEntry OBJECT-TYPE 2398 SYNTAX EfmCuPme10PProfileEntry 2399 MAX-ACCESS not-accessible 2400 STATUS current 2401 DESCRIPTION 2402 "Each entry corresponds to a single 10PASS-TS PME 2403 profile. 2404 Each profile contains a set of parameters, used either for 2405 configuration or representation of a 10PASS-TS PME. 2406 In case a particular profile is referenced via 2407 efmCuPmeAdminProfile object (or efmCuAdminProfile if 2408 efmCuPmeAdminProfile is zero), it represent the desired 2409 parameters the 10PassTS-O PME initialization. 2411 If a profile is referenced via efmCuPmeOperProfile object, 2412 it represents current operating parameters of the PME. 2414 Profiles may be created/deleted using the row creation/ 2415 deletion mechanism via efmCuPme10PProfileRowStatus. If an 2416 'active' entry is referenced, the entry MUST remain 'active' 2417 until all references are removed. 2418 Default entries MUST not be removed." 2419 INDEX { efmCuPme10PProfileIndex } 2420 ::= { efmCuPme10PProfileTable 1 } 2422 EfmCuPme10PProfileEntry ::= 2423 SEQUENCE { 2424 efmCuPme10PProfileIndex ProfileIndex, 2425 efmCuPme10PProfileDescr SnmpAdminString, 2426 efmCuPme10PBandplanPSDMskProfile INTEGER, 2427 efmCuPme10PUPBOReferenceProfile INTEGER, 2428 efmCuPme10PBandNotchProfiles BITS, 2429 efmCuPme10PPayloadURateProfile INTEGER, 2430 efmCuPme10PPayloadDRateProfile INTEGER, 2431 efmCuPme10PProfileRowStatus RowStatus 2432 } 2434 efmCuPme10PProfileIndex OBJECT-TYPE 2435 SYNTAX ProfileIndex 2436 MAX-ACCESS not-accessible 2437 STATUS current 2438 DESCRIPTION 2439 "10PASS-TS PME Profile Index. 2440 This object is the unique index associated with this profile. 2441 Entries in this table are referenced via efmCuAdminProfile or 2442 efmCuPmeAdminProfile." 2443 ::= { efmCuPme10PProfileEntry 1 } 2445 efmCuPme10PProfileDescr OBJECT-TYPE 2446 SYNTAX SnmpAdminString (SIZE(0..255)) 2447 MAX-ACCESS read-create 2448 STATUS current 2449 DESCRIPTION 2450 "A textual string containing information about 10PASS-TS PME 2451 Profile. The string MAY include information about data rate 2452 and spectral limitations of this particular profile." 2453 ::= { efmCuPme10PProfileEntry 2 } 2455 efmCuPme10PBandplanPSDMskProfile OBJECT-TYPE 2456 SYNTAX INTEGER { 2457 profile1(1), 2458 profile2(2), 2459 profile3(3), 2460 profile4(4), 2461 profile5(5), 2462 profile6(6), 2463 profile7(7), 2464 profile8(8), 2465 profile9(9), 2466 profile10(10), 2467 profile11(11), 2468 profile12(12), 2469 profile13(13), 2470 profile14(14), 2471 profile15(15), 2472 profile16(16), 2473 profile17(17), 2474 profile18(18), 2475 profile19(19), 2476 profile20(20), 2477 profile21(21), 2478 profile22(22), 2479 profile23(23), 2480 profile24(24), 2481 profile25(25), 2482 profile26(26), 2483 profile27(27), 2484 profile28(28), 2485 profile29(29) 2486 } 2487 MAX-ACCESS read-create 2488 STATUS current 2489 DESCRIPTION 2490 "10PASS-TS PME Bandplan and PSD Mask profile, 2491 as specified in 802.3ah Annex 62A. Possible values are: 2492 --------------+------------------------+-----------+--------- 2493 Profile Name PSD Mask Bands Bandplan 2494 --------------+------------------------+-----------+--------- 2495 profile1(1) - T1.424/T-U P1 FTTCab.M1 x/D/U/D/U A 2496 profile2(2) - T1.424/T-U P1 FTTEx.M1 2497 profile3(3) - T1.424/T-U P1 FTTCab.M2 2498 profile4(4) - T1.424/T-U P1 FTTEx.M2 2499 profile5(5) - T1.424/T-U P1 FTTCab.M1 D/D/U/D/U 2500 profile6(6) - T1.424/T-U P1 FTTEx.M1 2501 profile7(7) - T1.424/T-U P1 FTTCab.M2 2502 profile8(8) - T1.424/T-U P1 FTTEx.M2 2503 profile9(9) - T1.424/T-U P1 FTTCab.M1 U/D/U/D/x 2504 profile10(10) - T1.424/T-U P1 FTTEx.M1 2505 profile11(11) - T1.424/T-U P1 FTTCab.M2 2506 profile12(12) - T1.424/T-U P1 FTTEx.M2 2507 profile13(13) - TS1 101 270-1 Pcab.M1.A x/D/U/D/U B 2508 profile14(14) - TS1 101 270-1 Pcab.M1.B 2509 profile15(15) - TS1 101 270-1 Pex.P1.M1 2510 profile16(16) - TS1 101 270-1 Pex.P2.M1 2511 profile17(17) - TS1 101 270-1 Pcab.M2 2512 profile18(18) - TS1 101 270-1 Pex.P1.M2 2513 profile19(19) - TS1 101 270-1 Pex.P2.M2 2514 profile20(20) - TS1 101 270-1 Pcab.M1.A U/D/U/D/x 2515 profile21(21) - TS1 101 270-1 Pcab.M1.B 2516 profile22(22) - TS1 101 270-1 Pex.P1.M1 2517 profile23(23) - TS1 101 270-1 Pex.P2.M1 2518 profile24(24) - TS1 101 270-1 Pcab.M2 2519 profile25(25) - TS1 101 270-1 Pex.P1.M2 2520 profile26(26) - TS1 101 270-1 Pex.P2.M2 2521 profile27(27) - G.993.1 F.1.2.1 (VDSLoPOTS) x/D/U/D/U F 2522 profile28(28) - G.993.1 F.1.2.2 (VDSLoTCM-ISDN) 2523 profile29(29) - G.993.1 F.1.2.3 (PSD reduction) 2525 This object maps to the aBandplanPSDMaskProfile attribute 2526 in Clause 30." 2527 REFERENCE 2528 "[802.3ah] Annex 62A, 30.5.1.1.22" 2529 ::= { efmCuPme10PProfileEntry 3 } 2531 efmCuPme10PUPBOReferenceProfile OBJECT-TYPE 2532 SYNTAX INTEGER { 2533 profile1(1), 2534 profile2(2), 2535 profile3(3), 2536 profile4(4), 2537 profile5(5), 2538 profile6(6), 2539 profile7(7), 2540 profile8(8), 2541 profile9(9) 2542 } 2543 MAX-ACCESS read-create 2544 STATUS current 2545 DESCRIPTION 2546 "10PASS-TS PME Upstream Power Back-Off (UPBO) Reference PSD 2547 Profile, as specified in 802.3ah Annex 62A. Possible values 2548 are: 2549 profile1(1) - T1.424/T-U Noise A M1 2550 profile2(2) - T1.424/T-U Noise A M2 2551 profile3(3) - T1.424/T-U Noise F M1 2552 profile4(4) - T1.424/T-U Noise F M2 2553 profile5(5) - ETSI TS 101 270-1 Noise A&B 2554 profile6(6) - ETSI TS 101 270-1 Noise C 2555 profile7(7) - ETSI TS 101 270-1 Noise D 2556 profile8(8) - ETSI TS 101 270-1 Noise E 2557 profile9(9) - ETSI TS 101 270-1 Noise F 2559 This object maps to the aUPBOReferenceProfile attribute 2560 in Clause 30." 2561 REFERENCE 2562 "[802.3ah] Annex 62A.3.4, 30.5.1.1.23" 2563 ::= { efmCuPme10PProfileEntry 4 } 2565 efmCuPme10PBandNotchProfiles OBJECT-TYPE 2566 SYNTAX BITS { 2567 profile0(0), 2568 profile1(1), 2569 profile2(2), 2570 profile3(3), 2571 profile4(4), 2572 profile5(5), 2573 profile6(6), 2574 profile7(7), 2575 profile8(8), 2576 profile9(9), 2577 profile10(10), 2578 profile11(11) 2579 } 2580 MAX-ACCESS read-create 2581 STATUS current 2582 DESCRIPTION 2583 "10PASS-TS PME Egress Control Band Notch Profile bitmap, 2584 as specified in 802.3ah Annex 62A. Possible values are: 2585 --------------+---------+----------+-----------+------+----- 2586 Profile Name G.991.3 T1.424/T-U TS101 270-1 StartF EndF 2587 Table Table Table (MHz) (MHz) 2588 --------------+---------+----------+-----------+------+----- 2589 profile0(0) - no profile 2590 profile1(1) - F-5 #01 - - 1.810 1.825 2591 profile2(2) - 6-2 15-1 17 1.810 2.000 2592 profile3(3) - F-5 #02 - - 1.907 1.912 2593 profile4(4) - F-5 #03 - - 3.500 3.575 2594 profile5(5) - 6-2 - 17 3.500 3.800 2595 profile6(6) - - 15-1 - 3.500 4.000 2596 profile7(7) - F-5 #04 - - 3.747 3.754 2597 profile8(8) - F-5 #05 - - 3.791 3.805 2598 profile9(9) - 6-2 - 17 7.000 7.100 2599 profile10(10) - F-5 #06 15-1 - 7.000 7.300 2600 profile11(11) - 6-2 15-1 1 10.100 10.150 2602 Any combination of profiles can be specified by ORing 2603 individual profiles, for example value of 0x0622 selects 2604 profiles 2,6,10 and 11. 2606 This object maps to the aBandNotchProfile attribute 2607 in Clause 30." 2608 REFERENCE 2609 "[802.3ah] Annex 62A.3.5, 30.5.1.1.19" 2610 ::= { efmCuPme10PProfileEntry 5 } 2612 efmCuPme10PPayloadURateProfile OBJECT-TYPE 2613 SYNTAX INTEGER { 2614 profile5(5), 2615 profile10(10), 2616 profile15(15), 2617 profile20(20), 2618 profile25(25), 2619 profile30(30), 2620 profile50(50), 2621 profile70(70), 2622 profile100(100) 2623 } 2624 MAX-ACCESS read-create 2625 STATUS current 2626 DESCRIPTION 2627 "10PASS-TS PME Upstream Payload Rate Profile, 2628 as specified in 802.3ah Annex 62A. Possible values are: 2629 profile5(5) - 2.5 Mbps 2630 profile10(10) - 5 Mbps 2631 profile15(15) - 7.5 Mbps 2632 profile20(20) - 10 Mbps 2633 profile25(25) - 12.5 Mbps 2634 profile30(30) - 15 Mbps 2635 profile50(50) - 25 Mbps 2636 profile70(70) - 35 Mbps 2637 profile100(100) - 50 Mbps 2639 Each value represents a target for the PME's Upstream Payload 2640 Bitrate as seen at the MII. If the payload rate of the 2641 selected profile cannot be achieved based on the loop 2642 environment, bandplan and PSD mask, the PME initialization 2643 SHALL fail. 2645 This object maps to the aPayloadRateProfileUpstream 2646 attribute in Clause 30." 2647 REFERENCE 2648 "[802.3ah] Annex 62A.3.6, 30.5.1.1.20" 2649 ::= { efmCuPme10PProfileEntry 6 } 2651 efmCuPme10PPayloadDRateProfile OBJECT-TYPE 2652 SYNTAX INTEGER { 2653 profile5(5), 2654 profile10(10), 2655 profile15(15), 2656 profile20(20), 2657 profile25(25), 2658 profile30(30), 2659 profile50(50), 2660 profile70(70), 2661 profile100(100), 2662 profile140(140), 2663 profile200(200) 2664 } 2665 MAX-ACCESS read-create 2666 STATUS current 2667 DESCRIPTION 2668 "10PASS-TS PME Downstream Payload Rate Profile, 2669 as specified in 802.3ah Annex 62A. Possible values are: 2670 profile5(5) - 2.5 Mbps 2671 profile10(10) - 5 Mbps 2672 profile15(15) - 7.5 Mbps 2673 profile20(20) - 10 Mbps 2674 profile25(25) - 12.5 Mbps 2675 profile30(30) - 15 Mbps 2676 profile50(50) - 25 Mbps 2677 profile70(70) - 35 Mbps 2678 profile100(100) - 50 Mbps 2679 profile140(140) - 70 Mbps 2680 profile200(200) - 100 Mbps 2682 Each value represents a target for the PME's Downstream 2683 Payload Bitrate as seen at the MII. If the payload rate of 2684 the selected profile cannot be achieved based on the loop 2685 environment, bandplan and PSD mask, the PME initialization 2686 SHALL fail. 2688 This object maps to the aPayloadRateProfileDownstream 2689 attribute in Clause 30." 2690 REFERENCE 2691 "[802.3ah] Annex 62A.3.6, 30.5.1.1.21" 2692 ::= { efmCuPme10PProfileEntry 7 } 2694 efmCuPme10PProfileRowStatus OBJECT-TYPE 2695 SYNTAX RowStatus 2696 MAX-ACCESS read-create 2697 STATUS current 2698 DESCRIPTION 2699 "This object controls creation/deletion of the associated 2700 entry in efmCuPme10PProfileTable per the semantics of 2701 RowStatus. 2702 If an active entry is referenced via efmCuAdminProfile or 2703 efmCuPmeAdminProfile, the entry MUST remain 'active' until 2704 all references are removed." 2705 ::= { efmCuPme10PProfileEntry 8 } 2707 efmCuPme10PStatusTable OBJECT-TYPE 2708 SYNTAX SEQUENCE OF EfmCuPme10PStatusEntry 2709 MAX-ACCESS not-accessible 2710 STATUS current 2711 DESCRIPTION 2712 "Table reflecting status of EFMCu 10PASS-TS PMEs (modems)." 2713 ::= { efmCuPme10P 2 } 2715 efmCuPme10PStatusEntry OBJECT-TYPE 2716 SYNTAX EfmCuPme10PStatusEntry 2717 MAX-ACCESS not-accessible 2718 STATUS current 2719 DESCRIPTION 2720 "An entry in the EFMCu 10PASS-TS PME Status table." 2721 AUGMENTS { efmCuPmeStatusEntry } 2722 ::= { efmCuPme10PStatusTable 1 } 2724 EfmCuPme10PStatusEntry ::= 2725 SEQUENCE { 2726 efmCuPme10PElectricalLength Integer32, 2727 efmCuPme10PFECCorrectedBlocks Counter32, 2728 efmCuPme10PFECUncorrectedBlocks Counter32 2729 -- EdNote: To be continued 2730 } 2732 efmCuPme10PElectricalLength OBJECT-TYPE 2733 SYNTAX Integer32(0..8192|65535) 2734 UNITS "m" 2735 MAX-ACCESS read-only 2736 STATUS current 2737 DESCRIPTION 2738 "Electrical Length in meters as perceived by the 10PASS-TS PME 2739 after the link is established. 2740 The value of 65535 is returned if the link is Down or 2741 Initializing or the PME is unable to estimate the Electrical 2742 Length. 2744 If a Clause 45 MDIO Interface to the PME is present, then this 2745 object maps to the 10P Electrical Length register" 2747 REFERENCE 2748 "[802.3ah] 45.2.1.21" 2749 ::= { efmCuPme10PStatusEntry 1 } 2751 efmCuPme10PFECCorrectedBlocks OBJECT-TYPE 2752 SYNTAX Counter32 2753 MAX-ACCESS read-only 2754 STATUS current 2755 DESCRIPTION 2756 "A count of received and corrected FEC codewords in 10PASS-TS 2757 PME. 2759 This object maps to aPMEFECCorrectedBlocks attribute in 2760 clause 30. 2762 If a Clause 45 MDIO Interface to the PMA/PMD is present, 2763 then this object maps to the 10P FEC correctable errors 2764 register" 2765 REFERENCE 2766 "[802.3ah] 45.2.1.22" 2767 ::= { efmCuPme10PStatusEntry 2 } 2769 efmCuPme10PFECUncorrectedBlocks OBJECT-TYPE 2770 SYNTAX Counter32 2771 MAX-ACCESS read-only 2772 STATUS current 2773 DESCRIPTION 2774 "A count of received FEC codewords in 10PASS-TS PME, which are 2775 uncorrectable. 2777 This object maps to aPMEFECUncorrectableBlocks attribute in 2778 clause 30. 2780 If a Clause 45 MDIO Interface to the PMA/PMD is present, 2781 then this object maps to the 10P FEC uncorrectable errors 2782 register" 2783 REFERENCE 2784 "[802.3ah] 45.2.1.23" 2785 ::= { efmCuPme10PStatusEntry 3 } 2787 -- ifAvailableStackTable for use in Discovery 2789 ifAvailableStackTable OBJECT-TYPE 2790 SYNTAX SEQUENCE OF IfAvailableStackEntry 2791 MAX-ACCESS not-accessible 2792 STATUS current 2793 DESCRIPTION 2794 "This table, modeled after ifStackTable from [IF-MIB], 2795 contains information on the possible 'on-top-of' 2796 relationships between the multiple sub-layers of network 2797 interfaces (as opposed to actual relationships in 2798 ifStackTable). In particular, it contains information on 2799 which PCS ports (sublayers) can possibly run 'on top of' 2800 which PMEs (sublayers), as determined by cross-connect 2801 capability of the EFMCu device, where each sub-layer 2802 corresponds to a conceptual row in the ifTable. For example, 2803 when the PCS port with ifIndex value x can be connected 2804 to run on top of the PME with ifIndex value y, then this table 2805 contains: 2807 ifAvailableStackStatus.x.y=capable 2809 Note that there's always at least on PCS for each PME and at 2810 least one PME for each PCS in the EFMCu devices, with 2811 efmCuPAFCapacity and efmCuPeerPAFCapacity indicating 2812 maximum number of PMEs which can be aggregated by local and 2813 remote PCS port respectively. 2814 This table is read only as it describes device capability" 2815 REFERENCE 2816 "ifStackTable of RFC 2863" 2817 ::= { efmCuObjects 3 } 2819 ifAvailableStackEntry OBJECT-TYPE 2820 SYNTAX IfAvailableStackEntry 2821 MAX-ACCESS not-accessible 2822 STATUS current 2823 DESCRIPTION 2824 "Information on a particular relationship between two 2825 sub-layers, specifying that one sub-layer (PCS) runs on 'top' 2826 of the other sub-layer (PME). Each sub-layer corresponds to a 2827 conceptual row in the ifTable (interface index for PCS and 2828 PME respectively)." 2829 INDEX { 2830 ifAvailableStackHigherLayer, 2831 ifAvailableStackLowerLayer 2832 } 2833 ::= { ifAvailableStackTable 1 } 2835 IfAvailableStackEntry ::= 2836 SEQUENCE { 2837 ifAvailableStackHigherLayer InterfaceIndex, 2838 ifAvailableStackLowerLayer InterfaceIndex, 2839 ifAvailableStackStatus INTEGER 2840 } 2842 ifAvailableStackHigherLayer OBJECT-TYPE 2843 SYNTAX InterfaceIndex 2844 MAX-ACCESS not-accessible 2845 STATUS current 2846 DESCRIPTION 2847 "The value of ifIndex corresponding to the higher sub-layer 2848 of the 'cross-connect capability' relationship, i.e., the 2849 PCS sub-layer which MAY run on 'top' of the PME sub-layer 2850 identified by the corresponding instance of 2851 ifAvailableStackLowerLayer." 2852 ::= { ifAvailableStackEntry 1 } 2854 ifAvailableStackLowerLayer OBJECT-TYPE 2855 SYNTAX InterfaceIndex 2856 MAX-ACCESS not-accessible 2857 STATUS current 2858 DESCRIPTION 2859 "The value of ifIndex corresponding to the lower sub-layer 2860 of the 'cross-connect capability' relationship, i.e., the 2861 PME sub-layer which MAY run 'below' the PCS sub-layer 2862 identified by the corresponding instance of 2863 ifAvailableStackHigherLayer." 2864 ::= { ifAvailableStackEntry 2 } 2866 ifAvailableStackStatus OBJECT-TYPE 2867 SYNTAX INTEGER { 2868 capable(1), 2869 outOfService(2) 2870 } 2871 MAX-ACCESS read-only 2872 STATUS current 2873 DESCRIPTION 2874 "The status of the 'cross-connect capability' relationship 2875 between two sub-layers. The following values are defined: 2876 capable(1) - the PME sub-layer interface, identified by 2877 the ifAvailableStackLowerLayer MAY be 2878 connected to run 'below' the PCS sub-layer 2879 interface, identified by the 2880 ifAvailableStackLowerLayer. 2881 outOfService(2) - the PME sub-layer interface cannot be 2882 connected due to unavailability of the 2883 interface. 2885 Note that PME availability per PCS, indicated by 'capable' 2886 value, can be constrained by other parameters, 2887 for example by aggregation capacity of a PCS or by the PME in 2888 question being already connected to another PCS. So, in 2889 order to ensure that a particular PME can be connected to the 2890 PCS, all respective parameters (e.g. ifAvailableStackTable, 2891 ifStackTable and efmCuPAFCapacity) SHALL be inspected. 2893 This object is read only, unlike ifStackStatus, as it 2894 describes the device capability." 2895 ::= { ifAvailableStackEntry 3 } 2897 -- 2898 -- Conformance Statements 2899 -- 2901 efmCuGroups OBJECT IDENTIFIER ::= { efmCuConformance 1 } 2903 efmCuCompliances OBJECT IDENTIFIER ::= { efmCuConformance 2 } 2905 -- Object Groups 2907 efmCuBasicGroup OBJECT-GROUP 2908 OBJECTS { 2909 efmCuPAFSupported, 2910 efmCuAdminProfile, 2911 efmCuTargetDataRate, 2912 efmCuTargetSnrMgn, 2913 efmCuPortSide, 2914 efmCuFltStatus 2915 } 2916 STATUS current 2917 DESCRIPTION 2918 "A collection of objects required for all of EFMCu ports." 2919 ::= { efmCuGroups 1 } 2921 efmCuPAFGroup OBJECT-GROUP 2922 OBJECTS { 2923 efmCuPeerPAFSupported, 2924 efmCuPAFCapacity, 2925 efmCuPeerPAFCapacity, 2926 efmCuPAFAdminState, 2927 efmCuPAFDiscoveryCode, 2928 efmCuPAFRemoteDiscoveryCode, 2929 efmCuNumPMEs, 2930 ifAvailableStackStatus 2931 } 2932 STATUS current 2933 DESCRIPTION 2934 "A collection of objects required for optional PME 2935 Aggregation Function (PAF) and PAF discovery in EFMCu ports." 2936 ::= { efmCuGroups 2 } 2938 ifStackCapabilityGroup OBJECT-GROUP 2939 OBJECTS { 2940 ifAvailableStackStatus 2941 } 2942 STATUS current 2943 DESCRIPTION 2944 "A collection of objects providing information on 2945 the stacking capability of MIB-II interfaces." 2946 ::= { efmCuGroups 3 } 2948 efmCuPAFErrorsGroup OBJECT-GROUP 2949 OBJECTS { 2950 efmCuPAFInErrors, 2951 efmCuPAFInSmallFragments, 2952 efmCuPAFInLargeFragments, 2953 efmCuPAFInBadFragments, 2954 efmCuPAFInLostFragments, 2955 efmCuPAFInLostStarts, 2956 efmCuPAFInLostEnds, 2957 efmCuPAFInOverflows 2958 } 2959 STATUS current 2960 DESCRIPTION 2961 "A collection of objects supporting optional error counters 2962 of PAF on EFMCu ports." 2963 ::= { efmCuGroups 4 } 2965 efmCuPmeGroup OBJECT-GROUP 2966 OBJECTS { 2967 efmCuPmeAdminProfile, 2968 efmCuPmeOperStatus, 2969 efmCuPmeFltStatus, 2970 efmCuPmeSubTypesSupported, 2971 efmCuPmeAdminSubType, 2972 efmCuPmeOperSubType, 2973 efmCuPAFRemoteDiscoveryCode, 2974 efmCuPmeOperProfile, 2975 efmCuPmeSnrMgn, 2976 efmCuPmePeerSnrMgn, 2977 efmCuPmeLineAtn, 2978 efmCuPmePeerLineAtn, 2979 efmCuPmeTCCodingErrors, 2980 efmCuPmeThreshLineAtn, 2981 efmCuPmeThreshSnrMgn 2982 } 2983 STATUS current 2984 DESCRIPTION 2985 "A collection of objects providing information about 2986 a 2BASE-TL/10PASS-TS PME." 2987 ::= { efmCuGroups 5 } 2989 efmCuAlarmConfGroup OBJECT-GROUP 2990 OBJECTS { 2991 efmCuThreshLowBandwidth, 2992 efmCuLowBandwidthEnable, 2993 efmCuPmeThreshLineAtn, 2994 efmCuPmeLineAtnCrossingEnable, 2995 efmCuPmeThreshSnrMgn, 2996 efmCuPmeSnrMgnCrossingEnable, 2997 efmCuPmeLineAtnCrossingEnable, 2998 efmCuPmeDeviceFaultEnable, 2999 efmCuPmeConfigInitFailEnable, 3000 efmCuPmeProtocolInitFailEnable 3001 -- efmCuPmeThreshES, 3002 -- efmCuPmethreshSES, 3003 -- efmCuPmeThreshCRCanomalies, 3004 -- efmCuPmeThreshLOSWS, 3005 -- efmCuPmeThreshUAS 3006 } 3007 STATUS current 3008 DESCRIPTION 3009 "A collection of objects required for configuration of alarm 3010 thresholds and notifications in EFMCu ports." 3011 ::= { efmCuGroups 6 } 3013 efmCuNotificationGroup NOTIFICATION-GROUP 3014 NOTIFICATIONS { 3015 efmCuLowBandwidth, 3016 efmCuPmeLineAtnCrossing, 3017 efmCuPmeSnrMgnCrossing, 3018 efmCuPmeDeviceFault, 3019 efmCuPmeConfigInitFailure, 3020 efmCuPmeProtocolInitFailure 3021 -- efmCuPmePerfES, 3022 -- efmCuPmePerfSES, 3023 -- efmCuPmePerfCRCanomalies, 3024 -- efmCuPmePerfLOSWS, 3025 -- efmCuPmePerfUAS, 3026 -- efmCuPmeDeviceFault, 3027 -- efmCuPmeLocalPowerLoss 3028 } 3029 STATUS current 3030 DESCRIPTION 3031 "This group supports notifications of significant conditions 3032 associated with EFMCu ports." 3033 ::= { efmCuGroups 7 } 3035 efmCuPme2BProfileGroup OBJECT-GROUP 3036 OBJECTS { 3037 efmCuPme2BProfileDescr, 3038 efmCuPme2BRegion, 3039 efmCuPme2BDataRate, 3040 efmCuPme2BPower, 3041 efmCuPme2BConstellation, 3042 efmCuPme2BProfileRowStatus 3043 } 3044 STATUS current 3045 DESCRIPTION 3046 "A collection of objects that constitute a configuration 3047 profile for configuration of 2BASE-TL ports." 3048 ::= { efmCuGroups 8 } 3050 efmCuPme10PProfileGroup OBJECT-GROUP 3051 OBJECTS { 3052 efmCuPme10PProfileDescr, 3053 efmCuPme10PBandplanPSDMskProfile, 3054 efmCuPme10PUPBOReferenceProfile, 3055 efmCuPme10PBandNotchProfiles, 3056 efmCuPme10PPayloadURateProfile, 3057 efmCuPme10PPayloadDRateProfile, 3058 efmCuPme10PProfileRowStatus 3059 } 3060 STATUS current 3061 DESCRIPTION 3062 "A collection of objects that constitute a configuration 3063 profile for configuration of 10PASS-TS ports." 3064 ::= { efmCuGroups 9 } 3066 efmCuPme10PStatusGroup OBJECT-GROUP 3067 OBJECTS { 3068 efmCuPme10PElectricalLength, 3069 efmCuPme10PFECCorrectedBlocks, 3070 efmCuPme10PFECUncorrectedBlocks 3071 } 3072 STATUS current 3073 DESCRIPTION 3074 "A collection of objects providing status information 3075 specific to 10PASS-TS PMEs." 3076 ::= { efmCuGroups 10 } 3078 -- Compliance Statements 3080 efmCuCompliance MODULE-COMPLIANCE 3081 STATUS current 3082 DESCRIPTION 3083 "The compliance statement for 2BASE-TL/10PASS-TS interfaces. 3084 Compliance with the following external compliance statements 3085 is prerequisite: 3087 MIB Module Compliance Statement 3088 ---------- -------------------- 3089 IF-MIB ifCompliance3 3090 IF-INVERTED-STACK-MIB ifInvCompliance 3091 EtherLike-MIB dot3Compliance2 3092 MAU-MIB mauModIfCompl3" 3094 MODULE -- this module 3095 MANDATORY-GROUPS { 3096 efmCuBasicGroup, 3097 efmCuPmeGroup, 3098 efmCuAlarmConfGroup, 3099 efmCuNotificationGroup 3100 } 3102 GROUP efmCuPme2BProfileGroup 3103 DESCRIPTION 3104 "Support for this group is only required for implementations 3105 supporting 2BASE-TL Phy." 3107 GROUP efmCuPme10PProfileGroup 3108 DESCRIPTION 3109 "Support for this group is only required for implementations 3110 supporting 10PASS-TS Phy." 3112 GROUP efmCuPAFGroup 3113 DESCRIPTION 3114 "Support for this group is only required for 3115 implementations supporting PME Aggregation Function (PAF)." 3117 GROUP ifStackCapabilityGroup 3118 DESCRIPTION 3119 "Support for this group is optional for implementations 3120 supporting layered interfaces architecture with 3121 flexible cross-connect between the layers." 3123 GROUP efmCuPAFErrorsGroup 3124 DESCRIPTION 3125 "Support for this group is optional for implementations 3126 supporting PME Aggregation Function (PAF)." 3128 GROUP efmCuPme10PStatusGroup 3129 DESCRIPTION 3130 "Support for this group is optional for implementations 3131 supporting 10PASS-TS Phy." 3133 OBJECT efmCuPmeSubTypesSupported 3134 SYNTAX BITS { 3135 ieee2BaseTLO(0), 3136 ieee2BaseTLR(1), 3137 ieee10PassTSO(2), 3138 ieee10PassTSR(3) 3139 } 3140 DESCRIPTION 3141 "Support for all subtypes is not required. However at least 3142 one value SHALL be supported" 3144 OBJECT efmCuPmeAdminSubType 3145 MIN-ACCESS read-only 3146 DESCRIPTION 3147 "Write access is not required (needed only for PMEs 3148 supporting more than a single subtype, e.g. 3149 ieee2BaseTLO and ieee2BaseTSR or ieee2BaseTLR and 3150 ieee10PassTSR)" 3152 OBJECT efmCuTargetSnrMgn 3153 MIN-ACCESS read-only 3154 DESCRIPTION 3155 "Write access is optional. For PHYs without write access 3156 the target SNR margin SHALL be fixed at 5dB for 2BASE-TL 3157 and 6dB for 10PASS-TS." 3159 -- EdNote: To be Continued 3161 ::= { efmCuCompliances 1 } 3162 END 3164 6. Security Considerations 3166 There is a number of managed objects defined in this MIB module that 3167 have a MAX-ACCESS clause of read-write or read-create. Most objects 3168 are writeable only when the link is Down. Writing to these objects 3169 can have potentially disruptive effects on network operation, for 3170 example: 3172 o Changing of efmCuPmeAdminSubType MAY lead to a potential locking 3173 of the link, as peer PMEs of the same sub-type cannot exchange 3174 handshake messages. 3176 o Changing of efmCuPAFAdminState to enabled MAY lead to a potential 3177 locking of the link, if the peer Phy does not support PAF. 3179 o Changing of efmCuPAFDiscoveryCode, before the discovery operation, 3180 MAY lead to a wrongful discovery, for example when two -O ports 3181 are connected to the same multi-PME -R port and both -O ports have 3182 the same Discovery register value. 3184 o Changing PCS or PME configuration parameters (e.g. profile of a 3185 PCS or PME via efmCuAdminProfile or efmCuPmeAdminProfile) MAY lead 3186 to anything from link quality and rate degradation to a complete 3187 link initialization failure, as ability of an EFMCu port to 3188 support a particular configuration depends on the copper 3189 environment. 3191 o Activation of a PME can cause a severe degradation of service for 3192 another EFMCu Phy, whose PME(s) MAY be affected by the cross-talk 3193 from the newly activated PME. 3195 o Removal of a PME from an operationally 'up' EFMCu port, 3196 aggregating several PMEs, MAY cause port's rate degradation 3198 The user of this MIB module must therefore be aware that support for 3199 SET operations in a non-secure environment without proper protection 3200 can have a negative effect on network operations. 3202 The readable objects in this MIB module (i.e., those with MAX-ACCESS 3203 other than not-accessible) may be considered sensitive in some 3204 environments since, collectively, they provide information about the 3205 performance of network interfaces and can reveal some aspects of 3206 their configuration. In particular since EFMCu can be carried over 3207 Unshielded Twisted Pair (UTP) voice grade copper in a bundle with 3208 other pairs belonging to another operator/customer, it is 3209 theoretically possible to evasdrop to an EFMCu transmission simply by 3210 "listening" to a cross-talk from an EFMCu pair, especially if the 3211 parameters of the EFMCu link in question are known. In such 3212 environments it is important to control even GET and NOTIFY access to 3213 these objects and possibly even to encrypt their values when sending 3214 them over the network via SNMP. 3216 SNMP versions prior to SNMPv3 did not include adequate security. 3217 Even if the network itself is secure (for example by using IPSec), 3218 even then, there is no control as to who on the secure network is 3219 allowed to access and GET/SET (read/change/create/delete) the objects 3220 in this MIB module. 3222 It is RECOMMENDED that implementers consider the security features as 3223 provided by the SNMPv3 framework (see [RFC3410], section 8), 3224 including full support for the SNMPv3 cryptographic mechanisms (for 3225 authentication and privacy). 3227 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3228 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3229 enable cryptographic security. It is then a customer/operator 3230 responsibility to ensure that the SNMP entity giving access to an 3231 instance of this MIB module is properly configured to give access to 3232 the objects only to those principals (users) that have legitimate 3233 rights to indeed GET or SET (change/create/delete) them. 3235 7. IANA Considerations 3237 The two new values of dot3MauType (dot3MauType2BaseTL and 3238 dot3MauType10PassTS) and corresponding IANAifMauTypeListBits bit 3239 definitions (b2BaseTL and b10PassTS) SHALL be defined by the IANA in 3240 the IANA-MAU-TC-MIB module (see [I-D.ietf-hubmib-rfc3636bis]) before 3241 this document is published as an RFC. 3243 8. Acknowledgments 3245 This document was produced by the IETF Ethernet Interfaces and Hub 3246 MIB Working Group, whose efforts were greatly advanced by the 3247 contributions of the following people (in alphabetical order): 3249 Dan Romascanu 3251 Mathias Riess 3253 Matt Squire 3255 Mike Heard 3257 Udi Ashkenazi 3259 9. References 3261 9.1 Normative References 3263 [802.3ah] IEEE, "IEEE Standard for Information technology - 3264 Telecommunications and information exchange between 3265 systems - Local and metropolitan area networks - Specific 3266 requirements - Part 3: Carrier Sense Multiple Access with 3267 Collision Detection (CSMA/CD) Access Method and Physical 3268 Layer Specifications - Amendment: Media Access Control 3269 Parameters, Physical Layers and Management Parameters for 3270 Subscriber Access Networks", IEEE Std 802.3ah-2004, 3271 September 2004. 3273 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3274 Requirement Levels", BCP 14, RFC 2119, March 1997. 3276 [RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart, 3277 "Introduction to Version 3 of the Internet-standard 3278 Network Management Framework", RFC 2570, April 1999. 3280 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3281 McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of 3282 Management Information Version 2 (SMIv2)", STD 58, RFC 3283 2578, April 1999. 3285 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3286 McCloghrie, K., Rose, M. and S. Waldbusser, "Textual 3287 Conventions for SMIv2", STD 58, RFC 2579, April 1999. 3289 [RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder, 3290 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3291 April 1999. 3293 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 3294 "Introduction and Applicability Statements for 3295 Internet-Standard Management Framework", RFC 3410, 3296 December 2002. 3298 9.2 Informative References 3300 [G.991.2] ITU-T, "Single-pair High-speed Digital Subscriber Line 3301 (SHDSL) transceivers", ITU-T Recommendation G.991.2, 3302 December 2003. 3304 [G.993.1] ITU-T, "Very High speed Digital Subscriber Line 3305 transceivers", ITU-T Recommendation G.993.1, June 2004. 3307 [I-D.ietf-adslmib-gshdslbis] 3308 Sikes, C., Ray, B. and R. Abbi, "Definitions of Managed 3309 Objects for G.shdsl.bis Lines", 3310 draft-ietf-adslmib-gshdslbis-09 (work in progress), March 3311 2005. 3313 [I-D.ietf-adslmib-vdsl-ext-mcm] 3314 Dodge, M. and B. Ray, "Definitions of Managed Object 3315 Extensions for Very High Speed Digital Subscriber Lines 3316 (VDSL) Using Multiple Carrier Modulation (MCM) Line 3317 Coding", draft-ietf-adslmib-vdsl-ext-mcm-06 (work in 3318 progress), January 2005. 3320 [I-D.ietf-hubmib-efm-epon-mib] 3321 Khermosh, L., "Managed Objects for the Ethernet Passive 3322 Optical Networks", draft-ietf-hubmib-efm-epon-mib-03 (work 3323 in progress), March 2005. 3325 [I-D.ietf-hubmib-efm-mib] 3326 Squire, M., "Ethernet in the First Mile (EFM) Common MIB", 3327 draft-ietf-hubmib-efm-mib-03 (work in progress), March 3328 2005. 3330 [I-D.ietf-hubmib-rfc3636bis] 3331 Beili, E., "Definitions of Managed Objects for IEEE 802.3 3332 Medium Attachment Units (MAUs)", 3333 draft-ietf-hubmib-rfc3636bis-00 (work in progress), 3334 October 2004. 3336 [IANAifType-MIB] 3337 Internet Assigned Numbers Authority (IANA), "IANAifType 3338 Textual Convention definition", 3339 http://www.iana.org/assignments/ianaiftype-mib. 3341 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 3342 MIB", RFC 2863, June 2000. 3344 [RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table 3345 Extension to the Interfaces Group MIB", RFC 2864, June 3346 2000. 3348 [RFC3635] Flick, J., "Definitions of Managed Objects for the 3349 Ethernet-like Interface Types", RFC 3635, September 2003. 3351 Author's Address 3353 Edward Beili 3354 Actelis Networks 3355 Bazel 25 3356 Petach-Tikva 3357 Israel 3359 Phone: +972-3-924-3491 3360 EMail: edward.beili@actelis.com 3362 Intellectual Property Statement 3364 The IETF takes no position regarding the validity or scope of any 3365 Intellectual Property Rights or other rights that might be claimed to 3366 pertain to the implementation or use of the technology described in 3367 this document or the extent to which any license under such rights 3368 might or might not be available; nor does it represent that it has 3369 made any independent effort to identify any such rights. Information 3370 on the procedures with respect to rights in RFC documents can be 3371 found in BCP 78 and BCP 79. 3373 Copies of IPR disclosures made to the IETF Secretariat and any 3374 assurances of licenses to be made available, or the result of an 3375 attempt made to obtain a general license or permission for the use of 3376 such proprietary rights by implementers or users of this 3377 specification can be obtained from the IETF on-line IPR repository at 3378 http://www.ietf.org/ipr. 3380 The IETF invites any interested party to bring to its attention any 3381 copyrights, patents or patent applications, or other proprietary 3382 rights that may cover technology that may be required to implement 3383 this standard. Please address the information to the IETF at 3384 ietf-ipr@ietf.org. 3386 Disclaimer of Validity 3388 This document and the information contained herein are provided on an 3389 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 3390 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 3391 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 3392 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 3393 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3394 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 3396 Copyright Statement 3398 Copyright (C) The Internet Society (2005). This document is subject 3399 to the rights, licenses and restrictions contained in BCP 78, and 3400 except as set forth therein, the authors retain all their rights. 3402 Acknowledgment 3404 Funding for the RFC Editor function is currently provided by the 3405 Internet Society.