"OpenROADM.org";
description
"YANG definitions of ROADM device
-
- Copyright of the Members of the Open ROADM MSA Agreement dated (c) 2016,
+
+ Copyright of the Members of the Open ROADM MSA Agreement dated (c) 2016,
AT&T Intellectual Property. All other rights reserved.
-
- Redistribution and use in source and binary forms, with or without modification,
+
+ Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
-
- * Redistributions of source code must retain the above copyright notice, this
+
+ * Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
- * Redistributions in binary form must reproduce the above copyright notice,
- this list of conditions and the following disclaimer in the documentation and/or
+ * Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation and/or
other materials provided with the distribution.
- * Neither the Members of the Open ROADM MSA Agreement nor the names of its
- contributors may be used to endorse or promote products derived from this software
+ * Neither the Members of the Open ROADM MSA Agreement nor the names of its
+ contributors may be used to endorse or promote products derived from this software
without specific prior written permission.
-
- THIS SOFTWARE IS PROVIDED BY THE MEMBERS OF THE OPEN ROADM MSA AGREEMENT ''AS IS''
- AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
- WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
- IN NO EVENT THE MEMBERS OF THE OPEN ROADM MSA AGREEMENT BE LIABLE FOR ANY DIRECT,
- INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
- NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA,
- OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
- WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
- ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
+
+ THIS SOFTWARE IS PROVIDED BY THE MEMBERS OF THE OPEN ROADM MSA AGREEMENT ''AS IS''
+ AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+ WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+ IN NO EVENT THE MEMBERS OF THE OPEN ROADM MSA AGREEMENT BE LIABLE FOR ANY DIRECT,
+ INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+ NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA,
+ OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
+ WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
-
- Also contains code components extracted from IETF netconf. These code components
+
+ Also contains code components extracted from IETF netconf. These code components
are copyrighted and licensed as follows:
-
- Copyright (c) 2016 IETF Trust and the persons identified as the document authors.
- All rights reserved.
-
- This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating
- to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of
- publication of this document. Please review these documents carefully, as they
- describe your rights and restrictions with respect to this document. Code Components
+
+ Copyright (c) 2016 IETF Trust and the persons identified as the document authors.
+ All rights reserved.
+
+ This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating
+ to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of
+ publication of this document. Please review these documents carefully, as they
+ describe your rights and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text as described in
- Section 4.e of the Trust Legal Provisions and are provided without warranty as
+ Section 4.e of the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.";
revision 2017-12-15 {
leaf node-number {
type uint32;
description
- "Number assigned to a ROADM node at a
+ "Number assigned to a ROADM node at a
given office";
}
leaf node-type {
}
config false;
description
- "amp-number of amp module that is functionally associated to the amplifier
+ "amp-number of amp module that is functionally associated to the amplifier
in the opposite direction";
}
leaf ila-direction-label {
grouping external-links {
description
- "YANG definitions for external links..
+ "YANG definitions for external links..
- physical links between ROADMs and between the ROADMs and XPonders, which can be added and removed manually.";
list external-link {
key "external-link-name";
type string;
config true;
description
- "Complements ports identification. Used notably in case of bidirectional ports,
+ "Complements ports identification. Used notably in case of bidirectional ports,
and/or in multi-degree amplifier nodes. Allows associating one of the directions
specified in ila-direction-label. Shall be consistent with ila-direction-label";
}
type string;
config true;
description
- "Complements ports identification. Used notably in case of bidirectional ports,
+ "Complements ports identification. Used notably in case of bidirectional ports,
and/or in multi-degree amplifier nodes. Allows associating one of the directions
specified in ila-direction-label. Shall be consistent with ila-direction-label";
}
config true;
mandatory true;
description
- "allows identifying ports associated with logical amp :
+ "allows identifying ports associated with logical amp :
TX for OSC circuit-pack IN RX for OSC circuit-pack OUT";
}
uses port-name {
type string;
config true;
description
- "allows identifying associated logical amp port in which OTDR is launched:
+ "allows identifying associated logical amp port in which OTDR is launched:
corresponds to rx-instance-port-direction-label of corresponding amplifier line-port";
}
uses port-name {
type uint32;
config false;
description
- "Switch fabric interconnect bandwidth unit rate in bits per second.
+ "Switch fabric interconnect bandwidth unit rate in bits per second.
Represents granularity of switch fabric";
}
leaf interconnect-bandwidth {
type uint32;
config false;
description
- "Total interconnect bandwidth for a non-blocking element expressed as
+ "Total interconnect bandwidth for a non-blocking element expressed as
number of inter-connect-bandwidth units";
}
list port-list {
"Collects all log data for debugging and place it in a location accessible via ftp/sftp.
This model assumes ASYNC operation, i.e. the command will return after the device accepts the command,
A create-tech-info-notification will be send out later for the result of the operation.
- The log-file is cleared at the start of every create-tech-info operation in order to ensure
- the up-to-date logs are collected. If a vendor does not support concurrent log collection, the second
+ The log-file is cleared at the start of every create-tech-info operation in order to ensure
+ the up-to-date logs are collected. If a vendor does not support concurrent log collection, the second
create-tech-info command will be rejected.";
input {
leaf shelf-id {
path "/org-openroadm-device/shelves/shelf-name";
}
description
- "This optional field is used to specify the shelf for log collection.
+ "This optional field is used to specify the shelf for log collection.
When this filed is not provided, it is expected to collect logs for the whole node.
Vendor should reject the command if the whole node log collection is not supported.";
}
description
"The Notification that a resource has been added, modified or removed.
This notification can be triggered by changes in configuration and operational data.
- It shall contain the changed field pointed by the xpath.
+ It shall contain the changed field pointed by the xpath.
Typically it is not intended for frequently changing volatile data e.g. PM, power levels";
leaf change-time {
type ietf-yang-types:date-and-time;
Code Review / transportpce.git / blobdiff