1 module wire-interface-2-0 {
\r
3 namespace "urn:onf:yang:wire-interface-2-0";
\r
4 prefix wire-interface;
\r
6 import ietf-yang-types {
\r
9 import core-model-1-4 {
\r
14 "openBackhaul.com proposal to Open Networking Foundation (ONF)";
\r
16 "WG Web : https://github.com/openBackhaul/Overview
\r
17 WG List: WireInterface@openBackhaul.com
\r
18 Editor : Thorsten Heinze
\r
19 Email : Thorsten.Heinze@openBackhaul.com";
\r
21 "This model is for vendor agnostic management of Ethernet PHY interfaces.
\r
22 Supported: '10BASE5', 'FOIRL', '10BASE2', '10BROAD36', '10BASE-T', '10BASE-FP', '10BASE-FB', '10BASE-FL', '100BASE-T4', '100BASE-TX', '100BASE-BX10D', '100BASE-BX10U', '100BASE-FX', '100BASE-LX10', '100BASE-T2', '1000BASE-X', '1000BASE-BX10D', '1000BASE-BX10U', '1000BASE-LX', '1000BASE-LX10', '1000BASE-SX', '1000BASE-CX', '1000BASE-KX', '1000BASE-T', '10GBASE-X', '10GBASE-LX4', '10GBASE-KX4', '10GBASE-R', '10GBASE-ER', '10GBASE-LR', '10GBASE-SR', '10GBASE-LRM', '10GBASE-KR', '10GBASE-T', '10GBASE-PR-D1', '10GBASE-PR-D2', '10GBASE-PR-D3', '10GBASE-PR-D4', '10GBASE-PR-U1', '10GBASE-PR-U2', '10GBASE-PR-U3', '10GBASE-PR-U4', '40GBASE-R', '40GBASE-KR4', '40GBASE-CR4', '40GBASE-SR4', '4x10GBASE-SR', '40GBASE-LR4', '40GBASE-ER4', '40GBASE-FR', '100GBASE-R', '100GBASE-CR4', '100GBASE-KR4', '100GBASE-KP4', '100GBASE-CR10', '100GBASE-SR4', '100GBASE-SR10', '2x40GBASE-SR', '10x10GBASE-SR', '12x10GBASE-SR', '100GBASE-LR4', '100GBASE-ER4' and 'NOT_YET_DEFINED.
\r
23 NOT supported: '2BASE-TL', '10PASS-TS', '1000BASE-PX10-D', '1000BASE-PX10-U', '1000BASE-PX20-D', '1000BASE-PX20-U', '1000BASE-PX30-D', '1000BASE-PX30-U', '1000BASE-PX40-D', '1000BASE-PX40-U', '10GBASE-W', '10GBASE-EW', '10GBASE-LW', '10GBASE-SW', '10/1GBASE-PRX-D1', '10/1GBASE-PRX-D2', '10/1GBASE-PRX-D3', '10/1GBASE-PRX-D4', '10/1GBASE-PRX-U1', '10/1GBASE-PRX-U2', '10/1GBASE-PRX-U3' and '10/1GBASE-PRX-U4'.
\r
25 Copyright 2019 openBackhaul.com
\r
27 Licensed under the Apache License, Version 2.0 (the 'License');
\r
28 you may not use this file except in compliance with the License.
\r
29 You may obtain a copy of the License at
\r
30 http://www.apache.org/licenses/LICENSE-2.0
\r
31 Unless required by applicable law or agreed to in writing, software
\r
32 distributed under the License is distributed on an 'AS IS' BASIS,
\r
33 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
\r
34 See the License for the specific language governing permissions and
\r
35 limitations under the License.";
\r
37 revision 2020-01-23 {
\r
39 "Model for the Transport SDN Pilot at Telefonica Germany.
\r
40 Please view https://github.com/openBackhaul/wireInterface/issues for changes.";
\r
42 "https://github.com/openBackhaul/wireInterface/tree/tsp: Model definition
\r
43 https://github.com/openBackhaul/onfCoreIm/tree/tsp: ONF TR-512 Core IM incl. Profile and enhanced Equipment definition";
\r
45 revision 2019-11-22 {
\r
47 "Model for the Transport SDN Pilot at Telefonica Germany.
\r
48 Please view https://github.com/openBackhaul/wireInterface/issues for changes.";
\r
50 "https://github.com/openBackhaul/wireInterface/tree/tsp: Model definition
\r
51 https://github.com/openBackhaul/onfCoreIm/tree/tsp: ONF TR-512 Core IM incl. Profile and enhanced Equipment definition";
\r
53 revision 2019-10-30 {
\r
55 "Model for the Transport SDN Pilot at Telefonica Germany.
\r
56 Please view https://github.com/openBackhaul/wireInterface/issues for changes.";
\r
58 "https://github.com/openBackhaul/wireInterface/tree/tsp: Model definition
\r
59 https://github.com/openBackhaul/onfCoreIm/tree/tsp: ONF TR-512 Core IM incl. Profile and enhanced Equipment definition";
\r
61 revision 2019-07-11 {
\r
63 "Model for the Transport SDN Pilot at Telefonica Germany.
\r
64 Please view https://github.com/openBackhaul/wireInterface/issues for changes.";
\r
66 "https://github.com/openBackhaul/wireInterface/tree/tsp: Model definition
\r
67 https://github.com/openBackhaul/onfCoreIm/tree/tsp: ONF TR-512 Core IM incl. Profile and enhanced Equipment definition";
\r
70 identity LAYER_PROTOCOL_NAME_TYPE_WIRE_LAYER {
\r
71 base core-model:LAYER_PROTOCOL_NAME_TYPE;
\r
76 augment "/core-model:control-construct/core-model:logical-termination-point/core-model:layer-protocol" {
\r
77 when "derived-from-or-self(./core-model:layer-protocol-name, 'wire-interface:LAYER_PROTOCOL_NAME_TYPE_WIRE_LAYER')";
\r
78 uses wire-interface-lp-spec;
\r
83 /****************************************
\r
84 * package notifications
\r
85 **************************************/
\r
87 notification object-creation-notification {
\r
88 uses object-creation-notification;
\r
93 grouping object-creation-notification {
\r
99 "Counts object creation notifications.";
\r
102 type yang:date-and-time;
\r
103 default "2010-11-20T14:00:00+01:00";
\r
108 leaf object-id-ref {
\r
110 path "/core-model:control-construct/core-model:logical-termination-point/core-model:uuid";
\r
111 require-instance false;
\r
119 default "Type of created object not specified.";
\r
128 notification object-deletion-notification {
\r
129 uses object-deletion-notification;
\r
134 grouping object-deletion-notification {
\r
140 "Counts object deletion notifications.";
\r
143 type yang:date-and-time;
\r
144 default "2010-11-20T14:00:00+01:00";
\r
149 leaf object-id-ref {
\r
151 path "/core-model:control-construct/core-model:logical-termination-point/core-model:uuid";
\r
152 require-instance false;
\r
162 notification attribute-value-changed-notification {
\r
163 uses attribute-value-changed-notification;
\r
168 grouping attribute-value-changed-notification {
\r
174 "Counts attribute value changed notifications.";
\r
177 type yang:date-and-time;
\r
178 default "2010-11-20T14:00:00+01:00";
\r
183 leaf object-id-ref {
\r
185 path "/core-model:control-construct/core-model:logical-termination-point/core-model:uuid";
\r
186 require-instance false;
\r
192 leaf attribute-name {
\r
194 default "Attribute name not specified.";
\r
197 "Name of the attribute that has been changed.";
\r
201 default "New value not specified.";
\r
204 "Attribute value converted to a string (xml, json, ...)";
\r
210 notification problem-notification {
\r
211 uses problem-notification;
\r
216 grouping problem-notification {
\r
222 "Counts problem notifications";
\r
225 type yang:date-and-time;
\r
226 default "2010-11-20T14:00:00+01:00";
\r
231 leaf object-id-ref {
\r
233 path "/core-model:control-construct/core-model:logical-termination-point/core-model:uuid";
\r
234 require-instance false;
\r
242 default "Problem name not specified.";
\r
245 "Name of the problem according to supportedAlarmList";
\r
248 type severity-type;
\r
249 default "SEVERITY_TYPE_WARNING";
\r
252 "Severity of the problem according to problemKindSeverity";
\r
258 /****************************************
\r
259 * grouping statements for object classes
\r
260 **************************************/
\r
261 /****************************************
\r
262 * package super-classes
\r
263 **************************************/
\r
265 grouping current-problem {
\r
266 leaf sequence-number {
\r
270 "Unique sequence number of the current problem object.";
\r
273 type yang:date-and-time;
\r
274 default "2010-11-20T14:00:00+01:00";
\r
277 "Time when the alarm was raised";
\r
279 leaf problem-severity {
\r
280 type severity-type;
\r
281 default "SEVERITY_TYPE_NOT_YET_DEFINED";
\r
284 "Severity of the alarm.";
\r
290 grouping current-performance {
\r
292 type yang:date-and-time;
\r
293 default "2010-11-20T14:00:00+01:00";
\r
296 "The timestamp associated with when the current data was collected.";
\r
298 leaf suspect-interval-flag {
\r
303 "This attribute is used to indicate that the performance data for the current period may not be reliable. Some reasons for this to occur are:
\r
304 – Suspect data were detected by the actual resource doing data collection.
\r
305 – Transition of the administrativeState attribute to/from the 'lock' state.
\r
306 – Transition of the operationalState to/from the 'disabled' state.
\r
307 – Scheduler setting that inhibits the collection function.
\r
308 – The performance counters were reset during the interval.
\r
309 – The currentData (or subclass) object instance was created during the monitoring period.";
\r
311 leaf elapsed-time {
\r
317 "Number of seconds that elapsed since the last reset of the counter.";
\r
321 default "Scanner ID not defined.";
\r
326 leaf granularity-period {
\r
327 type granularity-period-type;
\r
330 "Time period between reset of the underlying counter.";
\r
336 grouping historical-performance {
\r
337 leaf suspect-interval-flag {
\r
342 "This attribute indicates that the data collected during the interval is suspect.";
\r
344 leaf history-data-id {
\r
346 default "History Data ID not defined.";
\r
351 leaf granularity-period {
\r
352 type granularity-period-type;
\r
355 "Time period between reset of the underlying counter.";
\r
357 leaf period-end-time {
\r
358 type yang:date-and-time;
\r
361 "Time when the counter values have been recorded and the counter reset.";
\r
367 grouping wire-interface-lp-spec {
\r
368 container wire-interface-pac {
\r
369 uses wire-interface-pac;
\r
377 grouping wire-interface-pac {
\r
378 container wire-interface-capability {
\r
380 uses wire-interface-capability;
\r
384 container wire-interface-configuration {
\r
385 uses wire-interface-configuration;
\r
389 container wire-interface-status {
\r
391 uses wire-interface-status;
\r
395 container wire-interface-current-problems {
\r
397 uses wire-interface-current-problems;
\r
401 container wire-interface-current-performance {
\r
403 uses wire-interface-current-performance;
\r
407 container wire-interface-historical-performances {
\r
409 uses wire-interface-historical-performances;
\r
417 grouping wire-interface-capability {
\r
418 list supported-pmd-kind-list {
\r
424 "List of Physical Medium Dependent (PMD) that can be operated";
\r
426 leaf auto-pmd-negotiation-is-avail {
\r
431 "1 = device is supporting auto-negotiation";
\r
433 leaf auto-negotiation-pmd-selection-is-avail {
\r
438 "1 = device is supporting restricting auto-negotiation on a pre-defined list of PMDs";
\r
440 leaf-list supported-signal-ordering-kind-list {
\r
441 type signal-ordering-kind-type;
\r
445 "Describes the different (e.g. MDI, MDI-X) ways of ordering the signals on the physical medium";
\r
447 leaf auto-signal-ordering-is-avail {
\r
452 "1 = there is a mechanism for automatically crossing over tx and rx implemented";
\r
454 leaf configuration-of-rx-sync-preference-is-avail {
\r
459 "1 = Configuration of the behavior during the synchronization of transmitter and receiver is available. This attribute has nothing to do with clock signals.";
\r
462 type mii-kind-type;
\r
463 default "MII_KIND_TYPE_NOT_YET_DEFINED";
\r
466 "Kind of Medium Independent Interface (MII) provided by this Medium Attachment Unit (MAU) (e.g. SFP, moldered port)";
\r
469 type mdi-kind-type;
\r
470 default "MDI_KIND_TYPE_NOT_YET_DEFINED";
\r
473 "Kind of Medium Dependent Interface (MDI) provided by this Medium Attachment Unit (MAU)";
\r
475 leaf required-medium-kind {
\r
476 type medium-kind-type;
\r
477 default "MEDIUM_KIND_TYPE_NOT_YET_DEFINED";
\r
480 "Kind of medium required for operating this Medium Attachment Unit (MAU), more like an information field";
\r
482 leaf-list wavelength-min-list {
\r
489 "Source: SFF-8690. Minimum laser wavelength in pico meter, -1 = not applicable, 0 = not known, if (wavelengthMin==wavelengthMax): wavelength cannot be configured; multiplicity=0..3 for 10GBASE-LX4 according to 802.3 53.5. Value to be read from the EPROM of the SFP.";
\r
491 leaf-list wavelength-max-list {
\r
498 "Source: SFF-8690. Maximum laser wavelength in pico meter, -1 = not applicable, 0 = not known, if (wavelengthMax==wavelengthMin): wavelength cannot be configured; multiplicity=0..3 for 10GBASE-LX4 according to 802.3 53.5. Value to be read from the EPROM of the SFP.";
\r
500 leaf wavelength-grid-min {
\r
506 "Source: SFF-8690. Minimum grid spacing supported by the transceiver, -1 = not applicable, 0 = not known";
\r
508 leaf short-reach-mode-is-avail {
\r
513 "1 = Indicates that Short Reach Mode for 10GBASE-T according to 802.3 45.2.1.64 is available";
\r
515 leaf eee-is-avail {
\r
520 "1 = Indicates that Energy-Efficient Ethernet (EEE) is available at the device.";
\r
522 leaf unidirectional-operation-is-avail {
\r
527 "Source: 802.3. 1 = Medium Attachment Unit (MAU) able to transmit from Media Independent Interface (MII) regardless of whether the MAU has determined that a valid link has been established, 0 = MAU able to transmit from MII only when the MAU has determined that a valid link has been established";
\r
529 leaf rxlevel-low-threshold {
\r
535 "Threshold for alarming low RX levels. Value pre-defined by SFP manufacturer (SFF- 8472)";
\r
537 leaf rxlevel-high-threshold {
\r
543 "Threshold for alarming high RX levels. Value pre-defined by SFP manufacturer (SFF- 8472)";
\r
545 leaf temperature-low-threshold {
\r
551 "Threshold for alarming low temperature values. Value pre-defined by SFP manufacturer (SFF- 8472)
\r
552 Might move to somewhere in the Physical Segment of the Core IM";
\r
554 leaf temperature-high-threshold {
\r
560 "Threshold for alarming high temperature values. Value pre-defined by SFP manufacturer (SFF- 8472)
\r
561 Might move to somewhere in the Physical Segment of the Core IM";
\r
563 leaf configuration-of-number-of-bip-errors-per-ses-is-avail {
\r
568 "1 = SET operation on the Line SES threshold defined by aLineSESThreshold in 30.8.1.1.11 of 802.3-2015 is available.";
\r
570 leaf admin-shut-down-is-avail {
\r
575 "1 = Manual switching on and off of the interface without deleting it (underlying OSI network layers are also not affected) is available.";
\r
577 leaf isolation-is-avail {
\r
582 "1 = Separation of the PHY from higher network layers is supported by the device. Maintenance feature. Source: 802.3. ";
\r
584 leaf-list supported-loop-back-kind-list {
\r
585 type loop-back-type;
\r
590 "Source: 802.3 45.2.1.12.1 PMA remote loopback ability. List of supported kinds of looping back of header information to the remote site.";
\r
592 leaf maintenance-timer-range {
\r
594 default "Range of the maintenance timer not yet defined.";
\r
597 "Available time periods for maintenance configurations (e.g. the loop back) to be described. Concrete values shall be separated by commas (e.g. '10, 60, 360'). Ranges shall be expressed as two values separated by a minus (e.g. '10-360').";
\r
599 leaf-list supported-alarm-list {
\r
604 "Available alarms to be listed. Mandatory: 'rxLos'. Optional: 'txFault', 'tempHigh', 'tempLow', 'rxLevelHigh', 'rxLevelLow', 'vccHigh', 'vccLow', 'txBiasHigh', 'txBiasLow', 'txPowerHigh', 'txPowerLow', 'laserTempHigh', 'laserTempLow', 'tecCurrentHigh', 'tecCurrentLow'. Further alarms might be added by the device.";
\r
606 leaf performance-monitoring-is-avail {
\r
611 "1 = Collection and aggregation of performance values is available.";
\r
617 grouping wire-interface-configuration {
\r
618 leaf interface-name {
\r
620 default "Interface name not yet defined.";
\r
622 "Description of the interface, could be a name, could be a number. Free text field to be filled by the operator.";
\r
624 leaf interface-is-on {
\r
628 "Source: 802.3 according 30.3.2.2.1 acPhyAdminControl. 1 = Activation of the interface (it gets powered and can be managed even if the transceiver is not yet transmitting or receiving). In case there is no Medium Attachment Unit (MAU) (e.g. no SFP in the cage) SETting (interfaceIsOn=1) must be ignored and GETing must return (interfaceIsOn=0)";
\r
630 leaf remote-wire-interface-name {
\r
632 default "Remote wire interface name not yet defined.";
\r
634 "Text field for defining the wire interface this one is connected with. Ideally used for entering unique numbers or names for unambiguously identifying the connection within the network";
\r
636 leaf-list transceiver-is-on-list {
\r
641 "Source: 802.3 45.2.1.8 PMD transmit disable register (Register 1.9). 1 = Activation of the transmitter and receiver (e.g. laser) of the PHY; transceiverIsOnList[0]:total interface; transceiverIsOnList[1..10] different lanes of a multilane Medium Attachment Unit (MAU)";
\r
643 leaf auto-pmd-negotiation-is-on {
\r
647 "Only relevant if (autoPmdNegotiationIsAvail == 1). 1 = Auto-negotiation is switched on";
\r
649 leaf fixed-pmd-kind {
\r
651 path "/core-model:control-construct/core-model:logical-termination-point/core-model:layer-protocol/wire-interface:wire-interface-pac/wire-interface:wire-interface-capability/wire-interface:supported-pmd-kind-list/wire-interface:pmd-name";
\r
652 require-instance false;
\r
654 must 'boolean(/core-model:control-construct/core-model:logical-termination-point/core-model:layer-protocol/wire-interface:wire-interface-pac/wire-interface:wire-interface-capability/wire-interface:supported-pmd-kind-list[pmd-name=current()])';
\r
656 "If (autoPmdNegotiationIsOn==0) : Configuration of the concrete kind of Physical Medium Dependent (PMD). If (autoNegotiationIsOn=1) value of this field becomes irrelevant";
\r
658 leaf-list auto-negotiation-pmd-list {
\r
660 path "/core-model:control-construct/core-model:logical-termination-point/core-model:layer-protocol/wire-interface:wire-interface-pac/wire-interface:wire-interface-capability/wire-interface:supported-pmd-kind-list/wire-interface:pmd-name";
\r
661 require-instance false;
\r
663 must 'boolean(/core-model:control-construct/core-model:logical-termination-point/core-model:layer-protocol/wire-interface:wire-interface-pac/wire-interface:wire-interface-capability/wire-interface:supported-pmd-kind-list[pmd-name=current()])';
\r
665 "If (autoPmdNegotiationIsOn==1) AND (autoNegotiationPmdSelectionIsAvail==1), this list defines the selection of PMDs the automated negotiation process is allowed to choose from. If no entry, the automated negotiation process is allowed to choose from all available PMDs.";
\r
667 leaf auto-signal-ordering-is-on {
\r
671 "Only relevant if (autoSignalOrderingIsAvail == 1). 1 = e.g. auto-MDI-X is switched on";
\r
673 leaf fixed-signal-ordering-kind {
\r
674 type signal-ordering-kind-type;
\r
675 default "SIGNAL_ORDERING_KIND_TYPE_NOT_YET_DEFINED";
\r
677 "If (autoSignalOrderingIsOn==0) configuration of the concrete kind of signal ordering on the media (e.g. MDI, or MDI-X). If (autoSignalOrderingIsOn=1) value of this field becomes irrelevant";
\r
679 leaf-list wavelength-list {
\r
685 "Source: SFF-8690. Wavelength of the signal of laser in pico meter; multiplicity=0..3 for 10GBASE-LX4 according to 802.3 53.5";
\r
687 leaf rx-sync-preference {
\r
688 type rx-sync-preference-type;
\r
689 default "RX_SYNC_PREFERENCE_TYPE_NOT_YET_DEFINED";
\r
691 "Source: 802.3. Only relevant if (configurationOfRxSyncPreferenceIsAvail == 1). Configuration of the behavior during the negotiation of the wire interface (master), which is sending a continuous stream of symbols for the remote site (slave) to synchronize its receiver on it. This attribute is for synchronizing transmitter and receiver and has nothing to do with clock signals.";
\r
693 leaf short-reach-mode-is-on {
\r
697 "Only relevant if (shortReachModeIsAvail == 1). Activation of the Short Reach Mode for 10GBASE-T according to 802.3 45.2.1.64";
\r
703 "Only relevant if (eeeIsAvail == 1). 1 = Energy Efficient Ethernet is activated\n";
\r
705 leaf unidirectional-operation-is-on {
\r
709 "Source: 802.3. Only relevant if (unidirectionalOperationIsAvail == 1). 1 = Enable transmit from media independent interface regardless of whether the PHY has determined that a valid link has been established, 0 = Enable transmit from media independent interface only when the PHY has determined that a valid link has been established";
\r
711 leaf number-of-bip-errors-per-ses {
\r
715 "Only relevant if (configurationOfNumberOfBipErrorsPerSesIsAvail == 1). SET operation on the Line SES threshold defined by aLineSESThreshold in 30.8.1.1.11 of 802.3-2015. This attribute configures the minimum number of BIP errors that have to occur in one second to count this second as a SES instead of an ES. According to 802.3, a value of 9835 should be the hardware default value, which should also apply after restarting the interface.";
\r
717 leaf restart-pmd-negotiation-is-on {
\r
721 "Source: 802.3. Restarts the auto negotiation process";
\r
723 leaf isolation-is-on {
\r
727 "Maintenance Feature. Only relevant if (isolationIsAvail == 1). Source: 802.3. 1 = Activation of the separation of the PHY from higher network layers. Maintenance feature.";
\r
729 leaf loop-back-kind-on {
\r
730 type loop-back-type;
\r
731 default "LOOP_BACK_TYPE_NONE";
\r
733 "Maintenance Feature. Source:802.3 according 22.2.4.1.2 Loopback. The currently configured type of looping back of the wire interface header shall be expressed here. The received header is returned to the remote site.";
\r
735 leaf maintenance-timer {
\r
740 "Time of existence of any maintenance configuration (e.g. the loop back). Valid values are defined in WireInterface::WireInterfaceCapability::maintenanceTimerRange. In case the hardware would implement just a single timer for maintenance at all kinds and instances of interfaces, this attribute should affect this single timer.";
\r
742 list problem-kind-severity-list {
\r
743 key "problem-kind-name";
\r
745 uses problem-kind-severity-type;
\r
747 "Severity of the problem to be configured.";
\r
749 leaf performance-monitoring-is-on {
\r
753 "Only relevant if (performanceMonitoringIsAvail==1). 1 = Collection and aggregation of performance values is switched on.";
\r
759 grouping wire-interface-status {
\r
760 leaf interface-status {
\r
761 type interface-status-type;
\r
762 default "INTERFACE_STATUS_TYPE_NOT_YET_DEFINED";
\r
765 "Source: 802.3 according 30.3.2.1.7 aPhyAdminState. 1 = A Physical layer entity (PHY) exists (including Medium Attachment Unit (e.g. SFP) ) and it is powered and can be managed";
\r
767 leaf-list receive-signal-is-detected-list {
\r
773 "Source: 802.3 45.2.1.9 PMD receive signal detect. 1 = Receiver (e.g. laser) detects signal; receiveSignalIsDetected[0]:total interface; receiveSignalIsDetected[1..10] different lanes of a multilane Medium Attachment Unit (MAU)";
\r
775 leaf pmd-negotiation-state {
\r
776 type pmd-negotiation-state-type;
\r
777 default "PMD_NEGOTIATION_STATE_TYPE_NOT_YET_DEFINED";
\r
780 "Source: 802.3. Status of the Physical Medium Dependent (PMD) negotiation process (auto-neg)";
\r
787 "Source: Inverse of 802.3 45.2.1.2.3 Fault (1.1.7). If (interfaceIsUp==1) BUT (pmdIsUp==0) : there is a fault in either transmit or receive path";
\r
789 leaf pmd-kind-cur {
\r
791 path "/core-model:control-construct/core-model:logical-termination-point/core-model:layer-protocol/wire-interface:wire-interface-pac/wire-interface:wire-interface-capability/wire-interface:supported-pmd-kind-list/wire-interface:pmd-name";
\r
792 require-instance false;
\r
796 "Indicates the kind of Physical Medium Dependent (PMD) currently operated at this interface";
\r
798 leaf signal-ordering-kind-cur {
\r
799 type signal-ordering-kind-type;
\r
800 default "SIGNAL_ORDERING_KIND_TYPE_NOT_YET_DEFINED";
\r
803 "Reference on a SignalOrderingType for expressing the currently active way of ordering the signals on the physical medium.";
\r
805 leaf rx-sync-role {
\r
806 type rx-sync-role-type;
\r
807 default "RX_SYNC_ROLE_TYPE_NOT_YET_DEFINED";
\r
810 "Indicates the result of the negotiation of the wire interface (master), which is sending a continuous stream of symbols for the remote site (slave) synchronizing its receiver on it";
\r
817 "1 = Energy Efficient Ethernet is supported at both ends of the link and it is activated";
\r
824 "If (transceiverIsUp==1) AND (linkIsUp==1) : communication is established to the remote site";
\r
826 leaf link-is-idle {
\r
831 "If (linkIsUp==1) AND (eeeIsAvail==1) AND (eeeIsOn==1) AND (linkIsIdle==1) : link is currently in idle mode. If Energy Efficient Ethernet is not supported or switched off, this attribute must be 0.";
\r
833 leaf loop-back-kind-up {
\r
834 type loop-back-type;
\r
835 default "LOOP_BACK_TYPE_NONE";
\r
838 "The currently active (not just configured) type of looping back of the wire interface header shall be expressed here. The received header is returned to the remote site.";
\r
840 leaf tx-level-cur {
\r
846 "Current transmit power";
\r
848 leaf-list rx-level-cur-list {
\r
855 "Current receive power; Also used for receive signal power measured at the Medium Dependent Interface (MDI) of 10GBASE-T during training as described in 802.3 55.4.3.1";
\r
857 leaf performance-monitoring-is-up {
\r
862 "1 = Performance values are currently collected and aggregated.";
\r
868 grouping wire-interface-current-problems {
\r
869 list current-problem-list {
\r
870 key "sequence-number";
\r
872 uses wire-interface-current-problem-type;
\r
876 leaf number-of-current-problems {
\r
881 "Number of alarms, which are currently active on this interface.";
\r
883 leaf time-of-latest-change {
\r
884 type yang:date-and-time;
\r
885 default "2010-11-20T14:00:00+01:00";
\r
888 "Date and time when the list of alarms has been changed for the last time.";
\r
894 grouping wire-interface-current-performance {
\r
895 list current-performance-data-list {
\r
896 key "granularity-period";
\r
900 uses wire-interface-current-performance-type;
\r
902 "At least values of the counters, which are reset every 15 minutes, are to be provided. If available, the current values of the counters, which are reset every 24 hour, can be provided, too.";
\r
904 leaf number-of-current-performance-sets {
\r
909 "Number of sets of current performance values, which are provided in the list.";
\r
912 "Aggregated performance information of the air interface at a particular moment.";
\r
915 grouping wire-interface-historical-performances {
\r
916 list historical-performance-data-list {
\r
917 key "granularity-period period-end-time";
\r
919 uses wire-interface-historical-performance-type;
\r
923 leaf number-of-historical-performance-sets {
\r
928 "Number of sets of historical performance values, which are provided in the list.";
\r
930 leaf time-of-latest-change {
\r
931 type yang:date-and-time;
\r
932 default "2010-11-20T14:00:00+01:00";
\r
935 "Date and time when the list of sets of historical performance values has been changed for the last time (e.g. new one added or existing one deleted).";
\r
938 "Aggregated performance information of the air interface for a pre-defined measurement interval.";
\r
941 grouping pmd-kind {
\r
946 "To be chosen from the following list of PMD names according to IEEE 802.3 '10BASE5', 'FOIRL', '10BASE2', '10BROAD36', '10BASE-T', '10BASE-FP', '10BASE-FB', '10BASE-FL', '100BASE-T4', '100BASE-TX', '100BASE-BX10D', '100BASE-BX10U', '100BASE-FX', '100BASE-LX10', '100BASE-T2', '1000BASE-X', '1000BASE-BX10D', '1000BASE-BX10U', '1000BASE-LX', '1000BASE-LX10', '1000BASE-SX', '1000BASE-CX', '1000BASE-KX', '1000BASE-T', '10GBASE-X', '10GBASE-LX4', '10GBASE-KX4', '10GBASE-R', '10GBASE-ER', '10GBASE-LR', '10GBASE-SR', '10GBASE-LRM', '10GBASE-KR', '10GBASE-T', '10GBASE-PR-D1', '10GBASE-PR-D2', '10GBASE-PR-D3', '10GBASE-PR-D4', '10GBASE-PR-U1', '10GBASE-PR-U2', '10GBASE-PR-U3', '10GBASE-PR-U4', '40GBASE-R', '40GBASE-KR4', '40GBASE-CR4', '40GBASE-SR4', '4x10GBASE-SR', '40GBASE-LR4', '40GBASE-ER4', '40GBASE-FR', '100GBASE-R', '100GBASE-CR4', '100GBASE-KR4', '100GBASE-KP4', '100GBASE-CR10', '100GBASE-SR4', '100GBASE-SR10', '2x40GBASE-SR', '10x10GBASE-SR', '12x10GBASE-SR', '100GBASE-LR4', '100GBASE-ER4' and 'NOT_YET_DEFINED'. Some PMDs are distinguishing Full Duplex and Half Duplex. '_FD' and '_HD' are to be attached to the respective PMD name accordingly.";
\r
950 default "NOT_YET_DEFINED";
\r
952 "Line speed of the PMD. Value to be chosen from '2Mbit/s', '10Mbit/s', '100Mbit/s', '1000Mbit/s', '10Gbit/s', '40Gbit/s', '100Gbit/s' or 'NOT_YET_DEFINED'. This field is not for calculation purposes, but for supporting selection of the correct PMD on application layer.";
\r
956 default "DUPLEX_TYPE_NOT_YET_DEFINED";
\r
958 "To be expressed, whether the PMD is full duplex or just half duplex. This field is not for configuration purposes, but for supporting selection of the correct PMD on application layer.";
\r
964 /****************************************
\r
965 * typedef statements
\r
966 **************************************/
\r
968 typedef loop-back-type {
\r
970 base LOOP_BACK_TYPE;
\r
976 typedef rx-sync-preference-type {
\r
978 base RX_SYNC_PREFERENCE_TYPE;
\r
984 typedef rx-sync-role-type {
\r
986 base RX_SYNC_ROLE_TYPE;
\r
992 typedef mii-kind-type {
\r
994 base MII_KIND_TYPE;
\r
1000 typedef mdi-kind-type {
\r
1001 type identityref {
\r
1002 base MDI_KIND_TYPE;
\r
1008 typedef medium-kind-type {
\r
1009 type identityref {
\r
1010 base MEDIUM_KIND_TYPE;
\r
1016 typedef duplex-type {
\r
1017 type identityref {
\r
1024 typedef signal-ordering-kind-type {
\r
1025 type identityref {
\r
1026 base SIGNAL_ORDERING_KIND_TYPE;
\r
1032 typedef pmd-negotiation-state-type {
\r
1033 type identityref {
\r
1034 base PMD_NEGOTIATION_STATE_TYPE;
\r
1040 /*********************************************
\r
1041 * grouping statements for complex data types
\r
1042 *******************************************/
\r
1044 identity LOOP_BACK_TYPE {
\r
1049 identity LOOP_BACK_TYPE_NONE {
\r
1050 base LOOP_BACK_TYPE;
\r
1055 identity LOOP_BACK_TYPE_EXTERNAL {
\r
1056 base LOOP_BACK_TYPE;
\r
1059 If the internal loopback test succeeds but the external loopback fails, the Medium Attachment Unit (MAU) is faulty (e.g. SFP has to be replaced)";
\r
1062 identity LOOP_BACK_TYPE_INTERNAL {
\r
1063 base LOOP_BACK_TYPE;
\r
1066 If the internal loopback test fails, the Data Terminal Equipment (DTE) is faulty (e.g. board has to be replaced)";
\r
1069 identity LOOP_BACK_TYPE_NOT_YET_DEFINED {
\r
1070 base LOOP_BACK_TYPE;
\r
1075 identity RX_SYNC_PREFERENCE_TYPE {
\r
1080 identity RX_SYNC_PREFERENCE_TYPE_AUTO_MULTIPORT_DEVICE {
\r
1081 base RX_SYNC_PREFERENCE_TYPE;
\r
1083 "Master/Slave relation is determined by auto-negotiation and this device has a preference for being Master";
\r
1086 identity RX_SYNC_PREFERENCE_TYPE_AUTO_SINGLE_PORT_DEVICE {
\r
1087 base RX_SYNC_PREFERENCE_TYPE;
\r
1089 "Master/Slave relation is determined by auto-negotiation and this device has a preference for being Slave";
\r
1092 identity RX_SYNC_PREFERENCE_TYPE_MANUAL_MASTER {
\r
1093 base RX_SYNC_PREFERENCE_TYPE;
\r
1095 "Master/Slave relation is determined by manual configuration and this device shall be Master";
\r
1098 identity RX_SYNC_PREFERENCE_TYPE_MANUAL_SLAVE {
\r
1099 base RX_SYNC_PREFERENCE_TYPE;
\r
1101 "Master/Slave relation is determined by manual configuration and this device shall be Slave";
\r
1104 identity RX_SYNC_PREFERENCE_TYPE_NOT_YET_DEFINED {
\r
1105 base RX_SYNC_PREFERENCE_TYPE;
\r
1110 identity RX_SYNC_ROLE_TYPE {
\r
1115 identity RX_SYNC_ROLE_TYPE_MASTER {
\r
1116 base RX_SYNC_ROLE_TYPE;
\r
1121 identity RX_SYNC_ROLE_TYPE_SLAVE {
\r
1122 base RX_SYNC_ROLE_TYPE;
\r
1127 identity RX_SYNC_ROLE_TYPE_FAULT {
\r
1128 base RX_SYNC_ROLE_TYPE;
\r
1133 identity RX_SYNC_ROLE_TYPE_NOT_YET_DEFINED {
\r
1134 base RX_SYNC_ROLE_TYPE;
\r
1139 identity MII_KIND_TYPE {
\r
1144 identity MII_KIND_TYPE_GBIC {
\r
1145 base MII_KIND_TYPE;
\r
1150 identity MII_KIND_TYPE_SOLDERED_CONNECTOR {
\r
1151 base MII_KIND_TYPE;
\r
1156 identity MII_KIND_TYPE_SFP_SFP_PLUS_SFP28 {
\r
1157 base MII_KIND_TYPE;
\r
1162 identity MII_KIND_TYPE_XBI_300_PIN {
\r
1163 base MII_KIND_TYPE;
\r
1168 identity MII_KIND_TYPE_XENPAK {
\r
1169 base MII_KIND_TYPE;
\r
1174 identity MII_KIND_TYPE_XFP {
\r
1175 base MII_KIND_TYPE;
\r
1180 identity MII_KIND_TYPE_XFP_E {
\r
1181 base MII_KIND_TYPE;
\r
1186 identity MII_KIND_TYPE_XPAK {
\r
1187 base MII_KIND_TYPE;
\r
1192 identity MII_KIND_TYPE_X2 {
\r
1193 base MII_KIND_TYPE;
\r
1198 identity MII_KIND_TYPE_DWDM_SFP_SFP_PLUS {
\r
1199 base MII_KIND_TYPE;
\r
1204 identity MII_KIND_TYPE_QSFP {
\r
1205 base MII_KIND_TYPE;
\r
1210 identity MII_KIND_TYPE_QSFP_PLUS {
\r
1211 base MII_KIND_TYPE;
\r
1216 identity MII_KIND_TYPE_CXP {
\r
1217 base MII_KIND_TYPE;
\r
1222 identity MII_KIND_TYPE_SHIELDED_MINI_MULTILANE_HD_4X {
\r
1223 base MII_KIND_TYPE;
\r
1228 identity MII_KIND_TYPE_SHIELDED_MINI_MULTILANE_HD__X {
\r
1229 base MII_KIND_TYPE;
\r
1234 identity MII_KIND_TYPE_QSFP28 {
\r
1235 base MII_KIND_TYPE;
\r
1240 identity MII_KIND_TYPE_CXP2 {
\r
1241 base MII_KIND_TYPE;
\r
1246 identity MII_KIND_TYPE_CDFP_STYLE1_STYLE2 {
\r
1247 base MII_KIND_TYPE;
\r
1252 identity MII_KIND_TYPE_SHIELDED_MINI_MULTILANE_HD_4X_FAN_OUT {
\r
1253 base MII_KIND_TYPE;
\r
1258 identity MII_KIND_TYPE_SHIELDED_MINI_MULTILANE_HD_8X_FAN_OUT {
\r
1259 base MII_KIND_TYPE;
\r
1264 identity MII_KIND_TYPE_CDFP_STYLE3 {
\r
1265 base MII_KIND_TYPE;
\r
1270 identity MII_KIND_TYPE_QSFP_MICRO {
\r
1271 base MII_KIND_TYPE;
\r
1276 identity MII_KIND_TYPE_QSFP_DD {
\r
1277 base MII_KIND_TYPE;
\r
1282 identity MII_KIND_TYPE_QSFP_PLUS_RATE_SELECT_V1 {
\r
1283 base MII_KIND_TYPE;
\r
1288 identity MII_KIND_TYPE_QSFP_PLUS_RATE_SELECT_V2 {
\r
1289 base MII_KIND_TYPE;
\r
1294 identity MII_KIND_TYPE_NOT_YET_DEFINED {
\r
1295 base MII_KIND_TYPE;
\r
1300 identity MDI_KIND_TYPE {
\r
1305 identity MDI_KIND_TYPE_SC {
\r
1306 base MDI_KIND_TYPE;
\r
1308 "Subscriber Connector";
\r
1311 identity MDI_KIND_TYPE_FIBRE_CHANNEL_STYLE_1 {
\r
1312 base MDI_KIND_TYPE;
\r
1314 "Copper connector";
\r
1317 identity MDI_KIND_TYPE_FIBRE_CHANNEL_STYLE_2 {
\r
1318 base MDI_KIND_TYPE;
\r
1320 "Copper connector";
\r
1323 identity MDI_KIND_TYPE_BNC_TNC {
\r
1324 base MDI_KIND_TYPE;
\r
1326 "Bayonet/Threaded Neill-Concelman";
\r
1329 identity MDI_KIND_TYPE_FC {
\r
1330 base MDI_KIND_TYPE;
\r
1332 "Fibre Channel coax headers";
\r
1335 identity MDI_KIND_TYPE_FIBER_JACK {
\r
1336 base MDI_KIND_TYPE;
\r
1341 identity MDI_KIND_TYPE_LC {
\r
1342 base MDI_KIND_TYPE;
\r
1344 "Lucent Connector";
\r
1347 identity MDI_KIND_TYPE_MT_RJ {
\r
1348 base MDI_KIND_TYPE;
\r
1350 "Mechanical Transfer - Registered Jack";
\r
1353 identity MDI_KIND_TYPE_MU {
\r
1354 base MDI_KIND_TYPE;
\r
1356 "Multiple Optical";
\r
1359 identity MDI_KIND_TYPE_SG {
\r
1360 base MDI_KIND_TYPE;
\r
1365 identity MDI_KIND_TYPE_OPTICAL_PIGTAIL {
\r
1366 base MDI_KIND_TYPE;
\r
1371 identity MDI_KIND_TYPE_MPO1x12 {
\r
1372 base MDI_KIND_TYPE;
\r
1374 "Multifiber Parallel Optic";
\r
1377 identity MDI_KIND_TYPE_MPO2x16 {
\r
1378 base MDI_KIND_TYPE;
\r
1380 "Multifiber Parallel Optic";
\r
1383 identity MDI_KIND_TYPE_HSSDC_II {
\r
1384 base MDI_KIND_TYPE;
\r
1386 "High Speed Serial Data Connector";
\r
1389 identity MDI_KIND_TYPE_COPPER_PIGTAIL {
\r
1390 base MDI_KIND_TYPE;
\r
1395 identity MDI_KIND_TYPE_RJ45 {
\r
1396 base MDI_KIND_TYPE;
\r
1398 "8P8C, according to Clause 3 and Figures 1 through 5 of IEC 60603-7";
\r
1401 identity MDI_KIND_TYPE_NO_SEPERABLE_CONNECTOR {
\r
1402 base MDI_KIND_TYPE;
\r
1407 identity MDI_KIND_TYPE_MXC2x16 {
\r
1408 base MDI_KIND_TYPE;
\r
1413 identity MDI_KIND_TYPE_ST {
\r
1414 base MDI_KIND_TYPE;
\r
1416 "according to IEC 60874-10:1992, also often called BFOC/2.5";
\r
1419 identity MDI_KIND_TYPE_NOT_YET_DEFINED {
\r
1420 base MDI_KIND_TYPE;
\r
1425 identity MEDIUM_KIND_TYPE {
\r
1430 identity MEDIUM_KIND_TYPE_TP_CAT3 {
\r
1431 base MEDIUM_KIND_TYPE;
\r
1436 identity MEDIUM_KIND_TYPE_TP_CAT5 {
\r
1437 base MEDIUM_KIND_TYPE;
\r
1442 identity MEDIUM_KIND_TYPE_TP_CAT6 {
\r
1443 base MEDIUM_KIND_TYPE;
\r
1448 identity MEDIUM_KIND_TYPE_TP_CAT8 {
\r
1449 base MEDIUM_KIND_TYPE;
\r
1454 identity MEDIUM_KIND_TYPE_SINGLE_MODE {
\r
1455 base MEDIUM_KIND_TYPE;
\r
1460 identity MEDIUM_KIND_TYPE_MULTI_MODE {
\r
1461 base MEDIUM_KIND_TYPE;
\r
1466 identity MEDIUM_KIND_TYPE_NOT_YET_DEFINED {
\r
1467 base MEDIUM_KIND_TYPE;
\r
1472 identity DUPLEX_TYPE {
\r
1477 identity DUPLEX_TYPE_HALF_DUPLEX {
\r
1483 identity DUPLEX_TYPE_FULL_DUPLEX {
\r
1489 identity DUPLEX_TYPE_NOT_YET_DEFINED {
\r
1495 identity SIGNAL_ORDERING_KIND_TYPE {
\r
1500 identity SIGNAL_ORDERING_KIND_TYPE_MDI {
\r
1501 base SIGNAL_ORDERING_KIND_TYPE;
\r
1506 identity SIGNAL_ORDERING_KIND_TYPE_MDI_X {
\r
1507 base SIGNAL_ORDERING_KIND_TYPE;
\r
1512 identity SIGNAL_ORDERING_KIND_TYPE_NOT_YET_DEFINED {
\r
1513 base SIGNAL_ORDERING_KIND_TYPE;
\r
1518 identity PMD_NEGOTIATION_STATE_TYPE {
\r
1523 identity PMD_NEGOTIATION_STATE_TYPE_NONE {
\r
1524 base PMD_NEGOTIATION_STATE_TYPE;
\r
1526 "Device does not support auto negotiation";
\r
1529 identity PMD_NEGOTIATION_STATE_TYPE_DISABLED {
\r
1530 base PMD_NEGOTIATION_STATE_TYPE;
\r
1532 "Auto negotiation is disabled.";
\r
1535 identity PMD_NEGOTIATION_STATE_TYPE_ENABLED {
\r
1536 base PMD_NEGOTIATION_STATE_TYPE;
\r
1538 "Auto negotiation is enabled, but currently nothing is connected";
\r
1541 identity PMD_NEGOTIATION_STATE_TYPE_IN_PROGRESS {
\r
1542 base PMD_NEGOTIATION_STATE_TYPE;
\r
1544 "The auto-negotiation protocol is running and negotiation is currently in-progress";
\r
1547 identity PMD_NEGOTIATION_STATE_TYPE_COMPLETE {
\r
1548 base PMD_NEGOTIATION_STATE_TYPE;
\r
1550 "The auto-negotation protocol has completed successfully";
\r
1553 identity PMD_NEGOTIATION_STATE_TYPE_FAILED {
\r
1554 base PMD_NEGOTIATION_STATE_TYPE;
\r
1556 "The auto-negotation protocol has failed";
\r
1559 identity PMD_NEGOTIATION_STATE_TYPE_NOT_YET_DEFINED {
\r
1560 base PMD_NEGOTIATION_STATE_TYPE;
\r
1562 "Device supports autonegotiation, but state is currently unknown, e.g. because device just booted";
\r
1565 identity GRANULARITY_PERIOD_TYPE {
\r
1570 identity GRANULARITY_PERIOD_TYPE_UNKNOWN {
\r
1571 base GRANULARITY_PERIOD_TYPE;
\r
1576 identity GRANULARITY_PERIOD_TYPE_PERIOD-15-MIN {
\r
1577 base GRANULARITY_PERIOD_TYPE;
\r
1582 identity GRANULARITY_PERIOD_TYPE_PERIOD-24-HOURS {
\r
1583 base GRANULARITY_PERIOD_TYPE;
\r
1588 identity GRANULARITY_PERIOD_TYPE_NOT_YET_DEFINED {
\r
1589 base GRANULARITY_PERIOD_TYPE;
\r
1594 identity SEVERITY_TYPE {
\r
1599 identity SEVERITY_TYPE_NON_ALARMED {
\r
1600 base SEVERITY_TYPE;
\r
1605 identity SEVERITY_TYPE_WARNING {
\r
1606 base SEVERITY_TYPE;
\r
1611 identity SEVERITY_TYPE_MINOR {
\r
1612 base SEVERITY_TYPE;
\r
1617 identity SEVERITY_TYPE_MAJOR {
\r
1618 base SEVERITY_TYPE;
\r
1623 identity SEVERITY_TYPE_CRITICAL {
\r
1624 base SEVERITY_TYPE;
\r
1629 identity SEVERITY_TYPE_NOT_YET_DEFINED {
\r
1630 base SEVERITY_TYPE;
\r
1635 identity INTERFACE_STATUS_TYPE {
\r
1640 identity INTERFACE_STATUS_TYPE_UP {
\r
1641 base INTERFACE_STATUS_TYPE;
\r
1643 "Ready to pass packets.";
\r
1646 identity INTERFACE_STATUS_TYPE_DOWN {
\r
1647 base INTERFACE_STATUS_TYPE;
\r
1649 "The interface does not pass any packets.";
\r
1652 identity INTERFACE_STATUS_TYPE_TESTING {
\r
1653 base INTERFACE_STATUS_TYPE;
\r
1655 "In some test mode. No operational packets can be passed.";
\r
1658 identity INTERFACE_STATUS_TYPE_UNKNOWN {
\r
1659 base INTERFACE_STATUS_TYPE;
\r
1661 "Status cannot be determined for some reason.";
\r
1664 identity INTERFACE_STATUS_TYPE_DORMANT {
\r
1665 base INTERFACE_STATUS_TYPE;
\r
1667 "Waiting for some external event.";
\r
1670 identity INTERFACE_STATUS_TYPE_NOT_PRESENT {
\r
1671 base INTERFACE_STATUS_TYPE;
\r
1673 "Some component (typically hardware) is missing.";
\r
1676 identity INTERFACE_STATUS_TYPE_LOWER_LAYER_DOWN {
\r
1677 base INTERFACE_STATUS_TYPE;
\r
1679 "Down due to state of lower-layer interface(s).";
\r
1682 identity INTERFACE_STATUS_TYPE_ADMIN_DOWN {
\r
1683 base INTERFACE_STATUS_TYPE;
\r
1685 "Down due to configuration.";
\r
1688 identity INTERFACE_STATUS_TYPE_NOT_YET_DEFINED {
\r
1689 base INTERFACE_STATUS_TYPE;
\r
1694 /****************************************
\r
1695 * package super-types
\r
1696 **************************************/
\r
1698 typedef granularity-period-type {
\r
1699 type identityref {
\r
1700 base GRANULARITY_PERIOD_TYPE;
\r
1703 "The enumeration with the options for granularity period of the performance data.";
\r
1706 typedef severity-type {
\r
1707 type identityref {
\r
1708 base SEVERITY_TYPE;
\r
1711 "According to ITU-T M.3160";
\r
1714 typedef interface-status-type {
\r
1715 type identityref {
\r
1716 base INTERFACE_STATUS_TYPE;
\r
1719 "Current Interface Status";
\r
1722 grouping problem-kind-severity-type {
\r
1723 leaf problem-kind-name {
\r
1726 "Name of the alarm according to supportedAlarmList";
\r
1728 leaf problem-kind-severity {
\r
1729 type severity-type;
\r
1730 default "SEVERITY_TYPE_NOT_YET_DEFINED";
\r
1732 "Severity of this type of alarm.";
\r
1738 grouping wire-interface-current-problem-type {
\r
1739 leaf problem-name {
\r
1741 default "Problem name not specified.";
\r
1744 "Name of the alarm according to supportedAlarmList attribute in MauType datatype";
\r
1746 uses current-problem;
\r
1751 grouping wire-interface-performance-type {
\r
1758 "Number of errored seconds according to 802.3 30.8.1.1.13 aLineESs";
\r
1766 "Number of severely errored seconds according to 802.3 30.8.1.1.12 aLineSESs";
\r
1768 leaf symbol-error-during-carrier {
\r
1774 "Source: 802.3 according to 30.3.2.1.5 aSymbolErrorDuringCarrier. Number of times when valid carrier was present and an invalid data symbol occured.";
\r
1776 leaf low-power-idle-transmitter-ms {
\r
1782 "Source: 802.3 similar to 30.3.2.1.8 aTransmitLPIMicroseconds. Number of milliseconds (original counter expresses microseconds), during which the transmitter was in power save mode";
\r
1784 leaf low-power-idle-receiver-ms {
\r
1790 "Source: 802.3 similar to 30.3.2.1.9 aReceiveLPIMicroseconds. Number of milliseconds (original counter expresses microseconds), during which the receiver was in power save mode";
\r
1796 grouping wire-interface-current-performance-type {
\r
1797 container performance-data {
\r
1799 uses wire-interface-performance-type;
\r
1803 uses current-performance;
\r
1805 "Turns performance information into current performance information by inheriting from OTN_CurrentData.";
\r
1808 grouping wire-interface-historical-performance-type {
\r
1809 container performance-data {
\r
1811 uses wire-interface-performance-type;
\r
1815 uses historical-performance;
\r
1817 "Turns performance information into historical performance information by inheriting from OTN_HistoryData.";
\r
Code Review / ccsdk / features.git / blob