This document describes the OpenConfig configurations for Optical-Channel and Terminal Device and states the attributes supported by OcNOS versions 5.0 and 5.1 and the limitations which apply for some of the paths.

This section used to be dedicated to Optical Transport Network (OTN), but with additional OpenZR/ZR+ support in OcNOS release 6.5.0, this section applies to all platforms which support similar optical features.

The OpenConfig feature is disabled by default and must be enabled using the following CLI command on the OcNOS shell.

Or using the equivalent NETCONF RPC:

Once enabled, the user is still able to get data in OcNOS format by specifying the required namespace:

This generates the following RPC:

To get OpenConfig data, the corresponding namespace must be given:

If OpenConfig is enabled and no filter is provided, all the supported OpenConfig models are retrieved in OpenConfig format. The OcNOS models for which no translation is supported will be retrieved in OcNOS format.

It is mandatory to enable the module previously for all other configurations.

This XML configuration snippet is used to enable coherent modules (slot 6 and slot 3).

Here is a sample OpenConfig NetConf Payload to enable coherent modules.

The below CLI command is used to enable coherent modules.

Here is a sample OcNOS NetConf Payload to enable coherent modules.

This filter for the Get operation results in the Get OpenConfig Return output shown below

This validation response provides information on the configuration and runtime for enabling coherent modules.

Host interface Loopback-type and Network interface prbs-type are translated to logical channels. The correlation is shown in the image below:

The optical channel contains the following:

The network interface is translated to an Optical channel and has the same value as a coherent module slot. (i.e. slot 6/ network interface 0→ och-6/0)

The logical channel contains the following:

The network interface is translated to logical channels. The index is represented by a 8 digits hexa number, where:

To avoid ambiguity, 1 is added to the desired interface.

For example:

Slot 6 host-interface 1 is represented by 0x060002. In OpenConfig, this number is translated to decimal 393218.

Slot 4, network-interface 0 is represented by 0x040100. In OpenConfig, this number is translated to decimal 262400.

Both optical-channel and logical-channel are mapped to /terminal-device/coherent-module/network-interfaces/network-interface on OcNOS. Hence, some specific information about configuration and unconfiguration are necessary.

Here is the mapping:

When the user creates optical-channel or logical-channel for the first time, it already creates the structure of /terminal-device/coherent-module/network-interfaces/interface/.

When the user wants to delete the entire component OCH or logical-channels/channel, it tries to delete /terminal-device/coherent-module/network-interfaces/interface/. So it is important to delete only one of them. It is recommended to delete network-interfaces through component OCH.

Examples:

In OcNOS, there is a restriction to delete the network-interfaces/interface, that it must be empty and not have any configuration under it. So, if the user wants to delete on that level, the other configurations must be deleted one by one.

This configuration is used to configure loopback type on the host interface.

The two possible values are: FACILITY (shallow in Netconf mode) and TERMINAL (deep in Netconf mode).

Configure slot 6, Host-interface 1 loopback -type to shallow.

Here is a sample OpenConfig NetConf Payload to configure loopback type on host interface.

The below CLI command is used to configure loopback type on host interface.

Here is a sample OcNOS NetConf Payload to configure loopback type on host interface.

This filter for the Get operation results in the Get OpenConfig Return output shown below.

This validation response provides information on the configuration and runtime for configuring loopback type on host interface.

Use the delete operation remove this configuration, as shown below:

This configuration is used to configure loopback type on the network interface.

The two possible values are: FACILITY (shallow in NetConf mode) and TERMINAL (deep in NetConf mode).

Configuration of deep mode at slot 6, Network interface 0, loopback-type to deep.

Here is a sample OpenConfig NetConf Payload to configure loopback type on the network interface.

The below CLI command is used to configure loopback type on the network interface.

Here is a sample OcNOS NetConf Payload to configure loopback type on the network interface.

This filter for the Get operation results in the Get OpenConfig Return output shown below

Use the delete operation to remove this configuration, as shown below:

This configuration is used to disable coherent module 6.

Here is a sample NetConf Payload to disable coherent module 6.

The below CLI command is used to disable coherent module 6

Here is a sample NetConf Payload to disable coherent module 6.

This filter for the Get operation results in the Get OpenConfig Return output shown below.

This validation response provides information on the configuration and runtime for disabling coherent module 6.

This XML configuration snippet is used to select the operational modes.

Each mode configures specific modulation-format, fec-mode, speed and grid-spacing.

Configure operational-mode 6 at slot 6, interface 0.

Here is a sample OpenCOnfig NetConf Payload to select the operational modes.

The below CLI command is used to select the operational modes.

Here is a sample OcNOS NetConf Payload to select the operational modes.

This filter for the Get operation results in the Get OpenConfig Return output shown below.

This validation response provides information on the configuration and runtime for selecting the operational modes.

Use the delete operation to remove this configuration, as shown below:

The range of acceptable values is 1-6.

This XML configuration snippet is used to disable the transmission of data on a network interface.

Disable transmission of slot 6, network interface 0.

Here is a sample OpenConfig NetConf Payload to disable the transmission of data on a network interface.

The below CLI command is used to disable the transmission of data on a network interface.

Here is a sample OcNOS NetConf Payload to disable the transmission of data on a network interface.

This filter for the Get operation results in the Get OpenConfig Return output shown below.

This validation response provides information on the configuration and runtime for disabling the transmission of data on a network interface.

Use the delete operation to remove this configuration, as shown below:

This XML configuration snippet is used to set the laser frequency for a network interface in Hz, THz, GHz, and MHz.

Configure the frequency 196100GHz at slot 6 network interface 0.

Here is a sample OpenConfig NetConf Payload to set the laser frequency for a network interface in Hz, THz, GHz, and MHz.

Here is a sample CLI command used to set the laser frequency for a network interface.

Here is a sample OcNOS NetConf Payload to set the laser frequency for a network interface.

This filter for the Get operation results in the Get OpenConfig Return output shown below.

This validation response provides information on the configuration and runtime for setting the laser frequency for a network interface.

Use the delete operation to remove this configuration, as shown below:

The permitted range is correlated to module brand.

This XML configuration snippet is used to set the output power of the network interface in dBm.

Configure tx-output-power to 1.0dBm at slot6, network-interface 0.

Here is a sample OpenConfig NetConf Payload to set the output power of the network interface in dBm.

The below CLI command is used to set the output power of the network interface in dBm.

Here is a sample OcNOS NetConf Payload to set the output power of the network interface in dBm.

This filter for the Get operation results in the Get OpenConfig Return output shown below.

This validation response provides information on the configuration and runtime for setting the output power of the network interface in dBm.

Use the delete operation to remove this configuration, as shown below: