smilint output for ./EFM-CU-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| error | 2 |
| Message Types |
|---|
| Type | Count |
|---|
| bad-identifier-case (error) | 1 |
| object-identifier-not-prefix (error) | 1 |
Messages:
EFM-CU-MIB
1: -- extracted from draft-ietf-hubmib-efm-cu-mib-08.txt
2: -- at Tue Jul 31 06:08:51 2007
3:
4: EFM-CU-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32,
8: Unsigned32, Counter32, mib-2
9: FROM SNMPv2-SMI -- RFC 2578
10: TEXTUAL-CONVENTION, TruthValue, RowStatus, PhysAddress
11: FROM SNMPv2-TC -- RFC 2579
12: MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
13: FROM SNMPv2-CONF -- RFC 2580
14: SnmpAdminString
15: FROM SNMP-FRAMEWORK-MIB -- RFC 3411
16: ifIndex, ifSpeed
17: FROM IF-MIB -- RFC 2863
18: ;
19:
20: efmCuMIB MODULE-IDENTITY
21: LAST-UPDATED "200707290000Z" -- July 29, 2007
22: ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group"
23: CONTACT-INFO
24: "WG charter:
25: http://www.ietf.org/html.charters/hubmib-charter.html
26:
27: Mailing Lists:
28: General Discussion: hubmib@ietf.org
29: To Subscribe: hubmib-request@ietf.org
30: In Body: subscribe your_email_address
31:
32: Chair: Bert Wijnen
33: Postal: Alcatel-Lucent
34: Schagen 33
35: 3461 GL Linschoten
36: Netherlands
37: Phone: +31-348-407-775
38: Email: bwijnen@alcatel-lucent.com
39:
40: Editor: Edward Beili
41: Postal: Actelis Networks Inc.
42: 25 Bazel St., P.O.B. 10173
43: Petach-Tikva 10173
44: Israel
45: Phone: +972-3-924-3491
46: Email: edward.beili@actelis.com"
47:
48: DESCRIPTION
49: "The objects in this MIB module are used to manage
50: the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces
51: 2BASE-TL and 10PASS-TS, defined in IEEE Std. 802.3ah-2004,
52: which is now a part of IEEE Std. 802.3-2005.
53:
54: The following references are used throughout this MIB module:
55:
56: [802.3ah] refers to:
57: IEEE Std 802.3ah-2004: 'IEEE Standard for Information
58: technology - Telecommunications and information exchange
59: between systems - Local and metropolitan area networks -
60: Specific requirements -
61: Part 3: Carrier Sense Multiple Access with Collision
62: Detection (CSMA/CD) Access Method and Physical Layer
63: Specifications -
64: Amendment: Media Access Control Parameters, Physical
65: Layers and Management Parameters for Subscriber Access
66: Networks', 07 September 2004.
67:
68: Of particular interest are Clause 61, 'Physical Coding
69: Sublayer (PCS) and common specifications, type 10PASS-TS and
70: type 2BASE-TL', Clause 30, 'Management', Clause 45,
71: 'Management Data Input/Output (MDIO) Interface', Annex 62A,
72: 'PMD profiles for 10PASS-TS' and Annex 63A, 'PMD profiles for
73: 2BASE-TL'.
74:
75: [G.991.2] refers to:
76: ITU-T Recommendation G.991.2: 'Single-pair High-speed Digital
77: Subscriber Line (SHDSL) transceivers', December 2003.
78:
79: [ANFP] refers to:
80: NICC Document ND1602:2005/08: 'Specification of the Access
81: Network Frequency Plan (ANFP) applicable to transmission
82: systems used on the BT Access Network,' August 2005.
83:
84: The following normative documents are quoted by the DESCRIPTION
85: clauses in this MIB module:
86:
87: [G.993.1] refers to:
88: ITU-T Recommendation G.993.1: 'Very High speed Digital
89: Subscriber Line transceivers', June 2004.
90:
91: [T1.424] refers to:
92: ANSI T1.424-2004: 'Interface Between Networks and Customer
93: Installation Very-high-bit-rate Digital Subscriber Lines
94: (VDSL) Metallic Interface (DMT Based)', June 2004.
95:
96: [TS 101 270-1] refers to:
97: ETSI TS 101 270-1: 'Transmission and Multiplexing (TM);
98: Access transmission systems on metallic access cables;
99: Very high speed Digital Subscriber Line (VDSL); Part 1:
100: Functional requirements', October 2005.
101:
102: Naming Conventions:
103: Atn - Attenuation
104: CO - Central Office
105: CPE - Customer Premises Equipment
106: EFM - Ethernet in the First Mile
107: EFMCu - EFM Copper
108: MDIO - Management Data Input/Output
109: Mgn - Margin
110: PAF - PME Aggregation Function
111: PBO - Power Back-Off
112: PCS - Physical Coding Sublayer
113: PMD - Physical Medium Dependent
114: PME - Physical Medium Entity
115: PSD - Power Spectral Density
116: SNR - Signal to Noise Ratio
117: TCPAM - Trellis Coded Pulse Amplitude Modulation
118:
119: Copyright (C) The IETF Trust (2007). This version
120: of this MIB module is part of RFC XXXX; see the RFC
121: itself for full legal notices."
122:
123: REVISION "200707290000Z" -- July 29, 2007
124: DESCRIPTION "Initial version, published as RFC XXXX."
125:
126: -- EdNote: Replace XXXX with the actual RFC number &
127: -- remove this note
128:
129: ::= { mib-2 YYY }
129: error -
`YYY' should start with a lower case letter
129: error -
Object identifier element `YYY' name only allowed as first element
130:
131: -- EdNote: Replace YYY with a real OID once it is
132: -- allocated & remove this note.
133:
134: -- Sections of the module
135:
136: efmCuObjects OBJECT IDENTIFIER ::= { efmCuMIB 1 }
137:
138: efmCuConformance OBJECT IDENTIFIER ::= { efmCuMIB 2 }
139:
140: -- Groups in the module
141:
142: efmCuPort OBJECT IDENTIFIER ::= { efmCuObjects 1 }
143:
144: efmCuPme OBJECT IDENTIFIER ::= { efmCuObjects 2 }
145:
146: -- Textual Conventions
147:
148: EfmProfileIndex ::= TEXTUAL-CONVENTION
149: DISPLAY-HINT "d"
150: STATUS current
151: DESCRIPTION
152: "A unique value, greater than zero, for each PME configuration
153: profile in the managed EFMCu port. It is RECOMMENDED that
154: values are assigned contiguously starting from 1. The value
155: for each profile MUST remain constant at least from one
156: re-initialization of the entity's network management system
157: to the next re-initialization."
158: SYNTAX Unsigned32 (1..255)
159:
160: EfmProfileIndexOrZero ::= TEXTUAL-CONVENTION
161: DISPLAY-HINT "d"
162: STATUS current
163: DESCRIPTION
164: "This textual convention is an extension of EfmProfileIndex
165: convention. The latter defines a greater than zero value used
166: to identify a PME profile in the managed EFMCu port. This
167: extension permits the additional value of zero. The value of
168: zero is object-specific and MUST therefore be defined as part
169: of the description of any object which uses this syntax.
170: Examples of the usage of zero value might include situations
171: where current operational profile is unknown."
172: SYNTAX Unsigned32 (0..255)
173:
174: EfmProfileIndexList ::= TEXTUAL-CONVENTION
175: DISPLAY-HINT "1d:"
176: STATUS current
177: DESCRIPTION
178: "This textual convention represents a list of up to 6
179: EfmProfileIndex values, any of which can be chosen for
180: configuration of an PME in a managed EFMCu port.
181: The EfmProfileIndex textual convention defines a greater than
182: zero value used to identify a PME profile.
183: The value of this object is a concatenation of zero or
184: more (up to 6) octets, where each octet contains an 8-bit
185: EfmProfileIndex value.
186: A zero-length octet string is object-specific and MUST
187: therefore be defined as part of the description of any object
188: which uses this syntax. Examples of the usage of a zero-length
189: value might include situations where an object using this
190: textual convention is irrelevant for a specific EFMCu port
191: type."
192: SYNTAX OCTET STRING (SIZE(0..6))
193:
194: EfmTruthValueOrUnknown ::= TEXTUAL-CONVENTION
195: STATUS current
196: DESCRIPTION
197: "This textual convention is an extension of the TruthValue
198: convention. The latter defines a boolean value with possible
199: values of true(1) and false(2). This extension permits the
200: additional value of unknown(0), that can be returned as the
201: result of a GET operation, when an exact true or false value
202: of the object cannot be determined."
203: SYNTAX INTEGER { unknown(0), true(1), false(2) }
204:
205: -- Port Notifications Group
206:
207: efmCuPortNotifications OBJECT IDENTIFIER ::= { efmCuPort 0 }
208:
209: efmCuLowRateCrossing NOTIFICATION-TYPE
210: OBJECTS {
211: ifSpeed,
212: efmCuThreshLowRate
213: }
214: STATUS current
215: DESCRIPTION
216: "This notification indicates that the EFMCu port's data rate
217: has reached/dropped below or exceeded the low rate threshold,
218: specified by efmCuThreshLowRate.
219:
220: This notification MAY be sent for the -O subtype ports
221: (2BaseTL-O/10PassTS-O) while the port is up, on the crossing
222: event in both directions: from normal (rate is above the
223: threshold) to low (rate equals the threshold or below it) and
224: from low to normal. This notification is not applicable to
225: the -R subtypes.
226:
227: It is RECOMMENDED that a small debouncing period of 2.5 sec,
228: between the detection of the condition and the notification,
229: is implemented to prevent simultaneous LinkUp/LinkDown and
230: efmCuLowRateCrossing notifications to be sent.
231:
232: The adaptive nature of the EFMCu technology allows the port to
233: adapt itself to the changes in the copper environment, e.g.
234: an impulse noise, alien crosstalk or a micro-interruption may
235: temporarily drop one or more PMEs in the aggregation group,
236: causing a rate degradation of the aggregated EFMCu link.
237: The dropped PMEs would then try to re-initialize, possibly at
238: a lower rate than before, adjusting the rate to provide
239: required target SNR margin.
240:
241: Generation of this notification is controlled by the
242: efmCuLowRateCrossingEnable object."
243: ::= { efmCuPortNotifications 1 }
244:
245: -- PCS Port group
246:
247: efmCuPortConfTable OBJECT-TYPE
248: SYNTAX SEQUENCE OF EfmCuPortConfEntry
249: MAX-ACCESS not-accessible
250: STATUS current
251: DESCRIPTION
252: "Table for Configuration of EFMCu 2BASE-TL/10PASS-TS (PCS)
253: Ports. Entries in this table MUST be maintained in a
254: persistent manner"
255: ::= { efmCuPort 1 }
256:
257: efmCuPortConfEntry OBJECT-TYPE
258: SYNTAX EfmCuPortConfEntry
259: MAX-ACCESS not-accessible
260: STATUS current
261: DESCRIPTION
262: "An entry in the EFMCu Port Configuration table.
263: Each entry represents an EFMCu port indexed by the ifIndex.
264: Note that an EFMCu PCS port runs on top of a single
265: or multiple PME port(s), which are also indexed by ifIndex."
266: INDEX { ifIndex }
267: ::= { efmCuPortConfTable 1 }
268:
269: EfmCuPortConfEntry ::=
270: SEQUENCE {
271: efmCuPAFAdminState INTEGER,
272: efmCuPAFDiscoveryCode PhysAddress,
273: efmCuAdminProfile EfmProfileIndexList,
274: efmCuTargetDataRate Unsigned32,
275: efmCuTargetSnrMgn Unsigned32,
276: efmCuAdaptiveSpectra TruthValue,
277: efmCuThreshLowRate Unsigned32,
278: efmCuLowRateCrossingEnable TruthValue
279: }
280:
281: efmCuPAFAdminState OBJECT-TYPE
282: SYNTAX INTEGER {
283: enabled(1),
284: disabled(2)
285: }
286: MAX-ACCESS read-write
287: STATUS current
288: DESCRIPTION
289: "Administrative (desired) state of the PAF of the EFMCu port
290: (PCS).
291: When 'disabled', PME Aggregation will not be performed by the
292: PCS. No more than a single PME can be assigned to this PCS in
293: this case.
294: When 'enabled', PAF will be performed by the PCS when the link
295: is Up, even on a single attached PME, if PAF is supported.
296:
297: PCS ports incapable of supporting PAF SHALL return a value of
298: 'disabled'. Attempts to 'enable' such ports SHALL be rejected.
299:
300: A PAF 'enabled' port with multiple PMEs assigned cannot be
301: 'disabled'. Attempts to 'disable' such port SHALL be rejected,
302: until at most one PME is left assigned.
303:
304: Changing PAFAdminState is a traffic disruptive operation and
305: as such SHALL be done when the link is Down. Attempts to
306: change this object SHALL be rejected if the link is Up or
307: Initializing.
308:
309: This object maps to the Clause 30 attribute aPAFAdminState.
310: If a Clause 45 MDIO Interface to the PCS is present, then this
311: object maps to the PAF enable bit in the 10P/2B PCS control
312: register.
313:
314: This object MUST be maintained in a persistent manner."
315: REFERENCE
316: "[802.3ah] 61.2.2, 45.2.3.18.3"
317: ::= { efmCuPortConfEntry 1 }
318:
319: efmCuPAFDiscoveryCode OBJECT-TYPE
320: SYNTAX PhysAddress (SIZE(0|6))
321: MAX-ACCESS read-write
322: STATUS current
323: DESCRIPTION
324: "PAF Discovery Code of the EFMCu port (PCS).
325: A unique 6 octet long code used by the Discovery function,
326: when PAF is supported.
327: PCS ports incapable of supporting PAF SHALL return a
328: zero-length octet string on an attempt to read this object.
329: An attempt to write to this object SHALL be rejected for such
330: ports.
331: This object MUST be instantiated for the -O subtype PCS before
332: writing operations on the efmCuPAFRemoteDiscoveryCode
333: (Set_if_Clear and Clear_if_Same) are performed by PMEs
334: associated with the PCS.
335: The initial value of this object for -R subtype ports after
336: reset is all zeroes. For -R subtype ports, the value of this
337: object cannot be changed directly. This value may be changed
338: as a result of writing operation on the
339: efmCuPAFRemoteDiscoveryCode object of remote PME of -O
340: subtype, connected to one of the local PMEs associated with
341: the PCS.
342:
343: Discovery MUST be performed when the link is Down.
344: Attempts to change this object MUST be rejected (in case of
345: SNMP with the error inconsistentValue), if the link is Up or
346: Initializing.
347:
348: The PAF Discovery code maps to the local Discovery code
349: variable in PAF (note that it does not have a corresponding
350: Clause 45 register)"
351: REFERENCE
352: "[802.3ah] 61.2.2.8.3, 61.2.2.8.4, 45.2.6.6.1, 45.2.6.8,
353: 61A.2"
354: ::= { efmCuPortConfEntry 2 }
355:
356: efmCuAdminProfile OBJECT-TYPE
357: SYNTAX EfmProfileIndexList
358: MAX-ACCESS read-write
359: STATUS current
360: DESCRIPTION
361: "Desired configuration profile(s), common for all PMEs in the
362: EFMCu port. This object is a list of pointers to entries in
363: either efmCuPme2BProfileTable or
364: efmCuPme10PProfileTable, depending on the current
365: operating SubType of the EFMCu port as indicated by
366: efmCuPortSide.
367: The value of this object is a list of up to 6 indices of
368: profiles. If this list consists of a single profile index,
369: then all PMEs assigned to this EFMCu port SHALL be configured
370: according to the profile referenced by that index, unless it
371: is overwritten by a corresponding non-zero
372: efmCuPmeAdminProfile instance, which takes precedence over
373: efmCuAdminProfile.
374: A list consisting of more than one index allows each PME
375: in the port to be configured according to any profile
376: specified in the list.
377: By default this object has a value of 0x01, referencing the
378: 1st entry in efmCuPme2BProfileTable or
379: efmCuPme10PProfileTable.
380:
381: This object is writable and readable for the -O subtype
382: (2BaseTL-O or 10PassTS-O) EFMCu ports. It is irrelevant for
383: the -R subtype (2BaseTL-R or 10PassTS-R) ports - a
384: zero-length octet string SHALL be returned on an attempt to
385: read this object and an attempt to change this object MUST be
386: rejected in this case.
387:
388: Note that the current operational profile value is available
389: via the efmCuPmeOperProfile object.
390:
391: Any modification of this object MUST be performed when the
392: link is Down. Attempts to change this object MUST be rejected,
393: if the link is Up or Initializing.
394: Attempts to set this object to a list with a member value that
395: is not the value of the index for an active entry in the
396: corresponding profile table MUST be rejected.
397:
398: This object maps to the Clause 30 attribute aProfileSelect.
399:
400: This object MUST be maintained in a persistent manner."
401: REFERENCE
402: "[802.3ah] 30.11.2.1.6"
403: DEFVAL { '01'H }
404: ::= { efmCuPortConfEntry 3 }
405:
406: efmCuTargetDataRate OBJECT-TYPE
407: SYNTAX Unsigned32(1..100000|999999)
408: UNITS "Kbps"
409: MAX-ACCESS read-write
410: STATUS current
411: DESCRIPTION
412: "Desired EFMCu port 'net' (as seen across MII) Data Rate in
413: Kbps, to be achieved during initialization, under spectral
414: restrictions placed on each PME via efmCuAdminProfile or
415: efmCuPmeAdminProfile, with the desired SNR Margin specified by
416: efmCuTargetSnrMgn.
417: In case of PAF, this object represents a sum of individual PME
418: data rates, modified to compensate for fragmentation and
419: 64/65B framing overhead (e.g. target data rate of 10Mbps
420: SHALL allow lossless transmission of a full-duplex 10Mbps
421: Ethernet frame stream with minimal inter-frame gap).
422:
423: The value is limited above by 100Mbps as this is the max
424: burst rate across MII for EFMCu ports.
425:
426: The value between 1 and 100000 indicates that the total data
427: rate (ifSpeed) of the EFMCu port after initialization SHALL be
428: equal to the target data rate or less, if the target data rate
429: cannot be achieved under spectral restrictions specified by
430: efmCuAdminProfile/efmCuPmeAdminProfile and with the desired
431: SNR margin. In case the copper environment allows to achieve
432: a higher total data rate than that specified by the target,
433: the excess capability SHALL be either converted to additional
434: SNR margin or reclaimed by minimizing transmit power as
435: controlled by efmCuAdaptiveSpectra.
436:
437: The value of 999999 means that the target data rate is not
438: fixed and SHALL be set to the maximum attainable rate during
439: initialization (Best Effort), under specified spectral
440: restrictions and with the desired SNR Margin.
441:
442: This object is read-write for the -O subtype EFMCu ports
443: (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
444:
445: Changing of the Target Data Rate MUST be performed when the
446: link is Down. Attempts to change this object MUST be rejected
447: (in case of SNMP with the error inconsistentValue), if the
448: link is Up or Initializing.
449:
450: Note that the current Data Rate of the EFMCu port is
451: represented by the ifSpeed object of IF-MIB.
452:
453: This object MUST be maintained in a persistent manner."
454: ::= { efmCuPortConfEntry 4 }
455:
456: efmCuTargetSnrMgn OBJECT-TYPE
457: SYNTAX Unsigned32(0..21)
458: UNITS "dB"
459: MAX-ACCESS read-write
460: STATUS current
461: DESCRIPTION
462: "Desired EFMCu port SNR Margin to be achieved on all PMEs
463: assigned to the port, during initialization. (The SNR margin
464: is the difference between the desired SNR and the actual SNR).
465:
466: Note that 802.3ah recommends using a default Target SNR Margin
467: of 5dB for 2BASE-TL ports and 6dB for 10PASS-TS ports in order
468: to achieve a mean Bit Error Rate (BER) of 10^-7 at the PMA
469: service interface.
470:
471: This object is read-write for the -O subtype EFMCu ports
472: (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
473:
474: Changing of the Target SNR Margin MUST be performed when the
475: link is Down. Attempts to change this object MUST be rejected
476: (in case of SNMP with the error inconsistentValue), if the
477: link is Up or Initializing.
478:
479: Note that the current SNR Margin of the PMEs comprising the
480: EFMCu port is represented by efmCuPmeSnrMgn.
481:
482: This object MUST be maintained in a persistent manner."
483: REFERENCE
484: "[802.3ah] 61.1.2"
485: ::= { efmCuPortConfEntry 5 }
486:
487: efmCuAdaptiveSpectra OBJECT-TYPE
488: SYNTAX TruthValue
489: MAX-ACCESS read-write
490: STATUS current
491: DESCRIPTION
492: "Indicates how to utilize excess capacity when the copper
493: environment allows to achieve a higher total data rate than
494: that specified by the efmCuTargetDataRate.
495:
496: A value of true(1) indicates that the excess capability SHALL
497: be reclaimed by minimizing transmit power, e.g. using higher
498: constellations and Power Back-Off, in order to reduce
499: interference to other copper pairs in the binder and the
500: adverse impact to link/system performance.
501: A value of false(2) indicates that the excess capability SHALL
502: be converted to additional SNR margin and spread evenly across
503: all active PMEs assigned to the (PCS) port, to increase link
504: robustness.
505:
506: This object is read-write for the -O subtype EFMCu ports
507: (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
508:
509: Changing of this object MUST be performed when the link is
510: Down. Attempts to change this object MUST be rejected (in case
511: of SNMP with the error inconsistentValue), if the link is Up
512: or Initializing.
513:
514: This object MUST be maintained in a persistent manner."
515: ::= { efmCuPortConfEntry 6 }
516:
517: efmCuThreshLowRate OBJECT-TYPE
518: SYNTAX Unsigned32(1..100000)
519: UNITS "Kbps"
520: MAX-ACCESS read-write
521: STATUS current
522: DESCRIPTION
523: "This object configures the EFMCu port low rate crossing alarm
524: threshold. When the current value of ifSpeed for this port
525: reaches/drops below or exceeds this threshold, an
526: efmCuLowRateCrossing notification MAY be generated if enabled
527: by efmCuLowRateCrossingEnable.
528:
529: This object is read-write for the -O subtype EFMCu ports
530: (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
531:
532: This object MUST be maintained in a persistent manner."
533: ::= { efmCuPortConfEntry 7 }
534:
535: efmCuLowRateCrossingEnable OBJECT-TYPE
536: SYNTAX TruthValue
537: MAX-ACCESS read-write
538: STATUS current
539: DESCRIPTION
540: "Indicates whether efmCuLowRateCrossing notifications should
541: be generated for this interface.
542:
543: A value of true(1) indicates that efmCuLowRateCrossing
544: notification is enabled. A value of false(2) indicates that
545: the notification is disabled.
546:
547: This object is read-write for the -O subtype EFMCu ports
548: (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
549: This object MUST be maintained in a persistent manner."
550: ::= { efmCuPortConfEntry 8 }
551:
552:
553: efmCuPortCapabilityTable OBJECT-TYPE
554: SYNTAX SEQUENCE OF EfmCuPortCapabilityEntry
555: MAX-ACCESS not-accessible
556: STATUS current
557: DESCRIPTION
558: "Table for Capabilities of EFMCu 2BASE-TL/10PASS-TS (PCS)
559: Ports. Entries in this table MUST be maintained in a
560: persistent manner"
561: ::= { efmCuPort 2 }
562:
563: efmCuPortCapabilityEntry OBJECT-TYPE
564: SYNTAX EfmCuPortCapabilityEntry
565: MAX-ACCESS not-accessible
566: STATUS current
567: DESCRIPTION
568: "An entry in the EFMCu Port Capability table.
569: Each entry represents an EFMCu port indexed by the ifIndex.
570: Note that an EFMCu PCS port runs on top of a single
571: or multiple PME port(s), which are also indexed by ifIndex."
572: INDEX { ifIndex }
573: ::= { efmCuPortCapabilityTable 1 }
574:
575: EfmCuPortCapabilityEntry ::=
576: SEQUENCE {
577: efmCuPAFSupported TruthValue,
578: efmCuPeerPAFSupported EfmTruthValueOrUnknown,
579: efmCuPAFCapacity Unsigned32,
580: efmCuPeerPAFCapacity Unsigned32
581: }
582:
583: efmCuPAFSupported OBJECT-TYPE
584: SYNTAX TruthValue
585: MAX-ACCESS read-only
586: STATUS current
587: DESCRIPTION
588: "PME Aggregation Function (PAF) Capability of the EFMCu port
589: (PCS).
590: This object has a value of true(1) when the PCS can perform
591: PME aggregation on the available PMEs.
592: Ports incapable of PAF SHALL return a value of false(2).
593:
594: This object maps to the Clause 30 attribute aPAFSupported.
595:
596: If a Clause 45 MDIO Interface to the PCS is present,
597: then this object maps to the PAF available bit in the
598: 10P/2B capability register."
599: REFERENCE
600: "[802.3ah] 61.2.2, 30.11.1.1.4, 45.2.3.17.1"
601: ::= { efmCuPortCapabilityEntry 1 }
602:
603: efmCuPeerPAFSupported OBJECT-TYPE
604: SYNTAX EfmTruthValueOrUnknown
605: MAX-ACCESS read-only
606: STATUS current
607: DESCRIPTION
608: "PME Aggregation Function (PAF) Capability of the EFMCu port
609: (PCS) link partner.
610: This object has a value of true(1) when the remote PCS can
611: perform PME aggregation on its available PMEs.
612: Ports whose peers are incapable of PAF SHALL return a value
613: of false(2).
614: Ports whose peers cannot be reached because of the link
615: state SHALL return a value of unknown(0).
616:
617: This object maps to the Clause 30 attribute
618: aRemotePAFSupported.
619:
620: If a Clause 45 MDIO Interface to the PCS is present, then
621: this object maps to the Remote PAF supported bit in the
622: 10P/2B capability register."
623: REFERENCE
624: "[802.3ah] 61.2.2, 30.11.1.1.9, 45.2.3.17.2"
625: ::= { efmCuPortCapabilityEntry 2 }
626:
627: efmCuPAFCapacity OBJECT-TYPE
628: SYNTAX Unsigned32 (1..32)
629: MAX-ACCESS read-only
630: STATUS current
631: DESCRIPTION
632: "Number of PMEs that can be aggregated by the local PAF.
633: The number of PMEs currently assigned to a particular
634: EFMCu port (efmCuNumPMEs) is never greater than
635: efmCuPAFCapacity.
636:
637: This object maps to the Clause 30 attribute
638: aLocalPAFCapacity."
639: REFERENCE
640: "[802.3ah] 61.2.2, 30.11.1.1.6"
641: ::= { efmCuPortCapabilityEntry 3 }
642:
643: efmCuPeerPAFCapacity OBJECT-TYPE
644: SYNTAX Unsigned32 (0|1..32)
645: MAX-ACCESS read-only
646: STATUS current
647: DESCRIPTION
648: "Number of PMEs that can be aggregated by the PAF of the peer
649: Phy (PCS port).
650: Value of 0 is returned when peer PAF Capacity is unknown
651: (peer cannot be reached).
652:
653: This object maps to the Clause 30 attribute
654: aRemotePAFCapacity."
655: REFERENCE
656: "[802.3ah] 61.2.2, 30.11.1.1.10"
657: ::= { efmCuPortCapabilityEntry 4 }
658:
659:
660: efmCuPortStatusTable OBJECT-TYPE
661: SYNTAX SEQUENCE OF EfmCuPortStatusEntry
662: MAX-ACCESS not-accessible
663: STATUS current
664: DESCRIPTION
665: "This table provides overall status information of EFMCu
666: 2BASE-TL/10PASS-TS ports, complementing the generic status
667: information from the ifTable of IF-MIB and ifMauTable of
668: MAU-MIB. Additional status information about connected PMEs
669: is available from the efmCuPmeStatusTable.
670:
671: This table contains live data from the equipment. As such,
672: it is NOT persistent."
673: ::= { efmCuPort 3 }
674:
675: efmCuPortStatusEntry OBJECT-TYPE
676: SYNTAX EfmCuPortStatusEntry
677: MAX-ACCESS not-accessible
678: STATUS current
679: DESCRIPTION
680: "An entry in the EFMCu Port Status table.
681: Each entry represents an EFMCu port indexed by the ifIndex.
682: Note that an EFMCu PCS port runs on top of a single
683: or multiple PME port(s), which are also indexed by ifIndex."
684: INDEX { ifIndex }
685: ::= { efmCuPortStatusTable 1 }
686:
687: EfmCuPortStatusEntry ::=
688: SEQUENCE {
689: efmCuFltStatus BITS,
690: efmCuPortSide INTEGER,
691: efmCuNumPMEs Unsigned32,
692: efmCuPAFInErrors Counter32,
693: efmCuPAFInSmallFragments Counter32,
694: efmCuPAFInLargeFragments Counter32,
695: efmCuPAFInBadFragments Counter32,
696: efmCuPAFInLostFragments Counter32,
697: efmCuPAFInLostStarts Counter32,
698: efmCuPAFInLostEnds Counter32,
699: efmCuPAFInOverflows Counter32
700: }
701:
702: efmCuFltStatus OBJECT-TYPE
703: SYNTAX BITS {
704: noPeer(0),
705: peerPowerLoss(1),
706: pmeSubTypeMismatch(2),
707: lowRate(3)
708: }
709: MAX-ACCESS read-only
710: STATUS current
711: DESCRIPTION
712: "EFMCu (PCS) port Fault Status. This is a bitmap of possible
713: conditions. The various bit positions are:
714: noPeer - the peer PHY cannot be reached (e.g.
715: no PMEs attached, all PMEs are Down
716: etc.) More info is available in
717: efmCuPmeFltStatus.
718: peerPowerLoss - the peer PHY has indicated impending
719: unit failure due to loss of local
720: power ('Dying Gasp').
721: pmeSubTypeMismatch - local PMEs in the aggregation group
722: are not of the same sub-type, e.g.
723: some PMEs in the local device are -O
724: while others are -R subtype.
725: lowRate - ifSpeed of the port reached or dropped
726: below efmCuThreshLowRate
727:
728: This object is intended to supplement the ifOperStatus object
729: in IF-MIB and ifMauMediaAvailable in MAU-MIB.
730:
731: Additional information is available via the efmCuPmeFltStatus
732: object for each PME in the aggregation group (single PME if
733: PAF is disabled)."
734: REFERENCE
735: "IF-MIB, ifOperStatus; MAU-MIB, ifMauMediaAvailable;
736: efmCuPmeFltStatus"
737: ::= { efmCuPortStatusEntry 1 }
738:
739: efmCuPortSide OBJECT-TYPE
740: SYNTAX INTEGER {
741: subscriber(1),
742: office(2),
743: unknown(3)
744: }
745: MAX-ACCESS read-only
746: STATUS current
747: DESCRIPTION
748: "EFM port mode of operation (subtype).
749: The value of 'subscriber' indicates the port is designated as
750: '-R' subtype (all PMEs assigned to this port are of subtype
751: '-R').
752: The value of the 'office' indicates that the port is
753: designated as '-O' subtype (all PMEs assigned to this port are
754: of subtype '-O').
755: The value of 'unknown' indicates that the port has no assigned
756: PMEs yet or that the assigned PMEs are not of the same side
757: (subTypePMEMismatch).
758:
759: This object partially maps to the Clause 30 attribute
760: aPhyEnd"
761: REFERENCE
762: "[802.3ah] 61.1, 30.11.1.1.2"
763: ::= { efmCuPortStatusEntry 2 }
764:
765: efmCuNumPMEs OBJECT-TYPE
766: SYNTAX Unsigned32 (0..32)
767: MAX-ACCESS read-only
768: STATUS current
769: DESCRIPTION
770: "The number of PMEs that is currently aggregated by the local
771: PAF (assigned to the EFMCu port using the ifStackTable).
772: This number is never greater than efmCuPAFCapacity.
773:
774: This object SHALL be automatically incremented or decremented
775: when a PME is added or deleted to/from the EFMCu port using
776: the ifStackTable."
777: REFERENCE
778: "[802.3ah] 61.2.2, 30.11.1.1.6"
779: ::= { efmCuPortStatusEntry 3 }
780:
781: efmCuPAFInErrors OBJECT-TYPE
782: SYNTAX Counter32
783: MAX-ACCESS read-only
784: STATUS current
785: DESCRIPTION
786: "The number of fragments that have been received across the
787: gamma interface with RxErr asserted and discarded.
788: This read-only counter is inactive (not incremented) when the
789: PAF is unsupported or disabled. Upon disabling the PAF, the
790: counter retains its previous value.
791:
792: If a Clause 45 MDIO Interface to the PCS is present, then
793: this object maps to the 10P/2B PAF RX error register.
794:
795: Discontinuities in the value of this counter can occur at
796: re-initialization of the management system, and at other times
797: as indicated by the value of ifCounterDiscontinuityTime,
798: defined in IF-MIB."
799: REFERENCE
800: "[802.3ah] 45.2.3.21"
801: ::= { efmCuPortStatusEntry 4 }
802:
803: efmCuPAFInSmallFragments OBJECT-TYPE
804: SYNTAX Counter32
805: MAX-ACCESS read-only
806: STATUS current
807: DESCRIPTION
808: "The number of fragments smaller than minFragmentSize
809: (64 Bytes), which have been received across the gamma
810: interface and discarded.
811: This read-only counter is inactive when the PAF is
812: unsupported or disabled. Upon disabling the PAF, the counter
813: retains its previous value.
814:
815: If a Clause 45 MDIO Interface to the PCS is present, then
816: this object maps to the 10P/2B PAF small fragments
817: register.
818:
819: Discontinuities in the value of this counter can occur at
820: re-initialization of the management system, and at other times
821: as indicated by the value of ifCounterDiscontinuityTime,
822: defined in IF-MIB."
823: REFERENCE
824: "[802.3ah] 45.2.3.22"
825: ::= { efmCuPortStatusEntry 5 }
826:
827: efmCuPAFInLargeFragments OBJECT-TYPE
828: SYNTAX Counter32
829: MAX-ACCESS read-only
830: STATUS current
831: DESCRIPTION
832: "The number of fragments larger than maxFragmentSize
833: (512 Bytes), which have been received across the gamma
834: interface and discarded.
835: This read-only counter is inactive when the PAF is
836: unsupported or disabled. Upon disabling the PAF, the counter
837: retains its previous value.
838:
839: If a Clause 45 MDIO Interface to the PCS is present, then
840: this object maps to the 10P/2B PAF large fragments
841: register.
842:
843: Discontinuities in the value of this counter can occur at
844: re-initialization of the management system, and at other times
845: as indicated by the value of ifCounterDiscontinuityTime,
846: defined in IF-MIB."
847: REFERENCE
848: "[802.3ah] 45.2.3.23"
849: ::= { efmCuPortStatusEntry 6 }
850:
851: efmCuPAFInBadFragments OBJECT-TYPE
852: SYNTAX Counter32
853: MAX-ACCESS read-only
854: STATUS current
855: DESCRIPTION
856: "The number of fragments which do not fit into the sequence
857: expected by the frame assembly function, that have been
858: received across the gamma interface and discarded (the
859: frame buffer is flushed to the next valid frame start).
860: This read-only counter is inactive when the PAF is
861: unsupported or disabled. Upon disabling the PAF, the counter
862: retains its previous value.
863:
864: If a Clause 45 MDIO Interface to the PCS is present, then
865: this object maps to the 10P/2B PAF bad fragments
866: register.
867:
868: Discontinuities in the value of this counter can occur at
869: re-initialization of the management system, and at other times
870: as indicated by the value of ifCounterDiscontinuityTime,
871: defined in IF-MIB."
872: REFERENCE
873: "[802.3ah] 45.2.3.25"
874: ::= { efmCuPortStatusEntry 7 }
875:
876: efmCuPAFInLostFragments OBJECT-TYPE
877: SYNTAX Counter32
878: MAX-ACCESS read-only
879: STATUS current
880: DESCRIPTION
881: "The number of gaps in the sequence of fragments, which have
882: been received across the gamma interface (the frame buffer is
883: flushed to the next valid frame start, when fragment/fragments
884: expected by the frame assembly function is/are not received).
885: This read-only counter is inactive when the PAF is
886: unsupported or disabled. Upon disabling the PAF, the counter
887: retains its previous value.
888:
889: If a Clause 45 MDIO Interface to the PCS is present, then
890: this object maps to the 10P/2B PAF lost fragment
891: register.
892:
893: Discontinuities in the value of this counter can occur at
894: re-initialization of the management system, and at other times
895: as indicated by the value of ifCounterDiscontinuityTime,
896: defined in IF-MIB."
897: REFERENCE
898: "[802.3ah] 45.2.3.26"
899: ::= { efmCuPortStatusEntry 8 }
900:
901: efmCuPAFInLostStarts OBJECT-TYPE
902: SYNTAX Counter32
903: MAX-ACCESS read-only
904: STATUS current
905: DESCRIPTION
906: "The number of missing StartOfPacket indicators expected by
907: the frame assembly function.
908: This read-only counter is inactive when the PAF is
909: unsupported or disabled. Upon disabling the PAF, the counter
910: retains its previous value.
911:
912: If a Clause 45 MDIO Interface to the PCS is present, then
913: this object maps to the 10P/2B PAF lost start of fragment
914: register.
915:
916: Discontinuities in the value of this counter can occur at
917: re-initialization of the management system, and at other times
918: as indicated by the value of ifCounterDiscontinuityTime,
919: defined in IF-MIB."
920: REFERENCE
921: "[802.3ah] 45.2.3.27"
922: ::= { efmCuPortStatusEntry 9 }
923:
924: efmCuPAFInLostEnds OBJECT-TYPE
925: SYNTAX Counter32
926: MAX-ACCESS read-only
927: STATUS current
928: DESCRIPTION
929: "The number of missing EndOfPacket indicators expected by the
930: frame assembly function.
931: This read-only counter is inactive when the PAF is
932: unsupported or disabled. Upon disabling the PAF, the counter
933: retains its previous value.
934:
935: If a Clause 45 MDIO Interface to the PCS is present, then
936: this object maps to the 10P/2B PAF lost start of fragment
937: register.
938:
939: Discontinuities in the value of this counter can occur at
940: re-initialization of the management system, and at other times
941: as indicated by the value of ifCounterDiscontinuityTime,
942: defined in IF-MIB."
943: REFERENCE
944: "[802.3ah] 45.2.3.28"
945: ::= { efmCuPortStatusEntry 10 }
946:
947: efmCuPAFInOverflows OBJECT-TYPE
948: SYNTAX Counter32
949: MAX-ACCESS read-only
950: STATUS current
951: DESCRIPTION
952: "The number of fragments, received across the gamma interface
953: and discarded, which would have caused the frame assembly
954: buffer to overflow.
955: This read-only counter is inactive when the PAF is
956: unsupported or disabled. Upon disabling the PAF, the counter
957: retains its previous value.
958:
959: If a Clause 45 MDIO Interface to the PCS is present, then
960: this object maps to the 10P/2B PAF overflow register.
961:
962: Discontinuities in the value of this counter can occur at
963: re-initialization of the management system, and at other times
964: as indicated by the value of ifCounterDiscontinuityTime,
965: defined in IF-MIB."
966: REFERENCE
967: "[802.3ah] 45.2.3.24"
968: ::= { efmCuPortStatusEntry 11 }
969:
970: -- PME Notifications Group
971:
972: efmCuPmeNotifications OBJECT IDENTIFIER ::= { efmCuPme 0 }
973:
974: efmCuPmeLineAtnCrossing NOTIFICATION-TYPE
975: OBJECTS {
976: efmCuPmeLineAtn,
977: efmCuPmeThreshLineAtn
978: }
979: STATUS current
980: DESCRIPTION
981: "This notification indicates that the loop attenuation
982: threshold (as per the efmCuPmeThreshLineAtn
983: value) has been reached/exceeded for the 2BASE-TL/10PASS-TS
984: PME. This notification MAY be sent on the crossing event in
985: both directions: from normal to exceeded and from exceeded
986: to normal.
987:
988: It is RECOMMENDED that a small debouncing period of 2.5 sec,
989: between the detection of the condition and the notification,
990: is implemented to prevent intermittent notifications to be
991: sent.
992:
993: Generation of this notification is controlled by the
994: efmCuPmeLineAtnCrossingEnable object."
995: ::= { efmCuPmeNotifications 1 }
996:
997: efmCuPmeSnrMgnCrossing NOTIFICATION-TYPE
998: OBJECTS {
999: efmCuPmeSnrMgn,
1000: efmCuPmeThreshSnrMgn
1001: }
1002: STATUS current
1003: DESCRIPTION
1004: "This notification indicates that the SNR margin threshold
1005: (as per the efmCuPmeThreshSnrMgn value) has been
1006: reached/exceeded for the 2BASE-TL/10PASS-TS PME.
1007: This notification MAY be sent on the crossing event in
1008: both directions: from normal to exceeded and from exceeded
1009: to normal.
1010:
1011: It is RECOMMENDED that a small debouncing period of 2.5 sec,
1012: between the detection of the condition and the notification,
1013: is implemented to prevent intermittent notifications to be
1014: sent.
1015:
1016: Generation of this notification is controlled by the
1017: efmCuPmeSnrMgnCrossingEnable object."
1018: ::= { efmCuPmeNotifications 2 }
1019:
1020: efmCuPmeDeviceFault NOTIFICATION-TYPE
1021: OBJECTS {
1022: efmCuPmeFltStatus
1023: }
1024: STATUS current
1025: DESCRIPTION
1026: "This notification indicates that a fault in the PME has been
1027: detected by a vendor specific diagnostic or a self-test.
1028: Generation of this notification is controlled by the
1029: efmCuPmeDeviceFaultEnable object."
1030: ::= { efmCuPmeNotifications 3 }
1031:
1032: efmCuPmeConfigInitFailure NOTIFICATION-TYPE
1033: OBJECTS {
1034: efmCuPmeFltStatus,
1035: efmCuAdminProfile,
1036: efmCuPmeAdminProfile
1037: }
1038: STATUS current
1039: DESCRIPTION
1040: "This notification indicates that PME initialization has
1041: failed, due to inability of the PME link to achieve the
1042: requested configuration profile.
1043:
1044: Generation of this notification is controlled by the
1045: efmCuPmeConfigInitFailEnable object."
1046: ::= { efmCuPmeNotifications 4 }
1047:
1048: efmCuPmeProtocolInitFailure NOTIFICATION-TYPE
1049: OBJECTS {
1050: efmCuPmeFltStatus,
1051: efmCuPmeOperSubType
1052: }
1053: STATUS current
1054: DESCRIPTION
1055: "This notification indicates that the peer PME was using
1056: an incompatible protocol during initialization.
1057:
1058: Generation of this notification is controlled by the
1059: efmCuPmeProtocolInitFailEnable object."
1060: ::= { efmCuPmeNotifications 5 }
1061:
1062: -- The PME group
1063:
1064: efmCuPmeConfTable OBJECT-TYPE
1065: SYNTAX SEQUENCE OF EfmCuPmeConfEntry
1066: MAX-ACCESS not-accessible
1067: STATUS current
1068: DESCRIPTION
1069: "Table for Configuration of common aspects for EFMCu
1070: 2BASE-TL/10PASS-TS PME ports (modems). Configuration of
1071: aspects specific to 2BASE-TL or 10PASS-TS PME types is
1072: represented in efmCuPme2BConfTable and efmCuPme10PConfTable
1073: respectively.
1074:
1075: Entries in this table MUST be maintained in a persistent
1076: manner."
1077: ::= { efmCuPme 1 }
1078:
1079: efmCuPmeConfEntry OBJECT-TYPE
1080: SYNTAX EfmCuPmeConfEntry
1081: MAX-ACCESS not-accessible
1082: STATUS current
1083: DESCRIPTION
1084: "An entry in the EFMCu PME Configuration table.
1085: Each entry represents common aspects of an EFMCu PME port
1086: indexed by the ifIndex. Note that an EFMCu PME port can be
1087: stacked below a single PCS port, also indexed by ifIndex,
1088: possibly together with other PME ports if PAF is enabled."
1089: INDEX { ifIndex }
1090: ::= { efmCuPmeConfTable 1 }
1091:
1092: EfmCuPmeConfEntry ::=
1093: SEQUENCE {
1094: efmCuPmeAdminSubType INTEGER,
1095: efmCuPmeAdminProfile EfmProfileIndexOrZero,
1096: efmCuPAFRemoteDiscoveryCode PhysAddress,
1097: efmCuPmeThreshLineAtn Integer32,
1098: efmCuPmeThreshSnrMgn Integer32,
1099: efmCuPmeLineAtnCrossingEnable TruthValue,
1100: efmCuPmeSnrMgnCrossingEnable TruthValue,
1101: efmCuPmeDeviceFaultEnable TruthValue,
1102: efmCuPmeConfigInitFailEnable TruthValue,
1103: efmCuPmeProtocolInitFailEnable TruthValue
1104: }
1105:
1106: efmCuPmeAdminSubType OBJECT-TYPE
1107: SYNTAX INTEGER {
1108: ieee2BaseTLO(1),
1109: ieee2BaseTLR(2),
1110: ieee10PassTSO(3),
1111: ieee10PassTSR(4),
1112: ieee2BaseTLor10PassTSR(5),
1113: ieee2BaseTLor10PassTSO(6),
1114: ieee10PassTSor2BaseTLO(7)
1115: }
1116: MAX-ACCESS read-write
1117: STATUS current
1118: DESCRIPTION
1119: "Administrative (desired) sub-type of the PME.
1120: Possible values are:
1121: ieee2BaseTLO - PME SHALL operate as 2BaseTL-O
1122: ieee2BaseTLR - PME SHALL operate as 2BaseTL-R
1123: ieee10PassTSO - PME SHALL operate as 10PassTS-O
1124: ieee10PassTSR - PME SHALL operate as 10PassTS-R
1125: ieee2BaseTLor10PassTSR - PME SHALL operate as 2BaseTL-R or
1126: 10PassTS-R. The actual value will
1127: be set by the -O link partner
1128: during initialization (handshake).
1129: ieee2BaseTLor10PassTSO - PME SHALL operate as 2BaseTL-O
1130: (preferred) or 10PassTS-O. The
1131: actual value will be set during
1132: initialization depending on the -R
1133: link partner capability (i.e. if
1134: -R is incapable of the preferred
1135: 2BaseTL mode, 10PassTS will be
1136: used).
1137: ieee10PassTSor2BaseTLO - PME SHALL operate as 10PassTS-O
1138: (preferred) or 2BaseTL-O. The
1139: actual value will be set during
1140: initialization depending on the -R
1141: link partner capability (i.e. if
1142: -R is incapable of the preferred
1143: 10PassTS mode, 2BaseTL will be
1144: used).
1145:
1146: Changing efmCuPmeAdminSubType is a traffic disruptive
1147: operation and as such SHALL be done when the link is Down.
1148: Attempts to change this object SHALL be rejected if the link
1149: is Up or Initializing.
1150: Attempts to change this object to an unsupported subtype
1151: (see efmCuPmeSubTypesSupported) SHALL be rejected.
1152:
1153: The current operational sub type is indicated by the
1154: efmCuPmeOperSubType variable.
1155:
1156: If a Clause 45 MDIO Interface to the PMA/PMD is present, then
1157: this object combines values of the Port sub-type select bits
1158: and the PMA/PMD type selection bits in the 10P/2B PMA/PMD
1159: control register"
1160: REFERENCE
1161: "[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7"
1162: ::= { efmCuPmeConfEntry 1 }
1163:
1164: efmCuPmeAdminProfile OBJECT-TYPE
1165: SYNTAX EfmProfileIndexOrZero
1166: MAX-ACCESS read-write
1167: STATUS current
1168: DESCRIPTION
1169: "Desired PME configuration profile. This object is a pointer
1170: to an entry in either the efmCuPme2BProfileTable or the
1171: efmCuPme10PProfileTable, depending on the current operating
1172: SubType of the PME. The value of this object is the index of
1173: the referenced profile.
1174: The value of zero (default) indicates that the PME is
1175: configured via the efmCuAdminProfile object for the PCS port
1176: to which this PME is assigned. That is, the profile referenced
1177: by efmCuPmeAdminProfile takes precedence over the profile(s)
1178: referenced by efmCuAdminProfile.
1179:
1180: This object is writable and readable for the CO subtype PMEs
1181: (2BaseTL-O or 10PassTS-O). It is irrelevant for the CPE
1182: subtype (2BaseTL-R or 10PassTS-R) - a zero value SHALL be
1183: returned on an attempt to read this object and any attempt
1184: to change this object MUST be rejected in this case.
1185:
1186: Note that the current operational profile value is available
1187: via efmCuPmeOperProfile object.
1188:
1189: Any modification of this object MUST be performed when the
1190: link is Down. Attempts to change this object MUST be rejected,
1191: if the link is Up or Initializing.
1192: Attempts to set this object to a value that is not the value
1193: of the index for an active entry in the corresponding profile
1194: table MUST be rejected.
1195:
1196: This object maps to the Clause 30 attribute aProfileSelect.
1197:
1198: This object MUST be maintained in a persistent manner."
1199: REFERENCE
1200: "[802.3ah] 30.11.2.1.6"
1201: DEFVAL { 0 }
1202: ::= { efmCuPmeConfEntry 2 }
1203:
1204: efmCuPAFRemoteDiscoveryCode OBJECT-TYPE
1205: SYNTAX PhysAddress (SIZE(0|6))
1206: MAX-ACCESS read-write
1207: STATUS current
1208: DESCRIPTION
1209: "PAF Remote Discovery Code of the PME port at the CO.
1210: The 6 octet long Discovery Code of the peer PCS connected via
1211: the PME.
1212: Reading this object results in a Discovery Get operation.
1213: Setting this object to all zeroes results in a Discovery
1214: Clear_if_Same operation (the value of efmCuPAFDiscoveryCode
1215: at the peer PCS SHALL be the same as efmCuPAFDiscoveryCode of
1216: the local PCS associated with the PME for the operation to
1217: succeed).
1218: Writing a non-zero value to this object results in a
1219: Discovery Set_if_Clear operation.
1220: A zero-length octet string SHALL be returned on an attempt to
1221: read this object when PAF aggregation is not enabled.
1222:
1223: This object is irrelevant in CPE port (-R) subtypes: in this
1224: case a zero-length octet string SHALL be returned on an
1225: attempt to read this object, writing to this object SHALL
1226: be rejected.
1227:
1228: Discovery MUST be performed when the link is Down.
1229: Attempts to change this object MUST be rejected (in case of
1230: SNMP with the error inconsistentValue), if the link is Up or
1231: Initializing.
1232:
1233: If a Clause 45 MDIO Interface to the PMA/PMD is present, then
1234: this object is a function of 10P/2B aggregation discovery
1235: control register, Discovery operation result bits in 10P/2B
1236: aggregation and discovery status register and
1237: 10P/2B aggregation discovery code register"
1238: REFERENCE
1239: "[802.3ah] 61.2.2.8.4, 45.2.6.6-45.2.6.8"
1240: ::= { efmCuPmeConfEntry 3 }
1241:
1242: efmCuPmeThreshLineAtn OBJECT-TYPE
1243: SYNTAX Integer32(-127..128)
1244: UNITS "dB"
1245: MAX-ACCESS read-write
1246: STATUS current
1247: DESCRIPTION
1248: "Desired Line Attenuation Threshold for the 2B/10P PME.
1249: This object configures the line attenuation alarm threshold.
1250: When the current value of Line Attenuation reaches or
1251: exceeds this threshold, a efmCuPmeLineAtnCrossing
1252: notification MAY be generated, if enabled by
1253: efmCuPmeLineAtnCrossingEnable.
1254:
1255: This object is writable for the CO subtype PMEs (-O).
1256: It is read-only for the CPE subtype (-R).
1257:
1258: Changing of the Line Attenuation Threshold MUST be performed
1259: when the link is Down. Attempts to change this object MUST be
1260: rejected (in case of SNMP with the error inconsistentValue),
1261: if the link is Up or Initializing.
1262:
1263: If a Clause 45 MDIO Interface to the PME is present, then this
1264: object maps to the Loop attenuation threshold bits in
1265: the 2B PMD line quality thresholds register"
1266: REFERENCE
1267: "[802.3ah] 45.2.1.36"
1268: ::= { efmCuPmeConfEntry 4 }
1269:
1270: efmCuPmeThreshSnrMgn OBJECT-TYPE
1271: SYNTAX Integer32(-127..128)
1272: UNITS "dB"
1273: MAX-ACCESS read-write
1274: STATUS current
1275: DESCRIPTION
1276: "Desired SNR Margin Threshold for the 2B/10P PME.
1277: This object configures the SNR margin alarm threshold.
1278: When the current value of SNR Margin reaches or exceeds this
1279: threshold, a efmCuPmeSnrMgnCrossing notification MAY be
1280: generated, if enabled by efmCuPmeSnrMgnCrossingEnable.
1281:
1282: This object is writable for the CO subtype PMEs
1283: (2BaseTL-O/10PassTS-O). It is read-only for the CPE subtype
1284: (2BaseTL-R/10PassTS-R).
1285:
1286: Changing of the SNR Margin Threshold MUST be performed when
1287: the link is Down. Attempts to change this object MUST be
1288: rejected (in case of SNMP with the error inconsistentValue),
1289: if the link is Up or Initializing.
1290:
1291: If a Clause 45 MDIO Interface to the PME is present, then this
1292: object maps to the SNR margin threshold bits in the 2B PMD
1293: line quality thresholds register"
1294: REFERENCE
1295: "[802.3ah] 45.2.1.36"
1296: ::= { efmCuPmeConfEntry 5 }
1297:
1298: efmCuPmeLineAtnCrossingEnable OBJECT-TYPE
1299: SYNTAX TruthValue
1300: MAX-ACCESS read-write
1301: STATUS current
1302: DESCRIPTION
1303: "Indicates whether efmCuPmeLineAtnCrossing notifications
1304: should be generated for this interface.
1305:
1306: A value of true(1) indicates that efmCuPmeLineAtnCrossing
1307: notification is enabled. Value of false(2) indicates that
1308: the notification is disabled."
1309: ::= { efmCuPmeConfEntry 6 }
1310:
1311: efmCuPmeSnrMgnCrossingEnable OBJECT-TYPE
1312: SYNTAX TruthValue
1313: MAX-ACCESS read-write
1314: STATUS current
1315: DESCRIPTION
1316: "Indicates whether efmCuPmeSnrMgnCrossing notifications
1317: should be generated for this interface.
1318:
1319: A value of true(1) indicates that efmCuPmeSnrMgnCrossing
1320: notification is enabled. Value of false(2) indicates that
1321: the notification is disabled."
1322: ::= { efmCuPmeConfEntry 7 }
1323:
1324: efmCuPmeDeviceFaultEnable OBJECT-TYPE
1325: SYNTAX TruthValue
1326: MAX-ACCESS read-write
1327: STATUS current
1328: DESCRIPTION
1329: "Indicates whether efmCuPmeDeviceFault notifications
1330: should be generated for this interface.
1331:
1332: A value of true(1) indicates that efmCuPmeDeviceFault
1333: notification is enabled. Value of false(2) indicates that
1334: the notification is disabled."
1335: ::= { efmCuPmeConfEntry 8 }
1336:
1337: efmCuPmeConfigInitFailEnable OBJECT-TYPE
1338: SYNTAX TruthValue
1339: MAX-ACCESS read-write
1340: STATUS current
1341: DESCRIPTION
1342: "Indicates whether efmCuPmeConfigInitFailure notifications
1343: should be generated for this interface.
1344:
1345: A value of true(1) indicates that efmCuPmeConfigInitFailure
1346: notification is enabled. A value of false(2) indicates that
1347: the notification is disabled."
1348: ::= { efmCuPmeConfEntry 9 }
1349:
1350: efmCuPmeProtocolInitFailEnable OBJECT-TYPE
1351: SYNTAX TruthValue
1352: MAX-ACCESS read-write
1353: STATUS current
1354: DESCRIPTION
1355: "Indicates whether efmCuPmeProtocolInitFailure notifications
1356: should be generated for this interface.
1357:
1358: A value of true(1) indicates that efmCuPmeProtocolInitFailure
1359: notification is enabled. A value of false(2) indicates that
1360: the notification is disabled."
1361: ::= { efmCuPmeConfEntry 10 }
1362:
1363: efmCuPmeCapabilityTable OBJECT-TYPE
1364: SYNTAX SEQUENCE OF EfmCuPmeCapabilityEntry
1365: MAX-ACCESS not-accessible
1366: STATUS current
1367: DESCRIPTION
1368: "Table for the configuration of common aspects for EFMCu
1369: 2BASE-TL/10PASS-TS PME ports (modems). The configuration of
1370: aspects specific to 2BASE-TL or 10PASS-TS PME types is
1371: represented in the efmCuPme2BConfTable and the
1372: efmCuPme10PConfTable, respectively.
1373:
1374: Entries in this table MUST be maintained in a persistent
1375: manner."
1376: ::= { efmCuPme 2 }
1377:
1378: efmCuPmeCapabilityEntry OBJECT-TYPE
1379: SYNTAX EfmCuPmeCapabilityEntry
1380: MAX-ACCESS not-accessible
1381: STATUS current
1382: DESCRIPTION
1383: "An entry in the EFMCu PME Capability table.
1384: Each entry represents common aspects of an EFMCu PME port
1385: indexed by the ifIndex. Note that an EFMCu PME port can be
1386: stacked below a single PCS port, also indexed by ifIndex,
1387: possibly together with other PME ports if PAF is enabled."
1388: INDEX { ifIndex }
1389: ::= { efmCuPmeCapabilityTable 1 }
1390:
1391: EfmCuPmeCapabilityEntry ::=
1392: SEQUENCE {
1393: efmCuPmeSubTypesSupported BITS
1394: }
1395:
1396: efmCuPmeSubTypesSupported OBJECT-TYPE
1397: SYNTAX BITS {
1398: ieee2BaseTLO(0),
1399: ieee2BaseTLR(1),
1400: ieee10PassTSO(2),
1401: ieee10PassTSR(3)
1402: }
1403: MAX-ACCESS read-only
1404: STATUS current
1405: DESCRIPTION
1406: "PME supported sub-types. This is a bitmap of possible
1407: sub-types. The various bit positions are:
1408: ieee2BaseTLO - PME is capable of operating as 2BaseTL-O
1409: ieee2BaseTLR - PME is capable of operating as 2BaseTL-R
1410: ieee10PassTSO - PME is capable of operating as 10PassTS-O
1411: ieee10PassTSR - PME is capable of operating as 10PassTS-R
1412:
1413: The desired mode of operation is determined by
1414: efmCuPmeAdminSubType, while efmCuPmeOperSubType reflects the
1415: current operating mode.
1416:
1417: If a Clause 45 MDIO Interface to the PCS is present, then this
1418: object combines the 10PASS-TS capable and 2BASE-TL capable
1419: bits in the 10P/2B PMA/PMD speed ability register and the
1420: CO supported and CPE supported bits in the 10P/2B PMA/PMD
1421: status register"
1422: REFERENCE
1423: "[802.3ah] 61.1, 45.2.1.4.1, 45.2.1.4.2, 45.2.1.12.2,
1424: 45.2.1.12.3"
1425: ::= { efmCuPmeCapabilityEntry 1 }
1426:
1427:
1428: efmCuPmeStatusTable OBJECT-TYPE
1429: SYNTAX SEQUENCE OF EfmCuPmeStatusEntry
1430: MAX-ACCESS not-accessible
1431: STATUS current
1432: DESCRIPTION
1433: "This table provides common status information of EFMCu
1434: 2BASE-TL/10PASS-TS PME ports. Status information specific
1435: to 10PASS-TS PME is represented in efmCuPme10PStatusTable.
1436:
1437: This table contains live data from the equipment. As such,
1438: it is NOT persistent."
1439: ::= { efmCuPme 3 }
1440:
1441: efmCuPmeStatusEntry OBJECT-TYPE
1442: SYNTAX EfmCuPmeStatusEntry
1443: MAX-ACCESS not-accessible
1444: STATUS current
1445: DESCRIPTION
1446: "An entry in the EFMCu PME Status table.
1447: Each entry represents common aspects of an EFMCu PME port
1448: indexed by the ifIndex. Note that an EFMCu PME port can be
1449: stacked below a single PCS port, also indexed by ifIndex,
1450: possibly together with other PME ports if PAF is enabled."
1451: INDEX { ifIndex }
1452: ::= { efmCuPmeStatusTable 1 }
1453:
1454: EfmCuPmeStatusEntry ::=
1455: SEQUENCE {
1456: efmCuPmeOperStatus INTEGER,
1457: efmCuPmeFltStatus BITS,
1458: efmCuPmeOperSubType INTEGER,
1459: efmCuPmeOperProfile EfmProfileIndexOrZero,
1460: efmCuPmeSnrMgn Integer32,
1461: efmCuPmePeerSnrMgn Integer32,
1462: efmCuPmeLineAtn Integer32,
1463: efmCuPmePeerLineAtn Integer32,
1464: efmCuPmeEquivalentLength Unsigned32,
1465: efmCuPmeTCCodingErrors Counter32,
1466: efmCuPmeTCCrcErrors Counter32
1467: }
1468:
1469: efmCuPmeOperStatus OBJECT-TYPE
1470: SYNTAX INTEGER {
1471: up(1),
1472: downNotReady(2),
1473: downReady(3),
1474: init(4)
1475: }
1476: MAX-ACCESS read-only
1477: STATUS current
1478: DESCRIPTION
1479: "Current PME link Operational Status. Possible values are:
1480: up(1) - The link is Up and ready to pass 64/65B
1481: encoded frames or fragments.
1482: downNotReady(2) - The link is Down and the PME does not
1483: detect Handshake tones from its peer. This
1484: value may indicate a possible problem with
1485: the peer PME.
1486: downReady(3) - The link is Down and the PME detects
1487: Handshake tones from its peer.
1488: init(4) - The link is initializing, as a result of
1489: ifAdminStatus being set to 'up' for a
1490: particular PME or a PCS the PME is
1491: connected to.
1492:
1493: This object is intended to supplement the Down(2) state of
1494: ifOperStatus.
1495:
1496: This object partially maps to the Clause 30 attribute
1497: aPMEStatus.
1498:
1499: If a Clause 45 MDIO Interface to the PME is present, then this
1500: object partially maps to PMA/PMD link status bits in 10P/2B
1501: PMA/PMD status register."
1502: REFERENCE
1503: "[802.3ah] 30.11.2.1.3, 45.2.1.12.4"
1504: ::= { efmCuPmeStatusEntry 1 }
1505:
1506: efmCuPmeFltStatus OBJECT-TYPE
1507: SYNTAX BITS {
1508: lossOfFraming(0),
1509: snrMgnDefect(1),
1510: lineAtnDefect(2),
1511: deviceFault(3),
1512: configInitFailure(4),
1513: protocolInitFailure(5)
1514: }
1515: MAX-ACCESS read-only
1516: STATUS current
1517: DESCRIPTION
1518: "Current/Last PME link Fault Status. This is a bitmap of
1519: possible conditions. The various bit positions are:
1520:
1521: lossOfFraming - Loss of Framing for 10P or
1522: Loss of Sync word for 2B PMD or
1523: Loss of 64/65B Framing
1524: snrMgnDefect - SNR Margin dropped below the Threshold
1525: lineAtnDefect - Line Attenuation exceeds the Threshold
1526: deviceFault - Indicates a vendor-dependent
1527: diagnostic or self-test fault
1528: has been detected.
1529: configInitFailure - Configuration initialization failure,
1530: due to inability of the PME link to
1531: support the configuration profile,
1532: requested during initialization.
1533: protocolInitFailure - Protocol initialization failure, due
1534: to an incompatible protocol used by
1535: the Peer PME during init (that could
1536: happen if a peer PMD is a regular
1537: G.SDHSL/VDSL modem instead of a
1538: 2BASE-TL/10PASS-TS PME).
1539:
1540: This object is intended to supplement ifOperStatus in IF-MIB.
1541:
1542: This object holds information about the last fault.
1543: efmCuPmeFltStatus is cleared by the device restart.
1544: In addition, lossOfFraming, configInitFailure, and
1545: protocolInitFailure are cleared by PME init;
1546: deviceFault is cleared by successful diagnostics/test;
1547: snrMgnDefect and lineAtnDefect are cleared by SNR Margin
1548: and line Attenuation respectively returning to norm and by
1549: PME init.
1550:
1551: This object partially maps to the Clause 30 attribute
1552: aPMEStatus.
1553:
1554: If a Clause 45 MDIO Interface to the PME is present, then this
1555: object consolidates information from various PMA/PMD
1556: registers, namely: Fault bit in PMA/PMD status 1 register,
1557: 10P/2B PMA/PMD link loss register,
1558: 10P outgoing indicator bits status register,
1559: 10P incoming indicator bits status register,
1560: 2B state defects register."
1561: REFERENCE
1562: "[802.3ah] 30.11.2.1.3, 45.2.1.2.1, 45.2.1.38,
1563: 45.2.1.39, 45.2.1.54"
1564: ::= { efmCuPmeStatusEntry 2 }
1565:
1566: efmCuPmeOperSubType OBJECT-TYPE
1567: SYNTAX INTEGER {
1568: ieee2BaseTLO(1),
1569: ieee2BaseTLR(2),
1570: ieee10PassTSO(3),
1571: ieee10PassTSR(4)
1572: }
1573: MAX-ACCESS read-only
1574: STATUS current
1575: DESCRIPTION
1576: "Current operational sub-type of the PME.
1577: Possible values are:
1578: ieee2BaseTLO - PME operates as 2BaseTL-O
1579: ieee2BaseTLR - PME operates as 2BaseTL-R
1580: ieee10PassTSO - PME operates as 10PassTS-O
1581: ieee10PassTSR - PME operates as 10PassTS-R
1582:
1583: The desired operational sub type of the PME can be configured
1584: via the efmCuPmeAdminSubType variable.
1585:
1586: If a Clause 45 MDIO Interface to the PMA/PMD is present, then
1587: this object combines values of the Port sub-type select
1588: bits, the PMA/PMD type selection bits in the 10P/2B
1589: PMA/PMD control register and the PMA/PMD link status bits in
1590: the 10P/2B PMA/PMD status register."
1591: REFERENCE
1592: "[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7, 45.2.1.12.4"
1593: ::= { efmCuPmeStatusEntry 3 }
1594:
1595: efmCuPmeOperProfile OBJECT-TYPE
1596: SYNTAX EfmProfileIndexOrZero
1597: MAX-ACCESS read-only
1598: STATUS current
1599: DESCRIPTION
1600: "PME current operating profile. This object is a pointer to
1601: an entry in either the efmCuPme2BProfileTable or the
1602: efmCuPme10PProfileTable, depending on the current operating
1603: SubType of the PME as indicated by efmCuPmeOperSubType.
1604: Note that a profile entry to which efmCuPmeOperProfile is
1605: pointing to can be created automatically to reflect achieved
1606: parameters in adaptive (not fixed) initialization,
1607: i.e. values of efmCuPmeOperProfile and efmCuAdminProfile or
1608: efmCuPmeAdminProfile may differ.
1609: The value of zero indicates that the PME is down or
1610: initializing.
1611:
1612: This object partially maps to the aOperatingProfile attribute
1613: in Clause 30."
1614: REFERENCE
1615: "[802.3ah] 30.11.2.1.7"
1616: ::= { efmCuPmeStatusEntry 4 }
1617:
1618: efmCuPmeSnrMgn OBJECT-TYPE
1619: SYNTAX Integer32(-127..128|65535)
1620: UNITS "dB"
1621: MAX-ACCESS read-only
1622: STATUS current
1623: DESCRIPTION
1624: "The current Signal-to-Noise Ratio (SNR) margin with respect
1625: to the received signal as perceived by the local PME.
1626: The value of 65535 is returned when the PME is down or
1627: initializing.
1628:
1629: This object maps to the aPMESNRMgn attribute in Clause 30.
1630:
1631: If a Clause 45 MDIO Interface is present, then this
1632: object maps to the 10P/2B RX SNR margin register."
1633: REFERENCE
1634: "[802.3ah] 30.11.2.1.4, 45.2.1.16"
1635: ::= { efmCuPmeStatusEntry 5 }
1636:
1637: efmCuPmePeerSnrMgn OBJECT-TYPE
1638: SYNTAX Integer32(-127..128|65535)
1639: UNITS "dB"
1640: MAX-ACCESS read-only
1641: STATUS current
1642: DESCRIPTION
1643: "The current SNR margin in dB with respect to the received
1644: signal, as perceived by the remote (link partner) PME.
1645: The value of 65535 is returned when the PME is down or
1646: initializing.
1647:
1648: This object is irrelevant for the -R PME subtypes. The value
1649: of 65535 SHALL be returned in this case.
1650: If a Clause 45 MDIO Interface is present, then this
1651: object maps to the 10P/2B link partner RX SNR margin
1652: register."
1653: REFERENCE
1654: "[802.3ah] 45.2.1.17"
1655: ::= { efmCuPmeStatusEntry 6}
1656:
1657: efmCuPmeLineAtn OBJECT-TYPE
1658: SYNTAX Integer32(-127..128|65535)
1659: UNITS "dB"
1660: MAX-ACCESS read-only
1661: STATUS current
1662: DESCRIPTION
1663: "The current Line Attenuation in dB as perceived by the local
1664: PME.
1665: The value of 65535 is returned when the PME is down or
1666: initializing.
1667:
1668: If a Clause 45 MDIO Interface is present, then this
1669: object maps to the Line Attenuation register"
1670: REFERENCE
1671: "[802.3ah] 45.2.1.18"
1672: ::= { efmCuPmeStatusEntry 7 }
1673:
1674: efmCuPmePeerLineAtn OBJECT-TYPE
1675: SYNTAX Integer32(-127..128|65535)
1676: UNITS "dB"
1677: MAX-ACCESS read-only
1678: STATUS current
1679: DESCRIPTION
1680: "The current Line Attenuation in dB as perceived by the remote
1681: (link partner) PME.
1682: The value of 65535 is returned when the PME is down or
1683: initializing.
1684:
1685: This object is irrelevant for the -R PME subtypes. The value
1686: of 65535 SHALL be returned in this case.
1687:
1688: If a Clause 45 MDIO Interface is present, then this
1689: object maps to the 20P/2B link partner Line Attenuation
1690: register."
1691: REFERENCE
1692: "[802.3ah] 45.2.1.19"
1693: ::= { efmCuPmeStatusEntry 8 }
1694:
1695: efmCuPmeEquivalentLength OBJECT-TYPE
1696: SYNTAX Unsigned32(0..8192|65535)
1697: UNITS "m"
1698: MAX-ACCESS read-only
1699: STATUS current
1700: DESCRIPTION
1701: "An estimate of the equivalent loop's physical length in
1702: meters, as perceived by the PME after the link is established.
1703: An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a
1704: perfect square root attenuation characteristic, without any
1705: bridged taps.
1706: The value of 65535 is returned if the link is Down or
1707: Initializing or the PME is unable to estimate the equivalent
1708: length.
1709:
1710: For a 10BASE-TL PME, if a Clause 45 MDIO Interface to the PME
1711: is present, then this object maps to the 10P Electrical Length
1712: register"
1713: REFERENCE
1714: "[802.3ah] 45.2.1.21"
1715: ::= { efmCuPmeStatusEntry 9 }
1716:
1717: efmCuPmeTCCodingErrors OBJECT-TYPE
1718: SYNTAX Counter32
1719: MAX-ACCESS read-only
1720: STATUS current
1721: DESCRIPTION
1722: "The number of 64/65-octet encapsulation errors. This counter
1723: is incremented for each 64/65-octet encapsulation error
1724: detected by the 64/65-octet receive function.
1725:
1726: This object maps to aTCCodingViolations attribute in
1727: Clause 30.
1728:
1729: If a Clause 45 MDIO Interface to the PME TC is present, then
1730: this object maps to the TC coding violations register
1731: (see 45.2.6.12).
1732:
1733: Discontinuities in the value of this counter can occur at
1734: re-initialization of the management system, and at other times
1735: as indicated by the value of ifCounterDiscontinuityTime,
1736: defined in IF-MIB."
1737: REFERENCE
1738: "[802.3ah] 61.3.3.1, 30.11.2.1.5, 45.2.6.12"
1739: ::= { efmCuPmeStatusEntry 10 }
1740:
1741: efmCuPmeTCCrcErrors OBJECT-TYPE
1742: SYNTAX Counter32
1743: MAX-ACCESS read-only
1744: STATUS current
1745: DESCRIPTION
1746: "The number of TC-CRC errors. This counter is incremented for
1747: each TC-CRC error detected by the 64/65-octet receive function
1748: (see 61.3.3.3 and Figure 61-19).
1749:
1750: This object maps to aTCCRCErrors attribute in
1751: Clause 30.
1752:
1753: If a Clause 45 MDIO Interface to the PME TC is present, then
1754: this object maps to the TC CRC error register
1755: (see 45.2.6.11).
1756:
1757: Discontinuities in the value of this counter can occur at
1758: re-initialization of the management system, and at other times
1759: as indicated by the value of ifCounterDiscontinuityTime,
1760: defined in IF-MIB."
1761: REFERENCE
1762: "[802.3ah] 61.3.3.3, 30.11.2.1.10, 45.2.6.11"
1763: ::= { efmCuPmeStatusEntry 11 }
1764:
1765: -- 2BASE-TL specific PME group
1766:
1767: efmCuPme2B OBJECT IDENTIFIER ::= { efmCuPme 5 }
1768:
1769: efmCuPme2BProfileTable OBJECT-TYPE
1770: SYNTAX SEQUENCE OF EfmCuPme2BProfileEntry
1771: MAX-ACCESS not-accessible
1772: STATUS current
1773: DESCRIPTION
1774: "This table supports definitions of administrative and
1775: operating profiles for 2BASE-TL PMEs.
1776: The first 14 entries in this table SHALL always be defined as
1777: follows (see 802.3ah Annex 63A):
1778: -------+-------+-------+-----+------+-------------+-----------
1779: Profile MinRate MaxRate Power Region Constellation Comment
1780: index (Kbps) (Kbps) (dBm)
1781: -------+-------+-------+-----+------+-------------+-----------
1782: 1 5696 5696 13.5 1 32-TCPAM default
1783: 2 3072 3072 13.5 1 32-TCPAM
1784: 3 2048 2048 13.5 1 16-TCPAM
1785: 4 1024 1024 13.5 1 16-TCPAM
1786: 5 704 704 13.5 1 16-TCPAM
1787: 6 512 512 13.5 1 16-TCPAM
1788: 7 5696 5696 14.5 2 32-TCPAM
1789: 8 3072 3072 14.5 2 32-TCPAM
1790: 9 2048 2048 14.5 2 16-TCPAM
1791: 10 1024 1024 13.5 2 16-TCPAM
1792: 11 704 704 13.5 2 16-TCPAM
1793: 12 512 512 13.5 2 16-TCPAM
1794: 13 192 5696 0 1 0 best effort
1795: 14 192 5696 0 2 0 best effort
1796: -------+-------+-------+-----+------+-------------+-----------
1797:
1798: These default entries SHALL be created during agent
1799: initialization and MUST NOT be deleted.
1800:
1801: Entries following the first 14 can be dynamically created and
1802: deleted to provide custom administrative (configuration)
1803: profiles and automatic operating profiles.
1804:
1805: This table MUST be maintained in a persistent manner."
1806: REFERENCE
1807: "[802.3ah] Annex 63A, 30.11.2.1.6"
1808: ::= { efmCuPme2B 2 }
1809:
1810: efmCuPme2BProfileEntry OBJECT-TYPE
1811: SYNTAX EfmCuPme2BProfileEntry
1812: MAX-ACCESS not-accessible
1813: STATUS current
1814: DESCRIPTION
1815: "Each entry corresponds to a single 2BASE-TL PME profile.
1816: Each profile contains a set of parameters, used either for
1817: configuration or representation of a 2BASE-TL PME.
1818: In case a particular profile is referenced via the
1819: efmCuPmeAdminProfile object (or efmCuAdminProfile if
1820: efmCuPmeAdminProfile is zero), it represents the desired
1821: parameters for the 2BaseTL-O PME initialization.
1822: If a profile is referenced via an efmCuPmeOperProfile object,
1823: it represents the current operating parameters of an
1824: operational PME.
1825:
1826: Profiles may be created/deleted using the row creation/
1827: deletion mechanism via efmCuPme2BProfileRowStatus. If an
1828: active entry is referenced, the entry MUST remain 'active'
1829: until all references are removed.
1830: Default entries MUST NOT be removed."
1831: INDEX { efmCuPme2BProfileIndex }
1832: ::= { efmCuPme2BProfileTable 1 }
1833:
1834: EfmCuPme2BProfileEntry ::=
1835: SEQUENCE {
1836: efmCuPme2BProfileIndex EfmProfileIndex,
1837: efmCuPme2BProfileDescr SnmpAdminString,
1838: efmCuPme2BRegion INTEGER,
1839: efmCuPme2BsMode EfmProfileIndexOrZero,
1840: efmCuPme2BMinDataRate Unsigned32,
1841: efmCuPme2BMaxDataRate Unsigned32,
1842: efmCuPme2BPower Unsigned32,
1843: efmCuPme2BConstellation INTEGER,
1844: efmCuPme2BProfileRowStatus RowStatus
1845: }
1846:
1847: efmCuPme2BProfileIndex OBJECT-TYPE
1848: SYNTAX EfmProfileIndex
1849: MAX-ACCESS not-accessible
1850: STATUS current
1851: DESCRIPTION
1852: "2BASE-TL PME profile index.
1853: This object is the unique index associated with this profile.
1854: Entries in this table are referenced via efmCuAdminProfile or
1855: efmCuPmeAdminProfile objects."
1856: ::= { efmCuPme2BProfileEntry 1 }
1857:
1858: efmCuPme2BProfileDescr OBJECT-TYPE
1859: SYNTAX SnmpAdminString
1860: MAX-ACCESS read-create
1861: STATUS current
1862: DESCRIPTION
1863: "A textual string containing information about a 2BASE-TL PME
1864: profile. The string may include information about the data
1865: rate and spectral limitations of this particular profile."
1866: ::= { efmCuPme2BProfileEntry 2 }
1867:
1868: efmCuPme2BRegion OBJECT-TYPE
1869: SYNTAX INTEGER {
1870: region1(1),
1871: region2(2)
1872: }
1873: MAX-ACCESS read-create
1874: STATUS current
1875: DESCRIPTION
1876: "Regional settings for a 2BASE-TL PME, as specified in the
1877: relevant Regional Annex of [G.991.2].
1878: Regional settings specify the Power Spectral Density (PSD)
1879: mask, Power Back-Off (PBO) values and place limitations on the
1880: max allowed data rate, power and constellation.
1881:
1882: Possible values for this object are:
1883: region1 - Annexes A and F (e.g. North America)
1884: region2 - Annexes B and G (e.g. Europe)
1885:
1886: Annex A/B specify regional settings for data rates 192-2304
1887: Kbps using 16-TCPAM encoding.
1888: Annex F/G specify regional settings for rates 2320-3840 Kbps
1889: using 16-TCPAM encoding and 768-5696 Kbps using 32-TCPAM
1890: encoding.
1891:
1892: If a Clause 45 MDIO Interface to the PME is present, then this
1893: object partially maps to the Region bits in the 2B general
1894: parameter register."
1895: REFERENCE
1896: "[802.3ah] 45.2.1.42; [G.991.2] Annexes A, B, F and G"
1897: ::= { efmCuPme2BProfileEntry 3 }
1898:
1899: efmCuPme2BsMode OBJECT-TYPE
1900: SYNTAX EfmProfileIndexOrZero
1901: MAX-ACCESS read-create
1902: STATUS current
1903: DESCRIPTION
1904: "Desired custom Spectral Mode for a 2BASE-TL PME. This object
1905: is a pointer to an entry in efmCuPme2BsModeTable and a block
1906: of entries in efmCuPme2BRateReachTable, which together define
1907: (country-specific) reach dependent rate limitations in
1908: addition to those defined by efmCuPme2BRegion.
1909:
1910: The value of this object is the index of the referenced
1911: spectral mode.
1912: The value of zero (default) indicates that no specific
1913: spectral mode is applicable.
1914:
1915: Attempts to set this object to a value that is not the value
1916: of the index for an active entry in the corresponding spectral
1917: mode table MUST be rejected."
1918: REFERENCE
1919: "efmCuPme2BsModeTable, efmCuPme2BRateReachTable"
1920: DEFVAL { 0 }
1921: ::= { efmCuPme2BProfileEntry 4 }
1922:
1923: efmCuPme2BMinDataRate OBJECT-TYPE
1924: SYNTAX Unsigned32(192..5696)
1925: UNITS "Kbps"
1926: MAX-ACCESS read-create
1927: STATUS current
1928: DESCRIPTION
1929: "Minimum Data Rate for the 2BASE-TL PME.
1930: This object can take values of (n x 64)Kbps,
1931: where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM encoding.
1932:
1933: The data rate of the 2BASE-TL PME is considered 'fixed' when
1934: the value of this object equals that of efmCuPme2BMaxDataRate.
1935: If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in
1936: the administrative profile, the data rate is considered
1937: 'adaptive', and SHALL be set to the maximum attainable rate
1938: not exceeding efmCuPme2BMaxDataRate, under the spectral
1939: limitations placed by the efmCuPme2BRegion and
1940: efmCuPme2BsMode.
1941:
1942: Note that the current operational data rate of the PME is
1943: represented by the ifSpeed object of IF-MIB.
1944:
1945: If a Clause 45 MDIO Interface to the PME is present, then this
1946: object maps to the Min Data Rate1 bits in the 2B PMD
1947: parameters register.
1948:
1949: This object MUST be maintained in a persistent manner."
1950: REFERENCE
1951: "[802.3ah] 45.2.1.43"
1952: ::= { efmCuPme2BProfileEntry 5 }
1953:
1954: efmCuPme2BMaxDataRate OBJECT-TYPE
1955: SYNTAX Unsigned32(192..5696)
1956: UNITS "Kbps"
1957: MAX-ACCESS read-create
1958: STATUS current
1959: DESCRIPTION
1960: "Maximum Data Rate for the 2BASE-TL PME.
1961: This object can take values of (n x 64)Kbps,
1962: where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM encoding.
1963:
1964: The data rate of the 2BASE-TL PME is considered 'fixed' when
1965: the value of this object equals that of efmCuPme2BMinDataRate.
1966: If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in
1967: the administrative profile, the data rate is considered
1968: 'adaptive', and SHALL be set to the maximum attainable rate
1969: not exceeding efmCuPme2BMaxDataRate, under the spectral
1970: limitations placed by the efmCuPme2BRegion and
1971: efmCuPme2BsMode.
1972:
1973: Note that the current operational data rate of the PME is
1974: represented by the ifSpeed object of IF-MIB.
1975:
1976: If a Clause 45 MDIO Interface to the PME is present, then this
1977: object maps to the Max Data Rate1 bits in the 2B PMD
1978: parameters register.
1979:
1980: This object MUST be maintained in a persistent manner."
1981: REFERENCE
1982: "[802.3ah] 45.2.1.43"
1983: ::= { efmCuPme2BProfileEntry 6 }
1984:
1985: efmCuPme2BPower OBJECT-TYPE
1986: SYNTAX Unsigned32(0|10..42)
1987: UNITS "0.5 dBm"
1988: MAX-ACCESS read-create
1989: STATUS current
1990: DESCRIPTION
1991: "Signal Transmit Power. Multiple of 0.5dBm.
1992: The value of 0 in the administrative profile means that the
1993: signal transmit power is not fixed and SHALL be set to
1994: maximize the attainable rate, under the spectral limitations
1995: placed by the efmCuPme2BRegion and efmCuPme2BsMode.
1996:
1997: If a Clause 45 MDIO Interface to the PME is present, then this
1998: object maps to the Power1 bits in the 2B PMD parameters
1999: register"
2000: REFERENCE
2001: "[802.3ah] 45.2.1.43"
2002: ::= { efmCuPme2BProfileEntry 7 }
2003:
2004: efmCuPme2BConstellation OBJECT-TYPE
2005: SYNTAX INTEGER {
2006: adaptive(0),
2007: tcpam16(1),
2008: tcpam32(2)
2009: }
2010: MAX-ACCESS read-create
2011: STATUS current
2012: DESCRIPTION
2013: "TCPAM Constellation of the 2BASE-TL PME.
2014: The possible values are:
2015: adaptive(0) - either 16- or 32-TCPAM
2016: tcpam16(1) - 16-TCPAM
2017: tcpam32(2) - 32-TCPAM
2018:
2019: The value of adaptive(0) in the administrative profile means
2020: that the constellation is not fixed and SHALL be set to
2021: maximize the attainable rate, under the spectral limitations
2022: placed by the efmCuPme2BRegion and efmCuPme2BsMode.
2023:
2024: If a Clause 45 MDIO Interface to the PME is present, then this
2025: object maps to the Constellation1 bits in the 2B general
2026: parameter register."
2027: REFERENCE
2028: "[802.3ah] 45.2.1.43"
2029: ::= { efmCuPme2BProfileEntry 8 }
2030:
2031: efmCuPme2BProfileRowStatus OBJECT-TYPE
2032: SYNTAX RowStatus
2033: MAX-ACCESS read-create
2034: STATUS current
2035: DESCRIPTION
2036: "This object controls the creation, modification or deletion
2037: of the associated entry in the efmCuPme2BProfileTable per the
2038: semantics of RowStatus.
2039:
2040: If an 'active' entry is referenced via efmCuAdminProfile or
2041: efmCuPmeAdminProfile instance(s), the entry MUST remain
2042: 'active'.
2043:
2044: An 'active' entry SHALL NOT be modified. In order to modify an
2045: existing entry it MUST be taken out of service (by setting
2046: this object to 'notInService'), modified and set 'active'
2047: again."
2048: ::= { efmCuPme2BProfileEntry 9 }
2049:
2050:
2051: efmCuPme2BsModeTable OBJECT-TYPE
2052: SYNTAX SEQUENCE OF EfmCuPme2BsModeEntry
2053: MAX-ACCESS not-accessible
2054: STATUS current
2055: DESCRIPTION
2056: "This table, together with efmCu2BReachRateTable, supports
2057: definition of administrative custom spectral modes for
2058: 2BASE-TL PMEs, describing spectral limitations in addition to
2059: those specified by efmCuPme2BRegion.
2060:
2061: In some countries, spectral regulations (e.g. UK ANFP) limit
2062: the length of the loops for certain data rates. This table
2063: allows these country-specific limitations to be specified.
2064:
2065: Entries in this table referenced by the efmCuPme2BsMode
2066: MUST NOT be deleted until all the active references are
2067: removed.
2068:
2069: This table MUST be maintained in a persistent manner."
2070: REFERENCE
2071: "efmCu2BReachRateTable"
2072: ::= { efmCuPme2B 3 }
2073:
2074: efmCuPme2BsModeEntry OBJECT-TYPE
2075: SYNTAX EfmCuPme2BsModeEntry
2076: MAX-ACCESS not-accessible
2077: STATUS current
2078: DESCRIPTION
2079: "Each entry specifies a spectral mode description and its
2080: index, which is used to reference corresponding entries in the
2081: efmCu2BReachRateTable.
2082: Entries may be created/deleted using the row creation/
2083: deletion mechanism via efmCuPme2BsModeRowStatus."
2084: INDEX { efmCuPme2BsModeIndex }
2085: ::= { efmCuPme2BsModeTable 1 }
2086:
2087: EfmCuPme2BsModeEntry ::=
2088: SEQUENCE {
2089: efmCuPme2BsModeIndex EfmProfileIndex,
2090: efmCuPme2BsModeDescr SnmpAdminString,
2091: efmCuPme2BsModeRowStatus RowStatus
2092: }
2093:
2094: efmCuPme2BsModeIndex OBJECT-TYPE
2095: SYNTAX EfmProfileIndex
2096: MAX-ACCESS not-accessible
2097: STATUS current
2098: DESCRIPTION
2099: "2BASE-TL PME Spectral Mode index.
2100: This object is the unique index associated with this spectral
2101: mode.
2102: Entries in this table are referenced via the efmCuPme2BsMode
2103: object."
2104: ::= { efmCuPme2BsModeEntry 1 }
2105:
2106: efmCuPme2BsModeDescr OBJECT-TYPE
2107: SYNTAX SnmpAdminString
2108: MAX-ACCESS read-create
2109: STATUS current
2110: DESCRIPTION
2111: "A textual string containing information about a 2BASE-TL PME
2112: spectral mode. The string may include information about
2113: corresponding (country-specific) spectral regulations
2114: and rate/reach limitations of this particular spectral mode."
2115: ::= { efmCuPme2BsModeEntry 2 }
2116:
2117: efmCuPme2BsModeRowStatus OBJECT-TYPE
2118: SYNTAX RowStatus
2119: MAX-ACCESS read-create
2120: STATUS current
2121: DESCRIPTION
2122: "This object controls creation, modification or deletion of
2123: the associated entry in efmCuPme2BsModeTable per the semantics
2124: of RowStatus.
2125:
2126: If an 'active' entry is referenced via efmCuPme2BsMode
2127: instance(s), the entry MUST remain 'active'.
2128:
2129: An 'active' entry SHALL NOT be modified. In order to modify an
2130: existing entry it MUST be taken out of service (by setting
2131: this object to 'notInService'), modified and set 'active'
2132: again."
2133: ::= { efmCuPme2BsModeEntry 3 }
2134:
2135:
2136: efmCuPme2BReachRateTable OBJECT-TYPE
2137: SYNTAX SEQUENCE OF EfmCuPme2BReachRateEntry
2138: MAX-ACCESS not-accessible
2139: STATUS current
2140: DESCRIPTION
2141: "This table supports the definition of administrative custom
2142: spectral modes for 2BASE-TL PMEs, providing spectral
2143: limitations in addition to those specified by
2144: efmCuPme2BRegion.
2145:
2146: The spectral regulations in some countries (e.g. UK ANFP)
2147: limit the length of the loops for certain data rates.
2148: This table allows these country-specific limitations to be
2149: specified.
2150:
2151: Below is an example of this table for [ANFP]:
2152: ----------+-------+-------
2153: Equivalent MaxRate MaxRate
2154: Length PAM16 PAM32
2155: (m) (Kbps) (Kbps)
2156: ----------+-------+-------
2157: 975 2304 5696
2158: 1125 2304 5504
2159: 1275 2304 5120
2160: 1350 2304 4864
2161: 1425 2304 4544
2162: 1500 2304 4288
2163: 1575 2304 3968
2164: 1650 2304 3776
2165: 1725 2304 3520
2166: 1800 2304 3264
2167: 1875 2304 3072
2168: 1950 2048 2688
2169: 2100 1792 2368
2170: 2250 1536 0
2171: 2400 1408 0
2172: 2550 1280 0
2173: 2775 1152 0
2174: 2925 1152 0
2175: 3150 1088 0
2176: 3375 1024 0
2177: ----------+-------+-------
2178: Entries in this table referenced by an efmCuPme2BsMode
2179: instance MUST NOT be deleted.
2180:
2181: This table MUST be maintained in a persistent manner."
2182: REFERENCE
2183: "[ANFP]"
2184: ::= { efmCuPme2B 4 }
2185:
2186: efmCuPme2BReachRateEntry OBJECT-TYPE
2187: SYNTAX EfmCuPme2BReachRateEntry
2188: MAX-ACCESS not-accessible
2189: STATUS current
2190: DESCRIPTION
2191: "Each entry specifies maximum 2BASE-TL PME data rates
2192: allowed for a certain equivalent loop length, when using
2193: 16-TCPAM or 32-TCPAM encoding.
2194:
2195: When a 2BASE-TL PME is initialized, its data rate MUST NOT
2196: exceed one of the following limitations:
2197: - the value of efmCuPme2BMaxDataRate
2198: - maximum data rate allowed by efmCuPme2BRegion and
2199: efmCuPme2BPower
2200: - maximum data rate for a given encoding specified in the
2201: efmCuPme2BsModeEntry, corresponding to the equivalent loop
2202: length, estimated by the PME.
2203:
2204: It is RECOMMENDED that the efmCuPme2BEquivalentLength values
2205: are assigned in increasing order, starting from the minimum
2206: value.
2207:
2208: Entries may be created/deleted using the row creation/
2209: deletion mechanism via efmCuPme2ReachRateRowStatus."
2210: INDEX { efmCuPme2BsModeIndex, efmCuPme2BReachRateIndex }
2211: ::= { efmCuPme2BReachRateTable 1 }
2212:
2213: EfmCuPme2BReachRateEntry ::=
2214: SEQUENCE {
2215: efmCuPme2BReachRateIndex EfmProfileIndex,
2216: efmCuPme2BEquivalentLength Unsigned32,
2217: efmCuPme2BMaxDataRatePam16 Unsigned32,
2218: efmCuPme2BMaxDataRatePam32 Unsigned32,
2219: efmCuPme2BReachRateRowStatus RowStatus
2220: }
2221:
2222: efmCuPme2BReachRateIndex OBJECT-TYPE
2223: SYNTAX EfmProfileIndex
2224: MAX-ACCESS not-accessible
2225: STATUS current
2226: DESCRIPTION
2227: "2BASE-TL custom spectral mode Reach-Rate table index.
2228: This object is the unique index associated with each enry."
2229: ::= { efmCuPme2BReachRateEntry 1 }
2230:
2231: efmCuPme2BEquivalentLength OBJECT-TYPE
2232: SYNTAX Unsigned32(0..8192)
2233: UNITS "m"
2234: MAX-ACCESS read-create
2235: STATUS current
2236: DESCRIPTION
2237: "Maximum allowed equivalent loop's physical length in meters
2238: for the specified data rates.
2239: An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a
2240: perfect square root attenuation characteristic, without any
2241: bridged taps."
2242: ::= { efmCuPme2BReachRateEntry 2 }
2243:
2244: efmCuPme2BMaxDataRatePam16 OBJECT-TYPE
2245: SYNTAX Unsigned32(0|192..5696)
2246: UNITS "Kbps"
2247: MAX-ACCESS read-create
2248: STATUS current
2249: DESCRIPTION
2250: "Maximum data rate for a 2BASE-TL PME at the specified
2251: equivalent loop's length using TC-PAM16 encoding.
2252: The value of zero means that TC-PAM16 encoding should not be
2253: used at this distance."
2254: ::= { efmCuPme2BReachRateEntry 3 }
2255:
2256: efmCuPme2BMaxDataRatePam32 OBJECT-TYPE
2257: SYNTAX Unsigned32(0|192..5696)
2258: UNITS "Kbps"
2259: MAX-ACCESS read-create
2260: STATUS current
2261: DESCRIPTION
2262: "Maximum data rate for a 2BASE-TL PME at the specified
2263: equivalent loop's length using TC-PAM32 encoding.
2264: The value of zero means that TC-PAM32 encoding should not be
2265: used at this distance."
2266: ::= { efmCuPme2BReachRateEntry 4 }
2267:
2268: efmCuPme2BReachRateRowStatus OBJECT-TYPE
2269: SYNTAX RowStatus
2270: MAX-ACCESS read-create
2271: STATUS current
2272: DESCRIPTION
2273: "This object controls the creation, modification or deletion
2274: of the associated entry in the efmCuPme2BReachRateTable per
2275: the semantics of RowStatus.
2276:
2277: If an 'active' entry is referenced via efmCuPme2BsMode
2278: instance(s), the entry MUST remain 'active'.
2279:
2280: An 'active' entry SHALL NOT be modified. In order to modify an
2281: existing entry it MUST be taken out of service (by setting
2282: this object to 'notInService'), modified and set 'active'
2283: again."
2284: ::= { efmCuPme2BReachRateEntry 5 }
2285:
2286:
2287: -- 10PASS-TS specific PME group
2288:
2289: efmCuPme10P OBJECT IDENTIFIER ::= { efmCuPme 6 }
2290:
2291: efmCuPme10PProfileTable OBJECT-TYPE
2292: SYNTAX SEQUENCE OF EfmCuPme10PProfileEntry
2293: MAX-ACCESS not-accessible
2294: STATUS current
2295: DESCRIPTION
2296: "This table supports definitions of configuration profiles for
2297: 10PASS-TS PMEs.
2298: The first 22 entries in this table SHALL always be defined as
2299: follows (see 802.3ah Annex 62B.3, table 62B-1):
2300: -------+--------+----+---------+-----+-----+---------------
2301: Profile Bandplan UPBO BandNotch DRate URate Comment
2302: Index PSDMask# p# p# p# p#
2303: -------+--------+----+---------+-----+-----+---------------
2304: 1 1 3 2,6,10,11 20 20 default profile
2305: 2 13 5 0 20 20
2306: 3 1 1 0 20 20
2307: 4 16 0 0 100 100
2308: 5 16 0 0 70 50
2309: 6 6 0 0 50 10
2310: 7 17 0 0 30 30
2311: 8 8 0 0 30 5
2312: 9 4 0 0 25 25
2313: 10 4 0 0 15 15
2314: 11 23 0 0 10 10
2315: 12 23 0 0 5 5
2316: 13 16 0 2,5,9,11 100 100
2317: 14 16 0 2,5,9,11 70 50
2318: 15 6 0 2,6,10,11 50 10
2319: 16 17 0 2,5,9,11 30 30
2320: 17 8 0 2,6,10,11 30 5
2321: 18 4 0 2,6,10,11 25 25
2322: 19 4 0 2,6,10,11 15 15
2323: 20 23 0 2,5,9,11 10 10
2324: 21 23 0 2,5,9,11 5 5
2325: 22 30 0 0 200 50
2326: -------+--------+----+---------+-----+-----+---------------
2327:
2328: These default entries SHALL be created during agent
2329: initialization and MUST NOT be deleted.
2330:
2331: Entries following the first 22 can be dynamically created and
2332: deleted to provide custom administrative (configuration)
2333: profiles and automatic operating profiles.
2334:
2335: This table MUST be maintained in a persistent manner."
2336: REFERENCE
2337: "[802.3ah] Annex 62B.3, 30.11.2.1.6"
2338: ::= { efmCuPme10P 1 }
2339:
2340: efmCuPme10PProfileEntry OBJECT-TYPE
2341: SYNTAX EfmCuPme10PProfileEntry
2342: MAX-ACCESS not-accessible
2343: STATUS current
2344: DESCRIPTION
2345: "Each entry corresponds to a single 10PASS-TS PME profile.
2346:
2347: Each profile contains a set of parameters, used either for
2348: configuration or representation of a 10PASS-TS PME.
2349: In case a particular profile is referenced via the
2350: efmCuPmeAdminProfile object (or efmCuAdminProfile if
2351: efmCuPmeAdminProfile is zero), it represents the desired
2352: parameters for the 10PassTS-O PME initialization.
2353: If a profile is referenced via an efmCuPmeOperProfile object,
2354: it represents the current operating parameters of the PME.
2355:
2356: Profiles may be created/deleted using the row creation/
2357: deletion mechanism via efmCuPme10PProfileRowStatus. If an
2358: 'active' entry is referenced, the entry MUST remain 'active'
2359: until all references are removed.
2360: Default entries MUST NOT be removed."
2361: INDEX { efmCuPme10PProfileIndex }
2362: ::= { efmCuPme10PProfileTable 1 }
2363:
2364: EfmCuPme10PProfileEntry ::=
2365: SEQUENCE {
2366: efmCuPme10PProfileIndex EfmProfileIndex,
2367: efmCuPme10PProfileDescr SnmpAdminString,
2368: efmCuPme10PBandplanPSDMskProfile INTEGER,
2369: efmCuPme10PUPBOReferenceProfile INTEGER,
2370: efmCuPme10PBandNotchProfiles BITS,
2371: efmCuPme10PPayloadDRateProfile INTEGER,
2372: efmCuPme10PPayloadURateProfile INTEGER,
2373: efmCuPme10PProfileRowStatus RowStatus
2374: }
2375:
2376: efmCuPme10PProfileIndex OBJECT-TYPE
2377: SYNTAX EfmProfileIndex
2378: MAX-ACCESS not-accessible
2379: STATUS current
2380: DESCRIPTION
2381: "10PASS-TS PME profile Index.
2382: This object is the unique index associated with this profile.
2383: Entries in this table are referenced via efmCuAdminProfile or
2384: efmCuPmeAdminProfile."
2385: ::= { efmCuPme10PProfileEntry 1 }
2386:
2387: efmCuPme10PProfileDescr OBJECT-TYPE
2388: SYNTAX SnmpAdminString
2389: MAX-ACCESS read-create
2390: STATUS current
2391: DESCRIPTION
2392: "A textual string containing information about a 10PASS-TS PME
2393: profile. The string may include information about data rate
2394: and spectral limitations of this particular profile."
2395: ::= { efmCuPme10PProfileEntry 2 }
2396:
2397: efmCuPme10PBandplanPSDMskProfile OBJECT-TYPE
2398: SYNTAX INTEGER {
2399: profile1(1),
2400: profile2(2),
2401: profile3(3),
2402: profile4(4),
2403: profile5(5),
2404: profile6(6),
2405: profile7(7),
2406: profile8(8),
2407: profile9(9),
2408: profile10(10),
2409: profile11(11),
2410: profile12(12),
2411: profile13(13),
2412: profile14(14),
2413: profile15(15),
2414: profile16(16),
2415: profile17(17),
2416: profile18(18),
2417: profile19(19),
2418: profile20(20),
2419: profile21(21),
2420: profile22(22),
2421: profile23(23),
2422: profile24(24),
2423: profile25(25),
2424: profile26(26),
2425: profile27(27),
2426: profile28(28),
2427: profile29(29),
2428: profile30(30)
2429: }
2430: MAX-ACCESS read-create
2431: STATUS current
2432: DESCRIPTION
2433: "The 10PASS-TS PME Bandplan and PSD Mask Profile, as specified
2434: in 802.3ah Annex 62A, table 62A-1. Possible values are:
2435: --------------+------------------------+------------+--------
2436: Profile Name PSD Mask Bands G.993.1
2437: 0/1/2/3/4/5 Bandplan
2438: --------------+------------------------+------------+--------
2439: profile1(1) T1.424 FTTCab.M1 x/D/U/D/U A
2440: profile2(2) T1.424 FTTEx.M1 x/D/U/D/U A
2441: profile3(3) T1.424 FTTCab.M2 x/D/U/D/U A
2442: profile4(4) T1.424 FTTEx.M2 x/D/U/D/U A
2443: profile5(5) T1.424 FTTCab.M1 D/D/U/D/U A
2444: profile6(6) T1.424 FTTEx.M1 D/D/U/D/U A
2445: profile7(7) T1.424 FTTCab.M2 D/D/U/D/U A
2446: profile8(8) T1.424 FTTEx.M2 D/D/U/D/U A
2447: profile9(9) T1.424 FTTCab.M1 U/D/U/D/x A
2448: profile10(10) T1.424 FTTEx.M1 U/D/U/D/x A
2449: profile11(11) T1.424 FTTCab.M2 U/D/U/D/x A
2450: profile12(12) T1.424 FTTEx.M2 U/D/U/D/x A
2451: profile13(13) TS 101 270-1 Pcab.M1.A x/D/U/D/U B
2452: profile14(14) TS 101 270-1 Pcab.M1.B x/D/U/D/U B
2453: profile15(15) TS 101 270-1 Pex.P1.M1 x/D/U/D/U B
2454: profile16(16) TS 101 270-1 Pex.P2.M1 x/D/U/D/U B
2455: profile17(17) TS 101 270-1 Pcab.M2 x/D/U/D/U B
2456: profile18(18) TS 101 270-1 Pex.P1.M2 x/D/U/D/U B
2457: profile19(19) TS 101 270-1 Pex.P2.M2 x/D/U/D/U B
2458: profile20(20) TS 101 270-1 Pcab.M1.A U/D/U/D/x B
2459: profile21(21) TS 101 270-1 Pcab.M1.B U/D/U/D/x B
2460: profile22(22) TS 101 270-1 Pex.P1.M1 U/D/U/D/x B
2461: profile23(23) TS 101 270-1 Pex.P2.M1 U/D/U/D/x B
2462: profile24(24) TS 101 270-1 Pcab.M2 U/D/U/D/x B
2463: profile25(25) TS 101 270-1 Pex.P1.M2 U/D/U/D/x B
2464: profile26(26) TS 101 270-1 Pex.P2.M2 U/D/U/D/x B
2465: profile27(27) G.993.1 F.1.2.1 x/D/U/D/U Annex F
2466: profile28(28) G.993.1 F.1.2.2 x/D/U/D/U Annex F
2467: profile29(29) G.993.1 F.1.2.3 x/D/U/D/U Annex F
2468: profile30(30) T1.424 FTTCab.M1 (ext.) x/D/U/D/U/D Annex A
2469: --------------+------------------------+------------+--------
2470: "
2471: REFERENCE
2472: "[802.3ah] Annex 62A"
2473: ::= { efmCuPme10PProfileEntry 3 }
2474:
2475: efmCuPme10PUPBOReferenceProfile OBJECT-TYPE
2476: SYNTAX INTEGER {
2477: profile0(0),
2478: profile1(1),
2479: profile2(2),
2480: profile3(3),
2481: profile4(4),
2482: profile5(5),
2483: profile6(6),
2484: profile7(7),
2485: profile8(8),
2486: profile9(9)
2487: }
2488: MAX-ACCESS read-create
2489: STATUS current
2490: DESCRIPTION
2491: "The 10PASS-TS PME Upstream Power Back-Off (UPBO) Reference
2492: PSD Profile, as specified in 802.3 Annex 62A, table 62A-3.
2493: Possible values are:
2494: ------------+-----------------------------
2495: Profile Name Reference PSD
2496: ------------+-----------------------------
2497: profile0(0) no profile
2498: profile1(1) T1.424 Noise A M1
2499: profile2(2) T1.424 Noise A M2
2500: profile3(3) T1.424 Noise F M1
2501: profile4(4) T1.424 Noise F M2
2502: profile5(5) TS 101 270-1 Noise A&B
2503: profile6(6) TS 101 270-1 Noise C
2504: profile7(7) TS 101 270-1 Noise D
2505: profile8(8) TS 101 270-1 Noise E
2506: profile9(9) TS 101 270-1 Noise F
2507: ------------+-----------------------------
2508: "
2509: REFERENCE
2510: "[802.3ah] Annex 62A.3.5"
2511: ::= { efmCuPme10PProfileEntry 4 }
2512:
2513: efmCuPme10PBandNotchProfiles OBJECT-TYPE
2514: SYNTAX BITS {
2515: profile0(0),
2516: profile1(1),
2517: profile2(2),
2518: profile3(3),
2519: profile4(4),
2520: profile5(5),
2521: profile6(6),
2522: profile7(7),
2523: profile8(8),
2524: profile9(9),
2525: profile10(10),
2526: profile11(11)
2527: }
2528: MAX-ACCESS read-create
2529: STATUS current
2530: DESCRIPTION
2531: "The 10PASS-TS PME Egress Control Band Notch Profile bitmap,
2532: as specified in 802.3 Annex 62A, table 62A-4. Possible values
2533: are:
2534: --------------+--------+------+------------+------+------
2535: Profile Name G.991.3 T1.424 TS 101 270-1 StartF EndF
2536: table table table (MHz) (MHz)
2537: --------------+--------+------+------------+------+------
2538: profile0(0) no profile
2539: profile1(1) F-5 #01 - - 1.810 1.825
2540: profile2(2) 6-2 15-1 17 1.810 2.000
2541: profile3(3) F-5 #02 - - 1.907 1.912
2542: profile4(4) F-5 #03 - - 3.500 3.575
2543: profile5(5) 6-2 - 17 3.500 3.800
2544: profile6(6) - 15-1 - 3.500 4.000
2545: profile7(7) F-5 #04 - - 3.747 3.754
2546: profile8(8) F-5 #05 - - 3.791 3.805
2547: profile9(9) 6-2 - 17 7.000 7.100
2548: profile10(10) F-5 #06 15-1 - 7.000 7.300
2549: profile11(11) 6-2 15-1 1 10.100 10.150
2550: --------------+--------+------+------------+------+------
2551:
2552: Any combination of profiles can be specified by ORing
2553: individual profiles, for example value of 0x2230 selects
2554: profiles 2,6,10 and 11."
2555: REFERENCE
2556: "[802.3ah] Annex 62A.3.5"
2557: ::= { efmCuPme10PProfileEntry 5 }
2558:
2559: efmCuPme10PPayloadDRateProfile OBJECT-TYPE
2560: SYNTAX INTEGER {
2561: profile5(5),
2562: profile10(10),
2563: profile15(15),
2564: profile20(20),
2565: profile25(25),
2566: profile30(30),
2567: profile50(50),
2568: profile70(70),
2569: profile100(100),
2570: profile140(140),
2571: profile200(200)
2572: }
2573: MAX-ACCESS read-create
2574: STATUS current
2575: DESCRIPTION
2576: "The 10PASS-TS PME Downstream Payload Rate Profile, as
2577: specified in 802.3 Annex 62A. Possible values are:
2578: profile5(5) - 2.5 Mbps
2579: profile10(10) - 5 Mbps
2580: profile15(15) - 7.5 Mbps
2581: profile20(20) - 10 Mbps
2582: profile25(25) - 12.5 Mbps
2583: profile30(30) - 15 Mbps
2584: profile50(50) - 25 Mbps
2585: profile70(70) - 35 Mbps
2586: profile100(100) - 50 Mbps
2587: profile140(140) - 70 Mbps
2588: profile200(200) - 100 Mbps
2589:
2590: Each value represents a target for the PME's Downstream
2591: Payload Bitrate as seen at the MII. If the payload rate of
2592: the selected profile cannot be achieved based on the loop
2593: environment, bandplan and PSD mask, the PME initialization
2594: SHALL fail."
2595: REFERENCE
2596: "[802.3ah] Annex 62A.3.6"
2597: ::= { efmCuPme10PProfileEntry 6 }
2598:
2599: efmCuPme10PPayloadURateProfile OBJECT-TYPE
2600: SYNTAX INTEGER {
2601: profile5(5),
2602: profile10(10),
2603: profile15(15),
2604: profile20(20),
2605: profile25(25),
2606: profile30(30),
2607: profile50(50),
2608: profile70(70),
2609: profile100(100)
2610:
2611: }
2612: MAX-ACCESS read-create
2613: STATUS current
2614: DESCRIPTION
2615: "The 10PASS-TS PME Upstream Payload Rate Profile, as specified
2616: in 802.3 Annex 62A. Possible values are:
2617: profile5(5) - 2.5 Mbps
2618: profile10(10) - 5 Mbps
2619: profile15(15) - 7.5 Mbps
2620: profile20(20) - 10 Mbps
2621: profile25(25) - 12.5 Mbps
2622: profile30(30) - 15 Mbps
2623: profile50(50) - 25 Mbps
2624: profile70(70) - 35 Mbps
2625: profile100(100) - 50 Mbps
2626:
2627: Each value represents a target for the PME's Upstream Payload
2628: Bitrate as seen at the MII. If the payload rate of the
2629: selected profile cannot be achieved based on the loop
2630: environment, bandplan and PSD mask, the PME initialization
2631: SHALL fail."
2632: REFERENCE
2633: "[802.3ah] Annex 62A.3.6"
2634: ::= { efmCuPme10PProfileEntry 7 }
2635:
2636: efmCuPme10PProfileRowStatus OBJECT-TYPE
2637: SYNTAX RowStatus
2638: MAX-ACCESS read-create
2639: STATUS current
2640: DESCRIPTION
2641: "This object controls creation, modification or deletion of
2642: the associated entry in efmCuPme10PProfileTable per the
2643: semantics of RowStatus.
2644:
2645: If an active entry is referenced via efmCuAdminProfile or
2646: efmCuPmeAdminProfile, the entry MUST remain 'active' until
2647: all references are removed.
2648:
2649: An 'active' entry SHALL NOT be modified. In order to modify an
2650: existing entry it MUST be taken out of service (by setting
2651: this object to 'notInService'), modified and set 'active'
2652: again."
2653: ::= { efmCuPme10PProfileEntry 8 }
2654:
2655:
2656: efmCuPme10PStatusTable OBJECT-TYPE
2657: SYNTAX SEQUENCE OF EfmCuPme10PStatusEntry
2658: MAX-ACCESS not-accessible
2659: STATUS current
2660: DESCRIPTION
2661: "This table provides status information of EFMCu 10PASS-TS
2662: PMEs (modems).
2663:
2664: This table contains live data from the equipment. As such,
2665: it is NOT persistent."
2666: ::= { efmCuPme10P 2 }
2667:
2668: efmCuPme10PStatusEntry OBJECT-TYPE
2669: SYNTAX EfmCuPme10PStatusEntry
2670: MAX-ACCESS not-accessible
2671: STATUS current
2672: DESCRIPTION
2673: "An entry in the EFMCu 10PASS-TS PME Status table."
2674: INDEX { ifIndex }
2675: ::= { efmCuPme10PStatusTable 1 }
2676:
2677: EfmCuPme10PStatusEntry ::=
2678: SEQUENCE {
2679: efmCuPme10PFECCorrectedBlocks Counter32,
2680: efmCuPme10PFECUncorrectedBlocks Counter32
2681: }
2682:
2683: efmCuPme10PFECCorrectedBlocks OBJECT-TYPE
2684: SYNTAX Counter32
2685: MAX-ACCESS read-only
2686: STATUS current
2687: DESCRIPTION
2688: "The number of received and corrected FEC codewords in this
2689: 10PASS-TS PME.
2690:
2691: This object maps to the aPMEFECCorrectedBlocks attribute in
2692: Clause 30.
2693:
2694: If a Clause 45 MDIO Interface to the PMA/PMD is present,
2695: then this object maps to the 10P FEC correctable errors
2696: register.
2697:
2698: Discontinuities in the value of this counter can occur at
2699: re-initialization of the management system, and at other times
2700: as indicated by the value of ifCounterDiscontinuityTime,
2701: defined in IF-MIB."
2702: REFERENCE
2703: "[802.3ah] 45.2.1.22, 30.11.2.1.8"
2704: ::= { efmCuPme10PStatusEntry 1 }
2705:
2706: efmCuPme10PFECUncorrectedBlocks OBJECT-TYPE
2707: SYNTAX Counter32
2708: MAX-ACCESS read-only
2709: STATUS current
2710: DESCRIPTION
2711: "The number of received uncorrectable FEC codewords in this
2712: 10PASS-TS PME.
2713:
2714: This object maps to the aPMEFECUncorrectableBlocks attribute
2715: in Clause 30.
2716:
2717: If a Clause 45 MDIO Interface to the PMA/PMD is present,
2718: then this object maps to the 10P FEC uncorrectable errors
2719: register.
2720:
2721: Discontinuities in the value of this counter can occur at
2722: re-initialization of the management system, and at other times
2723: as indicated by the value of ifCounterDiscontinuityTime,
2724: defined in IF-MIB."
2725: REFERENCE
2726: "[802.3ah] 45.2.1.23, 30.11.2.1.9"
2727: ::= { efmCuPme10PStatusEntry 2 }
2728:
2729: --
2730: -- Conformance Statements
2731: --
2732:
2733: efmCuGroups OBJECT IDENTIFIER ::= { efmCuConformance 1 }
2734:
2735: efmCuCompliances OBJECT IDENTIFIER ::= { efmCuConformance 2 }
2736:
2737: -- Object Groups
2738:
2739: efmCuBasicGroup OBJECT-GROUP
2740: OBJECTS {
2741: efmCuPAFSupported,
2742: efmCuAdminProfile,
2743: efmCuTargetDataRate,
2744: efmCuTargetSnrMgn,
2745: efmCuAdaptiveSpectra,
2746: efmCuPortSide,
2747: efmCuFltStatus
2748: }
2749: STATUS current
2750: DESCRIPTION
2751: "A collection of objects representing management information
2752: common for all types of EFMCu ports."
2753: ::= { efmCuGroups 1 }
2754:
2755: efmCuPAFGroup OBJECT-GROUP
2756: OBJECTS {
2757: efmCuPeerPAFSupported,
2758: efmCuPAFCapacity,
2759: efmCuPeerPAFCapacity,
2760: efmCuPAFAdminState,
2761: efmCuPAFDiscoveryCode,
2762: efmCuPAFRemoteDiscoveryCode,
2763: efmCuNumPMEs
2764: }
2765: STATUS current
2766: DESCRIPTION
2767: "A collection of objects supporting OPTIONAL PME
2768: Aggregation Function (PAF) and PAF discovery in EFMCu ports."
2769: ::= { efmCuGroups 2 }
2770:
2771: efmCuPAFErrorsGroup OBJECT-GROUP
2772: OBJECTS {
2773: efmCuPAFInErrors,
2774: efmCuPAFInSmallFragments,
2775: efmCuPAFInLargeFragments,
2776: efmCuPAFInBadFragments,
2777: efmCuPAFInLostFragments,
2778: efmCuPAFInLostStarts,
2779: efmCuPAFInLostEnds,
2780: efmCuPAFInOverflows
2781: }
2782: STATUS current
2783: DESCRIPTION
2784: "A collection of objects supporting OPTIONAL error counters
2785: of PAF on EFMCu ports."
2786: ::= { efmCuGroups 3 }
2787:
2788: efmCuPmeGroup OBJECT-GROUP
2789: OBJECTS {
2790: efmCuPmeAdminProfile,
2791: efmCuPmeOperStatus,
2792: efmCuPmeFltStatus,
2793: efmCuPmeSubTypesSupported,
2794: efmCuPmeAdminSubType,
2795: efmCuPmeOperSubType,
2796: efmCuPAFRemoteDiscoveryCode,
2797: efmCuPmeOperProfile,
2798: efmCuPmeSnrMgn,
2799: efmCuPmePeerSnrMgn,
2800: efmCuPmeLineAtn,
2801: efmCuPmePeerLineAtn,
2802: efmCuPmeEquivalentLength,
2803: efmCuPmeTCCodingErrors,
2804: efmCuPmeTCCrcErrors,
2805: efmCuPmeThreshLineAtn,
2806: efmCuPmeThreshSnrMgn
2807: }
2808: STATUS current
2809: DESCRIPTION
2810: "A collection of objects providing information about
2811: a 2BASE-TL/10PASS-TS PME."
2812: ::= { efmCuGroups 4 }
2813:
2814: efmCuAlarmConfGroup OBJECT-GROUP
2815: OBJECTS {
2816: efmCuThreshLowRate,
2817: efmCuLowRateCrossingEnable,
2818: efmCuPmeThreshLineAtn,
2819: efmCuPmeLineAtnCrossingEnable,
2820: efmCuPmeThreshSnrMgn,
2821: efmCuPmeSnrMgnCrossingEnable,
2822: efmCuPmeDeviceFaultEnable,
2823: efmCuPmeConfigInitFailEnable,
2824: efmCuPmeProtocolInitFailEnable
2825: }
2826: STATUS current
2827: DESCRIPTION
2828: "A collection of objects supporting configuration of alarm
2829: thresholds and notifications in EFMCu ports."
2830: ::= { efmCuGroups 5 }
2831:
2832: efmCuNotificationGroup NOTIFICATION-GROUP
2833: NOTIFICATIONS {
2834: efmCuLowRateCrossing,
2835: efmCuPmeLineAtnCrossing,
2836: efmCuPmeSnrMgnCrossing,
2837: efmCuPmeDeviceFault,
2838: efmCuPmeConfigInitFailure,
2839: efmCuPmeProtocolInitFailure
2840: }
2841: STATUS current
2842: DESCRIPTION
2843: "This group supports notifications of significant conditions
2844: associated with EFMCu ports."
2845: ::= { efmCuGroups 6 }
2846:
2847: efmCuPme2BProfileGroup OBJECT-GROUP
2848: OBJECTS {
2849: efmCuPme2BProfileDescr,
2850: efmCuPme2BRegion,
2851: efmCuPme2BsMode,
2852: efmCuPme2BMinDataRate,
2853: efmCuPme2BMaxDataRate,
2854: efmCuPme2BPower,
2855: efmCuPme2BConstellation,
2856: efmCuPme2BProfileRowStatus,
2857: efmCuPme2BsModeDescr,
2858: efmCuPme2BsModeRowStatus,
2859: efmCuPme2BEquivalentLength,
2860: efmCuPme2BMaxDataRatePam16,
2861: efmCuPme2BMaxDataRatePam32,
2862: efmCuPme2BReachRateRowStatus
2863: }
2864: STATUS current
2865: DESCRIPTION
2866: "A collection of objects that constitute a configuration
2867: profile for configuration of 2BASE-TL ports."
2868: ::= { efmCuGroups 7}
2869:
2870: efmCuPme10PProfileGroup OBJECT-GROUP
2871: OBJECTS {
2872: efmCuPme10PProfileDescr,
2873: efmCuPme10PBandplanPSDMskProfile,
2874: efmCuPme10PUPBOReferenceProfile,
2875: efmCuPme10PBandNotchProfiles,
2876: efmCuPme10PPayloadDRateProfile,
2877: efmCuPme10PPayloadURateProfile,
2878: efmCuPme10PProfileRowStatus
2879: }
2880: STATUS current
2881: DESCRIPTION
2882: "A collection of objects that constitute a configuration
2883: profile for configuration of 10PASS-TS ports."
2884: ::= { efmCuGroups 8 }
2885:
2886: efmCuPme10PStatusGroup OBJECT-GROUP
2887: OBJECTS {
2888: efmCuPme10PFECCorrectedBlocks,
2889: efmCuPme10PFECUncorrectedBlocks
2890: }
2891: STATUS current
2892: DESCRIPTION
2893: "A collection of objects providing status information
2894: specific to 10PASS-TS PMEs."
2895: ::= { efmCuGroups 9 }
2896:
2897: -- Compliance Statements
2898: efmCuCompliance MODULE-COMPLIANCE
2899: STATUS current
2900: DESCRIPTION
2901: "The compliance statement for 2BASE-TL/10PASS-TS interfaces.
2902: Compliance with the following external compliance statements
2903: is REQUIRED:
2904:
2905: MIB Module Compliance Statement
2906: ---------- --------------------
2907: IF-MIB ifCompliance3
2908: EtherLike-MIB dot3Compliance2
2909: MAU-MIB mauModIfCompl3
2910:
2911: Compliance with the following external compliance statements
2912: is OPTIONAL for implementations supporting PME Aggregation
2913: Function (PAF) with flexible cross-connect between the PCS
2914: and PME ports:
2915:
2916: MIB Module Compliance Statement
2917: ---------- --------------------
2918: IF-INVERTED-STACK-MIB ifInvCompliance
2919: IF-CAP-STACK-MIB ifCapStackCompliance"
2920:
2921: MODULE -- this module
2922: MANDATORY-GROUPS {
2923: efmCuBasicGroup,
2924: efmCuPmeGroup,
2925: efmCuAlarmConfGroup,
2926: efmCuNotificationGroup
2927: }
2928:
2929: GROUP efmCuPme2BProfileGroup
2930: DESCRIPTION
2931: "Support for this group is only required for implementations
2932: supporting 2BASE-TL Phy."
2933:
2934: GROUP efmCuPme10PProfileGroup
2935: DESCRIPTION
2936: "Support for this group is only required for implementations
2937: supporting 10PASS-TS Phy."
2938:
2939: GROUP efmCuPAFGroup
2940: DESCRIPTION
2941: "Support for this group is only required for
2942: implementations supporting PME Aggregation Function (PAF)."
2943:
2944: GROUP efmCuPAFErrorsGroup
2945: DESCRIPTION
2946: "Support for this group is OPTIONAL for implementations
2947: supporting PME Aggregation Function (PAF)."
2948:
2949: GROUP efmCuPme10PStatusGroup
2950: DESCRIPTION
2951: "Support for this group is OPTIONAL for implementations
2952: supporting 10PASS-TS Phy."
2953:
2954: OBJECT efmCuPmeSubTypesSupported
2955: SYNTAX BITS {
2956: ieee2BaseTLO(0),
2957: ieee2BaseTLR(1),
2958: ieee10PassTSO(2),
2959: ieee10PassTSR(3)
2960: }
2961: DESCRIPTION
2962: "Support for all subtypes is not required. However at least
2963: one value SHALL be supported"
2964:
2965: OBJECT efmCuPmeAdminSubType
2966: MIN-ACCESS read-only
2967: DESCRIPTION
2968: "Write access is not required (needed only for PMEs
2969: supporting more than a single subtype, e.g.
2970: ieee2BaseTLO and ieee2BaseTLR or ieee10PassTSO and
2971: ieee10PassTSR)"
2972:
2973: OBJECT efmCuTargetSnrMgn
2974: MIN-ACCESS read-only
2975: DESCRIPTION
2976: "Write access is OPTIONAL. For PHYs without write access
2977: the target SNR margin SHALL be fixed at 5dB for 2BASE-TL
2978: and 6dB for 10PASS-TS."
2979:
2980: OBJECT efmCuAdaptiveSpectra
2981: MIN-ACCESS read-only
2982: DESCRIPTION
2983: "Write access is OPTIONAL. For PHYs without write access
2984: the default value SHOULD be false."
2985:
2986: ::= { efmCuCompliances 1 }
2987: END
2988:
2989: --
2990: -- Copyright (C) The IETF Trust (2007).
2991: --
2992: -- This document is subject to the rights, licenses and restrictions
2993: -- contained in BCP 78, and except as set forth therein, the authors
2994: -- retain all their rights.
2995: --
2996: -- This document and the information contained herein are provided on an
2997: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
2998: -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
2999: -- THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
3000: -- OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
3001: -- THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
3002: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
3003: --
3004: --
3005: -- Intellectual Property
3006: --
3007: -- The IETF takes no position regarding the validity or scope of any
3008: -- Intellectual Property Rights or other rights that might be claimed to
3009: -- pertain to the implementation or use of the technology described in
3010: -- this document or the extent to which any license under such rights
3011: -- might or might not be available; nor does it represent that it has
3012: -- made any independent effort to identify any such rights. Information
3013: -- on the procedures with respect to rights in RFC documents can be
3014: -- found in BCP 78 and BCP 79.
3015: --
3016: -- Copies of IPR disclosures made to the IETF Secretariat and any
3017: -- assurances of licenses to be made available, or the result of an
3018: -- attempt made to obtain a general license or permission for the use of
3019: -- such proprietary rights by implementers or users of this
3020: -- specification can be obtained from the IETF on-line IPR repository at
3021: -- http://www.ietf.org/ipr.
3022: --
3023: -- The IETF invites any interested party to bring to its attention any
3024: -- copyrights, patents or patent applications, or other proprietary
3025: -- rights that may cover technology that may be required to implement
3026: -- this standard. Please address the information to the IETF at
3027: -- ietf-ipr@ietf.org.
3028: --
3029: --
3030: -- Acknowledgment
3031: --
3032: -- Funding for the RFC Editor function is provided by the IETF
3033: -- Administrative Support Activity (IASA).
3034: