Traffic configuration | Configure 400G digital coherent optics | Optics and Hardware Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

Introduces traffic configuration and outlines the main concept, process, task, principle, and reference areas in this section. Guides technical users to quickly locate the procedures and supporting data they need.

Traffic configuration covers traffic-mode settings and supported combinations, including muxponder modes, FEC, modulation, and DAC rate. Applicable for optics controllers.

Traffic configuration values for 400G digital coherent optics

This table contains the possible traffic configuration values for the 400G Digital Coherent QSFP-DD optical modules, in the transponder and muxponder mode:

Table 1. 400G Digital Coherent QSFP-DD Traffic Capabilities and Example Settings
	Client Speed	Trunk Speed	Frequency	FEC	Modulation	DAC-Rate	Chromatic Dispersion (CD)	Transmitted (Tx) Power
QDD-400G-ZR-S	1x400G, 4x100G	400G	C-Band, 196.1 To 191.3 THz	cFEC	16QAM	1x1	-2400 to +2400	Each optical module has its own Tx power optimal values. You can change the Tx power value based on the module capability.
QDD-400G-ZRP-S	1x400G, 4x100G, 3x100G, 2x100G, 1x100G Note Release 7.3.15 supports only 1x400 and 4x100 client speed.	400G, 300G, 200G, 1x100 Note Release 7.3.15 supports only 400G trunk speed.	C-Band, 196.1 To 191.3 THz	oFEC, cFEC	16QAM, 8QAM, QPSK Release 7.3.15 supports only 16QAM.	1x1 (OIF, OpenZR+ Mode without Tx shaping), 1x1.25 (Cisco Mode with Tx shaping), 1x5 (OpenZR+ Mode with Tx shaping)	Release 7.3.15: -80000 to +80000 Release 7.3.2: -160000 to +160000	Each optical module has its own Tx power optimal values. You can change the Tx power value based on the module capability.
DP04QSDD-HE0	1x400G, 4x100G, 3x100G, 2x100G, 1x100G	400G, 300G, 200G, 100G	C-Band, 196.1 To 191.3 THz	oFEC, cFEC	16QAM, 8QAM, QPSK	1x1.25 (Cisco Mode), 1x5 (OIF, OpenZR+ Mode)	400G: −52000 to +52000 100G: −160000 to +160000	Each optical module has its own Tx power optimal values. You can change the Tx power value based on the module capability.
DP04QSDD-ER1	1x400G, 2x200G, 4x100G	400G	193.7THz	cFEC, oFEC	16QAM	1x1	-2400 to +2400	Fixed at maximum output around -9 dBm.
DP01QSDD-ZF1	1x100G	100G	193.7THz	oFEC	QPSK	1x1	-2400 to +2400	Fixed at maximum output around -6 dBm.
DP04QSDD-HE0-A1	1x400G, 4x100G, 3x100G, 2x100G, 1x100G	400G, 300G, 200G, 100G	C‑Band, 196.1 to 191.3 THz	cFEC, oFEC	16QAM, 8QAM, QPSK	1x1.25 (Cisco Mode), 1x5 (OIF, OpenZR+ Mode)	400G: −52000 to +52000 100G: −160000 to +160000	Each optical module has its own Tx power optimal values. You can change the Tx power value based on the module capability.
400G Transponder oFEC OpenZR+ Mode (example settings)	No need to configure 400G transponder mode	No setting required; tied to Client Speed	dwdm-carrier 100MHz-grid frequency 1931000	fec OFEC (default; can be omitted)	modulation 16Qam (default; can be omitted)	DAC-Rate 1x1.5	cd-min −20000 cd-max 20000	transmit-power 10 (+1 dBm)
400G Muxponder oFEC Cisco Mode (example settings)	breakout 4x100	No setting required; tied to Client Speed	dwdm-carrier 100MHz-grid frequency 1931000	fec OFEC (default; can be omitted)	modulation 16Qam (default; can be omitted)	DAC-Rate 1x1.25 (default; can be omitted)	cd-min −20000 cd-max 20000	transmit-power 10 (+1 dBm)

This table contains the possible Transponder and Muxponder configuration values for the QDD-400G-ZR-S optical module:

Table 2. QDD-400G-ZR-S Transponder and Muxponder Configuration Values
TXP/MXP	Client	Trunk	Modulation	FEC	DAC Rate
400G-TXP	1 client, 400G speed	1 trunk, 400G	16 QAM	cFEC	1x1
4x100G-MXP	4 clients, 100G speed	1 trunk, 400G	16 QAM	cFEC	1x1

This table contains the possible Transponder and Muxponder configuration values for the QDD-400G-ZRP-S optical module:

Table 3. QDD-400G-ZRP-S Transponder and Muxponder Configuration Values
TXP/MXP	Client	Trunk	Modulation	FEC	DAC Rate
400G-TXP	1 Client, 400G speed	1 trunk, 400G speed	16 QAM	oFEC	1x1.25
400G-TXP	1 Client, 400G speed	1 trunk, 400G speed	16 QAM	oFEC	1x1
400G-TXP	1 Client, 400G speed	1 trunk, 400G speed	16 QAM	cFEC	1x1
4x100G- MXP	4 clients, 100G speed	1 trunk, 400G speed	16 QAM	oFEC	1x1.25
4x100G-MXP	4 Client, 100G speed	1 trunk, 400G speed	16 QAM	oFEC	1x1
4x100G- MXP	4 clients, 100G speed	1 trunk, 400G speed	16 QAM	cFEC	1x1
3x100G-MXP	3 clients, 100G speed	1 trunk, 400G speed	8 QAM	oFEC	1x1.25
3x100G-MXP	3 Client, 100G speed	1 trunk, 400G speed	8 QAM	oFEC	1x1
2x100G-MXP	2 clients, 100G speed	1 trunk, 200G speed	QPSK	oFEC	1x1.50
2x100G-MXP	2 Client, 100G speed	1 trunk, 400G speed	QPSK	oFEC	1x1
2x100G-MXP	2 Client, 100G speed	1 trunk, 400G speed	16 QAM	oFEC	1x1.25
1x100G-MXP	1 client, 100G speed	1 trunk, 100G speed	QPSK	oFEC	1x1.50

The high optical performance DP04QSDD-HE0 QSFP-DD pluggable coherent optical module is developed for easy deployment in Reconfigurable Optical Add/Drop Multiplexer (ROADM) line systems.

This table lists the possible Transponder and Muxponder configuration values for the DP04QSDD-HE0 and DP04QSDD-HE0-A1 optical modules.

Table 4. DP04QSDD-HE0/DP04QSDD-HE0-A1 Transponder and Muxponder Configuration Values
TXP/MXP	Client	Trunk	Modulation	FEC	DAC Rate	MSA Support
400G-TXP	1 client, 400G speed	1 trunk, 400G speed	16 QAM	oFEC	1x1.25
400G-TXP	1 client, 400G speed	1 trunk, 400G speed	16 QAM	cFEC	1x1.5	400ZR
400G-TXP	1 client, 400G speed	1 trunk, 400G speed	16 QAM	oFEC	1x1.5	OpenZR+
4x100G- MXP	4 clients, 100G speed	1 trunk, 400G speed	16 QAM	oFEC	1x1.25
4x100G- MXP	4 clients, 100G speed	1 trunk, 400G speed	16 QAM	cFEC	1x1.5	400ZR
4x100G- MXP	4 clients, 100G speed	1 trunk, 400G speed	16 QAM	oFEC	1x1.5	OpenZR+
3x100G-MXP	3 clients, 100G speed	1 trunk, 300G speed	8 QAM	oFEC	1x1.25
3x100G-MXP	3 clients, 100G speed	1 trunk, 300G speed	8 QAM	oFEC	1x1.5	OpenZR+
2x100G-MXP	2 clients, 100G speed	1 trunk, 200G speed	QPSK	oFEC	1x1.5	OpenZR+
2x100G-MXP	2 clients, 100G speed	1 trunk, 200G speed	8 QAM	oFEC	1x1.25
2x100G-MXP	2 clients, 100G speed	1 trunk, 200G speed	16 QAM	oFEC	1x1.25
1x100G-TXP	1 client, 100G speed	1 trunk, 100G speed	QPSK	oFEC	1x1.5	OpenZR+

This table lists the possible Transponder and Muxponder configuration values for the DP04QSDD-HE0 optical module.

Table 5. DP04QSDD-HE0 Transponder and Muxponder Configuration Values
TXP/MXP	Client	Trunk	Modulation	FEC	DAC Rate
400G-TXP	1 Client, 400G speed	1 trunk, 400G speed	16 QAM	oFEC	1x1.25
400G-TXP	1 clients, 400G speed		16 QAM		1x1.50
300G-TXP	1 clients, 300G speed		8 QAM		1x1.50
100G-TXP	1 Client, 100G speed	1 trunk, 400G speed	QPSK	oFEC	1x1.50
4x100G- MXP	4 clients, 100G speed	1 trunk, 400G speed	16 QAM	oFEC	1x1.25
4x100G- MXP	4 clients, 100G speed		16 QAM		1x1.50
3x100G-MXP	3 clients, 100G speed	1 trunk, 400G speed	8 QAM	oFEC	1x1.25
3x100G-MXP	3 clients, 100G speed		8 QAM		1x1.50
2x100-MXP	2 Client, 100G speed	2 Client, 100G speed	QPSK	oFEC	1x1.50

Configure muxponder mode

By default, the Cisco IOS XR software configures the QDD-400G-ZR-S and QDD-400G-ZRP-S optical modules in the 400G transponder mode. Follow this task to configure muxponder mode.

Using the breakout muxponder mode command, you can configure muxponder mode on optics controllers. Based on the muxponder mode, you can choose the modulation.

Muxponder mode options available for QDD-400G-ZR-S are:

4x100

Muxponder mode options available for QDD-400G-ZRP-S and DP04QSDD-HE are:

4x100
3x100
2x100

Note

Release 7.3.15 supports only 4x100 muxponder mode.

Refer to the tables in the Traffic configuration values for 400G digital coherent optics section for modulation values, based on the muxponder mode.

Using the no breakout muxponder mode command, you can switch from muxponder mode to transponder mode on optics controllers.

Before you begin

Ensure prerequisites for software state, hardware state, and access privileges are met.

Identify the optics controller R/S/I/P and the muxponder mode that you want to configure.

Procedure

Configure muxponder mode on the optics controller.
Example:

This example shows how to configure muxponder mode on the optics controller:
```
Router#config
Router(config)#controller optics 0/0/0/13
Router(config-Optics)#breakout 4x100
Router(config-Optics)#commit
Router(config-Optics)#exit
Router(config)#exit
```
Note

In this example, the Cisco IOS XR software creates four Ethernet clients with 100GE speed, which can be verified using the show interfaces brief | include R/S/I/P command.

Verify the running configuration on the optics controller.

Example:

This example shows the running configuration for the optics controller:

Router#show run controller optics 0/0/0/13
Thu May 13 12:24:42.353 UTC
controller Optics0/0/0/13
 cd-min -4000
 cd-max 4000
 breakout 4x100
 !

Verify that the expected 100GE client interfaces are created.

Example:

Verification

This example shows how to verify the muxponder mode configuration:

Router#show interfaces brief | include 0/0/0/13
 Hu0/0/0/13/0          up          up               ARPA  1514  100000000
 Hu0/0/0/13/1          up          up               ARPA  1514  100000000
 Hu0/0/0/13/2          up          up               ARPA  1514  100000000
 Hu0/0/0/13/3          up          up               ARPA  1514  100000000

Optional: Switch from muxponder mode to transponder mode on the optics controller.
Example:

This example shows how to switch to transponder mode on the optics controller:
```
Router#config
Router(config)#controller optics 0/0/0/13
Router(config-Optics)#no breakout 4x100
Router(config-Optics)#commit
Router(config-Optics)#exit
Router(config)#exit
```
Note

In this example, the Cisco IOS XR software creates a single 400GE interface, which can be verified using the show interfaces brief | include R/S/I/P command.
Optional: Verify the running configuration on the optics controller after you switch to transponder mode.
Example:

Running configuration

