Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Interfaces

 

This section describes how to configure Client and Line port interfaces on the ACX6160 through your Open ROADM controller. It also describes the Open ROADM YANG model support for each interface type available on the ACX6160 Client and Line ports.

Understanding the Hierarchical Relationship Between Ports and Interfaces

Tip

It’s important to understand, in Open ROADM, Ports and Interfaces are two distinct entities, which have a hierarchical relationship to each other.

  • Ports are the physical ports on the device, the Client and Line ports on the ACX6160 front panel. Client ports are labeled 0/0 through 0/7. Line ports (labeled 1/0 through 1/3.

  • Interfaces are configured on a supporting physical port (or another supporting interface).

When configuring a transponding circuit, the required interfaces need to be configured in the hierarchical order, beginning with the interface directly supported by the port, then working upwards in the interface stack. For each interface configured, the supporting circuit pack, supporting port and supporting interface must be provisioned appropriately to reflect the hierarchical relationships. Additional details are provided in Table 1 below.

Client and Line ports on the ACX6160 use pluggable optics. All Client ports use pluggable QSFP28 transceivers that are 100 Gbps. All Line ports use pluggable CFP2-DCO transceivers that are 100 Gbps and support HGFEC.

Table 1 describes the various interfaces available for the ACX6160 Client and Line ports and the Management port, which is (1000BASE-T). The ACX6160 supports the Open ROADM model for interface configuration and status data. You can provision and monitor the all of these interface types on the ACX6160.

Table 1: ACX6160 Supported Interface Types

Interfaces Available On Transponder Client Port

On Transporter Line Port

On Management Port

100 Gigabit Ethernet interface

See, see Table 3

Optical Channel interface

See, see Table 4

Ethernet interface

OTN OTU4 interface

See, Table 6

OTN OTU4 interface

See, Table 6

 

OTN OTU4 (100 Gbps) interface

See, Table 5

An OTU4 interface, with an ODU4 interface supported by the OTU4 interface.

OTN ODU4 interface

See, Table 5

 

Configuring Client Port Interfaces

The ACX6160 has eight Client ports (labeled 0/0 through 0/7 on the front panel) that support QSFP28 transceivers. These transceivers provide a speed of up to 100 Gbps, through four 25-Gbps channels. By default, Client ports are configured as 100-Gigabit Ethernet ports.

On Client ports, the interfaces that are provisioned depend on the transponding application required. To configure a 100 Gigabit Ethernet transponding circuit, an ethernet interface is provisioned on the Client port. To configure a OTU4 transponding circuit, both an OTU interface and an ODU interface are configured on the Client port. In the case of a 100 Gigabit Ethernet Client, the Ethernet interface is provisioned to be directly supported by the Client port. For an OTU4 Client, the OTU interface is supported by the port and the ODU interface is supported by the OTU interface.

As an example, let’s look at what it would take to configure a 100 Gigabit Ethernet transponding circuit on the Client port of the ACX6160, again, looking at Table 1:

  1. Configure the Shelf

  2. Configure the FPC circuit-pack

  3. Configure the PIC circuit-pack

  4. Configure the XCVR circuit-pack (pluggable optics)

  5. Configure the port on the XCVR

You must perform these steps in the order shown using your Open ROADM controller.

Again, referring to Table 1, let’s look at what steps you need to take to configure an OTU4 Client:

  1. Configure the port on the XCVR

  2. Configure the XCVR circuit-pack (pluggable optics)

  3. Configure the PIC circuit-pack

  4. Configure the FPC circuit-pack

  5. Configure the Shelf

In addition you’ll need to configure:

  • A single 100GE interface supported by the provisioned port

  • A single OTU4 interface supported by the provisioned port

  • A single ODU4 interface supported by the OTU4 interface.

Configuring Line Port Interfaces

The ACX6160 has four Line CFP2 ports (labeled 1/0 through 1/3 on the front panel) that support C form-factor pluggable type 2 transceivers.

To configure a Line port”

  1. Configure the port on the XCVR

  2. Configure the XCVR circuit-pack (pluggable optics)

  3. Configure the PIC circuit-pack

  4. Configure the FPC circuit-pack

  5. Configure the Shelf

These Line interfaces have a hierarchical relationship, with the optical channel interface (OCH) directly supported by the Line port, the OTU interface supported by the optical channel interface, and the ODU interface supported by the OTU interface.

These three interfaces are configured together on the Line side. It is the only arrangement of interfaces that is configured on the Line side.

On Line ports, you must provision all three interfaces:

  1. A single OCH interface supported by the provisioned port

  2. A single OTU4 interface supported by the OCH interface

  3. A single ODU4 interface supported by the OTU4 interface

You must provision these Line interfaces in the order shown.

Open ROADM Device Interface YANG Model Support

Table 2 describes ACX6160 compliance with the content of the Open ROADM device interface YANG model that is common to all interface types. The location within the Open ROADM YANG model of the nodes listed in the table is /org-openroadm-device/interface.

The columns in 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 content of the Open ROADM interface YANG model that is common to all interface types. The location within the Open ROADM YANG model of the nodes listed in the table is /org-openroadm-device/interface.

Table 2: Open ROADM Device Interface YANG Model Support

YANG Node

Access

Supported

Supported Values

name

rw

yes

User-specified string.

description

rw

yes

User-specified string.

type

rw

yes

  • opticalChannel — for optical-channel interfaces

  • otnOtu — for OTU4 Line and Client interfaces

  • otnOdu — for ODU4 Line and Client interfaces

  • ethernetCsmacd — for Client 100 Gigabit Ethernet interfaces and the management port interface

administrative-state

rw

yes

  • inService — normal service enabled, alarm reporting enabled

  • outOfService — service disabled, alarm reporting disabled

  • maintenance — normal service enabled, alarm reporting disabled

operational-state

ro

yes

  • inService — interface is able to perform in normal function

  • outOfService — interface is unable to perform its normal function

  • degraded — ability of interface to perform its normal function is degraded

circuit-id

rw

yes

User-specified string.

supporting-interface

rw

yes

If interface type is otnOdu, this field must be set to name field of the supporting interface, which must be type otnOtu.

If interface type is otnOtu on the Line-side port, this field must be set to name field of the supporting interface, which must be type opticalChannel.

For all other interfaces, this attribute must not be configured.

supporting-circuit-pack-name

rw

yes

If supporting-interface field is not specified, this attribute must be configured as the name of the interface’s supporting circuit-pack.

supporting-port

rw

yes

If supporting-interface field is not specified, this attribute must be configured as the name of the interface’s supporting port.

Open ROADM Device Ethernet Interface YANG Model Support

Table 3 describes ACX6160 compliance with the content of the augmentation for ethernet interfaces to the Open ROADM interface YANG model. The location within the Open ROADM YANG model of the nodes listed in the table is /org-openroadm-device/interface/ethernet.

Note

In the column on supported values, the information that applies to 100 Gigabit Ethernet client interfaces is prefixed by “100GE” and the information that applies to the management port interface is prefixed by “Mgmt IF”.

Table 3: Open ROADM Device Ethernet Interface YANG Model Support

YANG Node

Access

Supported

Supported Values

ethernet

rw

yes

- speed

rw

yes

  • 100GE – 100000

  • Mgmt IF – 10, 100, 1000, 10000

- fec

rw

yes

  • 100GE – off

  • Mgmt IF - off

- duplex

rw

yes

  • 100GE – full

  • Mgmt IF – half, full

- mtu

rw

no

  • 100GE – not supported

  • Mgmt IF – 1518 through 9000

- auto-negotiation

rw

no

  • 100GE – not supported

  • Mgmt IF – enabled, disabled

- curr-speed

ro

yes

  • 100GE – 100000

  • Mgmt IF – 10, 100, 1000, 10000

- curr-duplex

ro

yes

  • 100GE – full

  • Mgmt IF – half, full

Open ROADM Device Optical-Channel Interface YANG Model Support

Table 4 describes ACX6160 compliance with the content of the augmentation for optical-channel interfaces to the Open ROADM interface YANG model. The location within the Open ROADM YANG model of the nodes listed in the table is /org-openroadm-device/interface/och.

Table 4: Open ROADM Device Optical-Channel Interface YANG Model Support

YANG Node

Access

Supported

Supported Values

Och

rw

yes

 

- rate

rw

yes

R100G

- frequency

rw

yes

ITU 50 GHz grid frequency within range 191.35 to 196.10

- width

ro

yes

50.00000 (for 50 GHz spacing)

- modulation-format

rw

yes

qpsk

- transmit-power

rw

yes

Range: -35.0 through +10.0

(power in dBm)

Open ROADM Device OTN ODU Interface YANG Model Support

Table 5 describes ACX6160 compliance with the content of the augmentation for OTN ODU interfaces to the Open ROADM interface YANG model. The location within the Open ROADM YANG model of the nodes listed in the table is /org-openroadm-device/interface/odu.

Where the level of support differs between line-port and client-port ODU4 interfaces, the port-specific support is identified by “ODU4 line interface” and “ODU4 client interface” respectively.

Note

Descriptions for the maint-testsignal container within the odu container are excluded from this section and discussed in a later section of this document.

Table 5: Open ROADM Device OTN ODU Interface YANG Model Support

YANG Node

Access

Supported

Supported Values

Odu

rw

yes

Container

- rate

rw

yes

ODU4

- odu-function

rw

no

Not supported

- monitoring-mode

rw

yes

  • For Line-side ODU interface with 100GE Client interface – terminated

  • For Line-side ODU interface with OTU4 Client interface – monitored

  • For Client-side ODU interface - monitored

- no-oam-function

ro

yes

This node is always absent.

- proactive-delay-measurement-enabled

rw

yes

False.

- parent-odu-allocation

rw

no

Not supported.

- tx-sapi

rw

yes

User-specific string, up to 15 characters

- tx-dapi

rw

yes

User-specific string, up to 15 characters

- tx-operator

rw

yes

User-specific string, up to 32 characters

- accepted-sapi

ro

yes

User-specific string, up to 15 characters

- accepted-dapi

ro

yes

User-specific string, up to 15 characters

- accepted-operator

ro

yes

User-specific string, up to 32 characters

- expected-sapi

rw

yes

User-specific string, up to 15 characters

- expected-dapi

rw

yes

User-specific string, up to 15 characters

- tim-act-enabled

rw

yes

True/false.

- tim-detect-mode

rw

yes

Disabled, SAPI, DAPI. SAPI-and-DAPI

- degm-intervals

rw

yes

Range: 2 through 10

- degthr-percentage

rw

yes

Range: 1 through 10000

- tcm

rw

no

Not supported

- opu

rw

yes

Container

-- payload-type

rw

yes

  • For Line-side ODU interface with 100GE Client interface – 07

  • For Line-side ODU interface with OTU4 Client interface – not supported

  • For Client-side ODU interface – not supported

-- rx-payload-type

ro

no

Not supported

-- exp-payload-type

rw

yes

  • For Line-side ODU interface with 100GE Client interface – 07

  • For other ODU interfaces, range: 00 through FF

-- payload-interface

rw

yes

User-specified string

-- msi

rw

no

Not supported

Open ROADM Device OTN OTU4 Interface YANG Model Support

Table 6 describes ACX6160 compliance with the content of the augmentation for OTN OTU interfaces to the Open ROADM interface YANG model. The location within the Open ROADM YANG model of the nodes listed in the table is /org-openroadm-device/interface/otu.

Where the level of support differs between Line-port and Client-port OTU4 interfaces, the port-specific support is identified by “OTU4 Line interface” and “OTU4 Client interface” respectively.

Note

Descriptions for the maint-loopback container within the otu container are excluded from this section and discussed in a later section of this document.

Table 6: Open ROADM Device OTN OTU4 Interface YANG Model Support

YANG Node

Access

Supported

Supported Values

Otu

rw

yes

Container

- rate

rw

yes

OTU4

- fec

rw

yes

OTU4 Line interface – scfec

OTU4 Client interface – rsfec, off

- tx-sapi

rw

yes

User-specific string, up to 15 characters

- tx-dapi

rw

yes

User-specific string, up to 15 characters

- tx-operator

rw

yes

User-specific string, up to 32 characters

- accepted-sapi

ro

yes

User-specific string, up to 15 characters

- accepted-dapi

ro

yes

User-specific string, up to 15 characters

- accepted-operator

ro

yes

User-specific string, up to 32 characters

- expected-sapi

rw

yes

User-specific string, up to 15 characters

- expected-dapi

rw

yes

User-specific string, up to 15 characters

- tim-act-enabled

rw

yes

True, false

- tim-detect-mode

rw

yes

Disabled, SAPI, DAPI. SAPI-and-DAPI

- degm-intervals

rw

yes

Range: 2 through 10

- degthr-percentage

rw

yes

Range: 1 through 10000