Connectivity
The Open ROADM device YANG model contains a number of lists and an RPC for configuring and retrieving connectivity information. This section describes the extent of support for this connectivity modeling on ACX6160.
internal-link – This list is not supported. All internal connectivity information is provided by the connection-map.
physical-link – This list is not supported. There are no links required to be setup between circuit packs on the ACX6160, thus there is nothing to configure for this list.
external-link – This list is supported. You can provision any data you wish to record on links between the ACX6160 and external devices.
connection-map – This list is supported. The connection-map list reports the traffic path connections between ACX6160 transponder Client and Line ports, identifying which Client and Line ports are paired together to provide 100 gigabit transponder units.
get-connection-port-trail – This RPC is not supported, because there are no internal or physical links required on ACX6160, the connection port trail is trivial and thus there is no need for this RPC. You can reference all internal connectivity information from the connection-map.
ACX6160 Client to Line Port Fixed Mappings
Consistent with the Open ROADM connectivity model, there is a fixed linkage between Client and Line ports that is reported by the read-only connection-map list from the Open ROADM YANG model.. The ACX6160 supports the fixed port mapping described in Table 1.
Although there are eight QSFP28 Client ports, only four of these ports, along with four Line ports are reported in the connection-map. These are the only ports that are available for use as Open ROADM transponder configurations.
Table 1: ACX6160 Client to Line Port Fixed Mapping
Client Side Ports Labeled: 0/0 - 0/7 Client ports: 0/0/[0-7] | Line Side Port Labeled 1/0-1/3 Line Ports: 0/1/[0-3] |
|---|---|
Client port: 0/0/0 | Line port: 0/1/0 |
Client port: 0/0/1 Note: Not used in this release. | |
Client port: 0/0/2 | Line port: 0/1/1 |
Client port: 0/0/3 Note: Not used in this release. | |
Client port: 0/0/4 | Line port: 0/1/2 |
Client port: 0/0/5 Note: Not used in this release. | |
Client port: 0/0/6 | Line port: 0/1/3 |
Client port: 0/0/7 Note: Not used in this release. | |
Open ROADM Connectivity YANG Model Support
The columns in the Table 2 are defined as:
YANG node — The node from the Open ROADM YANG model.
Access — Access properties of the node. Can be:
rw — read/write
ro — read-only
x — RPC function
n — notification
Supported — Indicates ACX6160 support for the node.
Yes — ACX6160 supports the node
No — ACX6160 does not support the node
N/A — Node is not applicable to transponder device
Supported Values — Describes the range of supported values on ACX6160.
Table 2 describes ACX6160 compliance with the connectivity-related lists of the Open ROADM YANG model. The location within the Open ROADM YANG model of the YANG nodes listed in the table is /org-openroadm-device.
Table 2: Open ROADM Device Connectivity YANG Model Support
YANG Node | Access | Supported | Supported Values |
|---|---|---|---|
internal-link list | ro | no | Not supported |
physical-link list | rw | no | Not supported |
external-link list | rw | yes | User-specified string |
- external-link-name | |||
- source
| rw | yes | User-specified string |
- destination
| rw | yes | User-specified string |
connection-map list | ro | yes | Returns fixed mapping of Client to Line ports. |
- connection-map-number | ro | yes | Unsigned integer key into this table. This key is generated by the ACX6160. |
- source
| ro | yes | The source container identifies the Client circuit-pack and port for this connection-map list entry. |
- destination
| ro | yes | The destination container identifies the Line circuit-pack and port for this connection-map list entry. |