This example shows the running configuration for the optics controller. The breakout configuration is absent in the running configuration.
```
Router#show run controller optics 0/0/0/13
Thu May 13 13:51:20.330 UTC
controller Optics0/0/0/13
 cd-min -4000
 cd-max 4000
 transmit-power -100
 !
```
Optional: Verify that the expected 400GE interface is created.
Example:

This example shows how to verify the transponder mode configuration:
```
Router#show interfaces brief | include 0/0/0/13
FH0/0/0/13          up          up               ARPA  1514  400000000
```

Muxponder mode is configured on the optics controller and the expected client interfaces are created.

What to do next

Continue with related procedures as required by your workflow.

2x200G DAC breakout modes

This topic explains 2x200G DAC breakout modes and provides the technical context you need before configuration.

The 2x200G DAC Cable with 2x200G Breakout CLI feature allows you to manually configure 2x200G breakout interfaces when using 2x200G modules.

Table 6. Feature History Table
Feature Name	Release Information	Feature Description
Configure 2x200G DACs with 2x200 Breakout	Release 25.4.1	Introduced in this release on: Fixed Systems (8010 [ASIC: A100])(select variants only) This feature is supported on: the Cisco routers. 8011-4G24Y4H-I 8011-32Y8L2H2FH 8011-12G12X4Y-A/D
Configure 2x200G DACs with 2x200 Breakout	Release 25.2.1	Introduced in this release on: Fixed Systems (8200 [ASIC: Q200](select variants only), Modular Systems (8800 [LC ASIC: Q200]) (select variants only) This feature enables support for configuring 2x200G DAC (Direct Attach Copper) cables with a 2x200G breakout. It addresses the issue where certain 2x200G DAC cables are incorrectly detected as 400G cables and allows you to explicitly configure the 2x200G breakout using the CLI (Command-Line Interface). The feature is supported on: 88-LC0-36FH 88-LC0-36FH-M 8201-32FH 8202-32FH-M This feature introduces these changes: CLI: The breakout* keyword is enhanced to include 2x200 option in the controller optics command

The 2x200G DAC Cable with 2x200G Breakout feature allows you to manually configure 2x200G breakout interfaces when using 2x200G modules. By default, the system might detect these modules as 400G and create 400G interfaces. This feature provides a CLI command to explicitly set the breakout configuration to 2x200G, creating the correct interfaces. The CLI command is implemented under the existing controller optics command.

Note

Starting from Cisco IOS XR Release 25.2.1, the 2x200 implicit breakout is deprecated. To operate 2x200G modules in 2x200 mode, you must explicitly apply the breakout configuration.

Configure 2x200G DAC breakout

Follow this task to configure 2x200G DAC breakout.

Use this procedure in the appropriate operating context for your deployment.

Before you begin

Associated line cards should be operational.
Supported 2x200G modules should be inserted.

Procedure

Configure 2x200G DAC with 2x200G breakout.

Example:

Router#configure 
Router(config)#controller optics 0/0/1/1
Router(config-if)# breakout 2x200
Router(config-if)#commit

Configure autonegotiation on the connected interfaces.

You must enable auto negotiation on the connected interfaces after applying the 2x200G breakout configuration for the DACs.
Example:
```
Router#configure 
Router(config)#interface TwoHundredGigE 0/0/1/1/0
Router(config-if)# negotiation auto
Router(config-if)#commit
```
Note

Verify that the system reflects the intended configuration state.

What to do next

Continue with related procedures as required by your workflow.

100G operating modes with 200G DAC

This topic explains 100G operating modes with 200G DAC and provides the technical context you need before configuration.

The configuration of 100G operating modes with 200G DAC is a process that

allows devices to operate at various speeds and lane combinations, and
provides high-bandwidth links between networking devices using 200G QSFP56 DAC and 4x100 DAC.

Table 7. Feature History Table
Feature Name	Release Information	Feature Description
Configure 100G operating modes with 200G DAC	Release 25.3.1	Introduced in this release on: Fixed Systems (8010 [ASIC: A100], 8200 [ASIC: Q200)) (select variants only) The feature addresses the need for flexible speed configuration, particularly for connecting to custom servers that support specific speed and lane modes, and to prevent alarms when optics with different speeds are inserted. You will have 100G operating modes with 200G QSFP56 DAC, that allows to configure multi-rate optics and passive copper cables to operate at various speeds and lane combinations. This feature is supported on: 8201-32FH 8101-32FH The feature introduces these changes: CLI: The speed keyword is included along with the 100G [ host-lanes < 4 \| 2 > ] option in the controller optics command.

Flexible 100G modes configuration for 200G DAC

The configuration for 100G operating modes with 200G DAC feature allows you to manually configure the speed of the port as 100G when using 200G DAC modules. This feature provides a CLI command to explicitly set the speed configuration to 100G operating modes and optionally specify the number of host lanes. The CLI command is implemented under the existing controller optics command which allows users to configure the speed of a port and optionally specify the number of host lanes.

Benefits of the 100G modes in 200G DAC

Allows the users to use the same 200G QSFP56 DAC for different speeds based on the speed support of peer device. This means a single cable type can serve multiple connectivity needs, reducing the variety of hardware required.
The feature allows setting the unused port to a speed that suits the system, even if a different speed optics is inserted, thereby avoiding false alarms and streamlining operations.

Configure 100G operating modes with 200G and 4x100 DAC

Follow this task to configure 100G operating modes with 200G and 4x100 DAC.

Use this procedure in the appropriate operating context for your deployment.

Before you begin

Ensure prerequisites for software state, hardware state, and access privileges are met.

Procedure

Configure 100G operational modes with 200G and 4x100 DAC.
Example:

This example shows how to configure the speed of port as 100G with host lane valuse as 2. The supported host lanes for 100G speed are 2 and 4.
```
Router#configure 
         Router(config)#controller optics 0/0/0/0
         Router(config-Optics)# speed 100g host-lanes 2
         Router(config-Optics)#commit
```

Run the show running-config controller optics CLI command to verify the running configuration of the speed port.

Example:

Router#show running-config controller optics 0/0/0/0 
Thu Aug 14 01:16:52.946 UTC
controller Optics0/0/0/0
 speed 100g host-lanes 2

Optional: Run the show configuration failed CLI command to verify if the speed port configuration is failed.

Example:

This example shows the failure scenario, when the breakout is configured on the same port.

Router#show config failed
Tue Oct 29 13:07:55.478 UTC
!! SEMANTIC ERRORS: This configuration was rejected by
!! the system due to semantic errors. The individual
!! errors with each failed configuration command can be
!! found below. Controller Optics0/0/0/0 speed 100g host-lanes 2
!!% Breakout is configured on this port, remove breakout configuration before apply port speed configuration
!
end

Example:

This example shows the failure scenario, when the unsupported host lanes are configured.

Router#:ios(config)#show config failed
Tue Oct 29 13:07:55.478 UTC
!! SEMANTIC ERRORS: This configuration was rejected by
!! the system due to semantic errors. The individual
!! errors with each failed configuration command can be
!! found below.

controller Optics0/0/0/0
 speed 100g host-lanes 3
!!% The list of supported host lanes for speed 100g is 2, 4
!
end

Note
After the CLI is verified, the alarm is raised when the optics is present and optics driver cannot configure the optics in such speed or host lanes:
Router#:Oct 29 12:25:42.808 UTC: optics_driver[274]: %PKT_INFRA-FM-3-
FAULT_MAJOR : ALARM_MAJOR : MODULE AND SPEED CONFIG MISMATCH :DECLARE
:0/RP0/CPU0:  Optics0/0/0/18
If you remove the module, the alarm is cleared. Similarly, when a new module is inserted, the same alarm is triggered if the module does not support the configured speed.

Verify that the system reflects the intended configuration state.

What to do next

Continue with related procedures as required by your workflow.

Configure modulation

Use this task to configure the modulation value on an optics controller.

You can configure modulation on optics controllers. Based on the muxponder mode, you can choose the modulation.

For supported modulation values, see Traffic configuration values for 400G digital coherent optics.

Note

The system accepts any modulation value that you enter. However, if the modulation value is outside the supported range, the optical module is not configured with that value.

Instead, the optical module is auto-configured with a valid modulation value. To view this value, use the show controller optics R/S/I/P command.

Before you begin

Identify the optics controller optics R/S/I/P and the supported modulation value that you want to configure.

Procedure

Enter XR configuration mode.
Example:
```
Router#config
```
Enter optics controller configuration mode.
Example:
```
Router(config)#controller optics 0/0/0/1
```
Configure the modulation value on the optics controller.
Example:
```
Router(config-Optics)#modulation 16Qam
```
Commit the configuration.
Example:
```
Router(config-Optics)#commit
```
Exit optics controller configuration mode.
Example:
```
Router(config-Optics)#exit
```
Exit XR configuration mode.
Example:
```
Router(config)#exit
```

Verify the modulation value in the running configuration.

Example:

This example shows the running configuration:

Router#show run controller optics 0/0/0/1
controller Optics0/0/0/1
 cd-min -4000
 cd-max 4000
 transmit-power -100
 modulation 16Qam
!

Verify the configured modulation value on the optical module.

Example:

This example shows how to verify the configured modulation value for the optics controller:

Router#show controller optics 0/0/0/1
 Controller State: Up
 Transport Admin State: In Service
 Laser State: On
 LED State: Green
 FEC State: FEC ENABLED
 Optics Status
         Optics Type:  QSFPDD 400G ZR
         DWDM carrier Info: C BAND, MSA ITU Channel=61, Frequency=193.10THz,
         Wavelength=1552.524nm
         Alarm Status:
         -------------
         Detected Alarms: None
         LOS/LOL/Fault Status:
         Alarm Statistics:
         -------------
         HIGH-RX-PWR = 0            LOW-RX-PWR = 0
         HIGH-TX-PWR = 0            LOW-TX-PWR = 0
         HIGH-LBC = 0               HIGH-DGD = 0
         OOR-CD = 0                 OSNR = 35
         WVL-OOL = 0                MEA  = 0
         IMPROPER-REM = 0
         TX-POWER-PROV-MISMATCH = 0
         Laser Bias Current = 0.0 %
         Actual TX Power = -7.87 dBm
         RX Power = -8.27 dBm
         RX Signal Power = -8.43 dBm
         Frequency Offset = 130 MHz
         Performance Monitoring: Enable
         THRESHOLD VALUES
         ----------------
         Parameter                 High Alarm  Low Alarm  High Warning  Low Warning
         ------------------------  ----------  ---------  ------------  -----------
         Rx Power Threshold(dBm)          1.9      -28.2           0.0        -25.0
         Tx Power Threshold(dBm)          0.0      -15.0          -2.0        -16.0
         LBC Threshold(mA)               0.00       0.00          0.00         0.00
         Temp. Threshold(celsius)       80.00      -5.00         75.00        15.00
         Voltage Threshold(volt)         3.46       3.13          3.43         3.16
         LBC High Threshold = 98 %
         Configured Tx Power = -6.00 dBm
         Configured CD High Threshold = 80000 ps/nm
         Configured CD lower Threshold = -80000 ps/nm
         Configured OSNR lower Threshold = 9.00 dB
         Configured DGD Higher Threshold = 80.00 ps
         Baud Rate =  59.8437500000 GBd
         Modulation Type: 16QAM
         Chromatic Dispersion 0 ps/nm
         Configured CD-MIN -4000 ps/nm  CD-MAX 4000 ps/nm
         Second Order Polarization Mode Dispersion = 5.00 ps^2
         Optical Signal to Noise Ratio = 36.30 dB
         Polarization Dependent Loss = 0.40 dB
         Polarization Change Rate = 0.00 rad/s
         Differential Group Delay = 4.00 ps
         Temperature = 54.00 Celsius
         Voltage = 3.37 V
 Transceiver Vendor Details
         Form Factor            : QSFP-DD
         Optics type            : QSFPDD 400G ZR
         Name                   : CISCO-ACACIA
         OUI Number             : 7c.b2.5c
         Part Number            : DP04QSDD-E20-19E
         Rev Number             : 10
         Serial Number          : ACA2447003L
         PID                    : QDD-400G-ZR-S
         VID                    : ES03
         Firmware Version       : 61.12
         Date Code(yy/mm/dd)    : 20/12/02

The optics controller is configured with the modulation value, and the controller output shows the active modulation type.

What to do next

Continue with related traffic configuration tasks as required for your deployment.

Configure DAC rate

Use this task to configure the digital-to-analog conversion (DAC) sampling rate on an optics controller.

You can set the DAC sampling rate on optics controllers. You can modify the DAC sampling rate only on the QDD-400G-ZRP-S and DP04QSDD-HE optical modules.

For DAC rate values, see Traffic configuration values for 400G digital coherent optics.

Note

The QDD-400G-ZR-S optical module supports 1x1 DAC rate in cFEC mode. The QDD-400G-ZRP-S and DP04QSDD-HE optical modules support 1x1 DAC rate in cFEC mode and 1x1.25 DAC rate in oFEC mode.

Before you begin

Identify the optics controller optics R/S/I/P , the FEC mode, and the supported DAC rate that you want to configure.

Procedure

Enter XR configuration mode.
Example:
```
Router#config
```
Enter optics controller configuration mode.
Example:
```
Router(config)#controller optics 0/0/0/1
```
Configure the DAC rate on the optics controller.
Example:
```
Router(config-Optics)#dac-rate 1x1
```
Commit the configuration.
Example:
```
Router(config-Optics)#commit
```
Exit optics controller configuration mode.
Example:
```
Router(config-Optics)#exit
```
Exit XR configuration mode.
Example:
```
Router(config)#exit
```

Verify the DAC rate in the running configuration.

Example:

This example shows the running configuration:

Router#show run controller optics 0/0/0/1
Thu May 13 12:52:35.020 UTC
controller Optics0/0/0/1
 cd-min -4000
 cd-max 4000
 transmit-power -100
 modulation 16Qam
 DAC-Rate 1x1
!
!

Verify the configured DAC rate on the optical module.

Example:

This example shows how to verify the configured DAC rate for the optics controller:

Router#show controller optics 0/0/0/1
 Controller State: Up
 Transport Admin State: In Service
 Laser State: On
 LED State: Green
 FEC State: FEC ENABLED
 Optics Status
         Optics Type:  QSFPDD 400G ZR
         DWDM carrier Info: C BAND, MSA ITU Channel=61, Frequency=193.10THz,
         Wavelength=1552.524nm
         Alarm Status:
         -------------
         Detected Alarms: None
         LOS/LOL/Fault Status:
         Alarm Statistics:
         -------------
         HIGH-RX-PWR = 0            LOW-RX-PWR = 0
         HIGH-TX-PWR = 0            LOW-TX-PWR = 0
         HIGH-LBC = 0               HIGH-DGD = 0
         OOR-CD = 0                 OSNR = 35
         WVL-OOL = 0                MEA  = 0
         IMPROPER-REM = 0
         TX-POWER-PROV-MISMATCH = 0
         Laser Bias Current = 0.0 %
         Actual TX Power = -7.87 dBm
         RX Power = -8.27 dBm
         RX Signal Power = -8.43 dBm
         Frequency Offset = 130 MHz
         DAC Rate = 1x1
         Performance Monitoring: Enable
         THRESHOLD VALUES
         ----------------
         Parameter                 High Alarm  Low Alarm  High Warning  Low Warning
         ------------------------  ----------  ---------  ------------  -----------
         Rx Power Threshold(dBm)          1.9      -28.2           0.0        -25.0
         Tx Power Threshold(dBm)          0.0      -15.0          -2.0        -16.0
         LBC Threshold(mA)               0.00       0.00          0.00         0.00
         Temp. Threshold(celsius)       80.00      -5.00         75.00        15.00
         Voltage Threshold(volt)         3.46       3.13          3.43         3.16
         LBC High Threshold = 98 %
         Configured Tx Power = -6.00 dBm
         Configured CD High Threshold = 80000 ps/nm
         Configured CD lower Threshold = -80000 ps/nm
         Configured OSNR lower Threshold = 9.00 dB
         Configured DGD Higher Threshold = 80.00 ps
         Baud Rate =  59.8437500000 GBd
         Modulation Type: 16QAM
         Chromatic Dispersion 0 ps/nm
         Configured CD-MIN -4000 ps/nm  CD-MAX 4000 ps/nm
         Second Order Polarization Mode Dispersion = 5.00 ps^2
         Optical Signal to Noise Ratio = 36.30 dB
         Polarization Dependent Loss = 0.40 dB
         Polarization Change Rate = 0.00 rad/s
         Differential Group Delay = 4.00 ps
         Temperature = 54.00 Celsius
         Voltage = 3.37 V
 Transceiver Vendor Details
         Form Factor            : QSFP-DD
         Optics type            : QSFPDD 400G ZR
         Name                   : CISCO-ACACIA
         OUI Number             : 7c.b2.5c
         Part Number            : DP04QSDD-E20-19E
         Rev Number             : 10
         Serial Number          : ACA2447003L
         PID                    : QDD-400G-ZR-S
         VID                    : ES03
         Firmware Version       : 61.12
         Date Code(yy/mm/dd)    : 20/12/02

The optics controller is configured with the DAC rate, and the controller output shows the active DAC rate.

What to do next

Continue with related traffic configuration tasks as required for your deployment.

Configure FEC

Use this task to configure forward error correction on an optics controller.

You can configure FEC only on optics controllers. You can modify FEC only on the QDD-400G-ZRP-S and DP04QSDD-HE optical modules.

FEC controls errors during data transmission by adding data redundancy. This redundancy lets the receiver detect and correct a limited number of errors without requesting retransmission.

For FEC values, see Traffic configuration values for 400G digital coherent optics.

Note

The QDD-400G-ZR-S optical module supports cFEC. The QDD-400G-ZRP-S and DP04QSDD-HE optical modules support cFEC and oFEC.

Before you begin

Identify the optics controller optics R/S/I/P and the supported FEC mode that you want to configure.

Procedure

Enter XR configuration mode.
Example:
```
Router#configure
```
Enter optics controller configuration mode.
Example:
```
Router(config)#controller optics 0/0/0/13
```
Configure FEC on the optics controller.
Example:
```
Router(config-Optics)#fec CFEC
```
Commit the configuration.
Example:
```
Router(config-Optics)#commit
```
Exit optics controller configuration mode.
Example:
```
Router(config-Optics)#exit
```
Exit XR configuration mode.
Example:
```
Router(config)#exit
```

Verify the FEC mode in the controller configuration.

Example:

This example shows the running configuration:

Router#show controllers optics 0/0/0/13
controller Optics0/0/0/1
 cd-min -4000
 cd-max 4000
 transmit-power -100
 fec CFEC
 modulation 16Qam
 DAC-Rate 1x1.25
!

Verify the FEC mode in the coherent DSP output.

Example:

This example shows how to verify the FEC configuration for the optics controller:

Router#show controller coherentdsp 0/0/0/13
Thu May 27 17:28:51.960 UTC
Port                                            : CoherentDSP 0/0/0/13
Controller State                                : Down
Inherited Secondary State                       : Normal
Configured Secondary State                      : Maintenance
Derived State                                   : Maintenance
Loopback mode                                   : Internal
BER Thresholds                                  : SF = 1.0E-5  SD = 1.0E-7
Performance Monitoring                          : Enable
Bandwidth                                       : 400.0Gb/s

Alarm Information:
LOS = 6 LOF = 0 LOM = 0
OOF = 0 OOM = 0 AIS = 0
IAE = 0 BIAE = 0        SF_BER = 0
SD_BER = 0      BDI = 0 TIM = 0
FECMISMATCH = 0 FEC-UNC = 0     FLEXO_GIDM = 0
FLEXO-MM = 0    FLEXO-LOM = 0   FLEXO-RDI = 0
FLEXO-LOF = 5
Detected Alarms                                 : LOS
Bit Error Rate Information
PREFEC  BER                                     : 5.0E-01
POSTFEC BER                                     : 0.0E+00
Q-Factor                                        : 0.00 dB
Q-Margin                                        : -7.20dB
OTU TTI Received
FEC mode                                        : C_FEC

The optics controller is configured with the FEC mode, and the coherent DSP output shows the active FEC mode.

What to do next

Continue with related traffic configuration tasks as required for your deployment.