Configuring Controllers

This chapter describes the Optics Controller . This chapter also describes the procedures used to configure the controllers.


Note

When you plan to replace a configured optical module with a different type of optical module, you must clear the configurations of the old module before installing the new optical module.

Optics Controllers

Controllers are represented in the rack/slot/instance/port format (r/s/i/p); for example, 0/3/0/1. Each port has an optics controller that is created on startup.


Note

You must shut down the optics controller before you perform any of the following tasks:

  • Configure the controller

  • Restore a saved configuration

  • Upgrade the DSP processor or CFP2 optics module Field Programmable Device (FPD)

Port Mode Speed Support for NC57 Line Cards

Table 1. Feature History Table

Feature Name

Release Information

Feature Description

50G Optics Support for Quad Port Mode on NC57 Line Cards

Release 24.2.1

Introduced in this release on: NCS 5500 modular routers; NCS 5700 line cards [Mode: Compatibility; Native]

This feature provides higher bandwidth on the following NC57 line cards with the support for 50G optics on the 8-port quads of these line cards:

  • NC-57-48Q2D-S

  • NC-57-48Q2D-SE

CLI: This feature modifies the hw-module quad command.

How to Configure Controllers

This section contains the following procedures:

Configuring Optics Controller

To configure the Optics controller, use the following commands:

Before you begin

You must shut down the optics controller before you perform any of the following tasks:

  • Configure the controller

  • Restore a saved configuration

Procedure

  Command or Action Purpose

Step 1

configure

Example:


RP/0/RP0/CPU0:router# configure terminal

Enters global configuration mode.

Step 2

controller optics r/s/i/p

Example:


RP/0/RP0/CPU0:router(config)# controller optics 0/3/0/1

Enters optics controller configuration mode.

Step 3

shutdown

Example:


RP/0/RP0/CPU0:router(config-Optics)# shutdown

Shuts down the optics controller.

Step 4

commit

Example:


RP/0/RP0/CPU0:router(config-Optics)# commit

Saves the configuration changes to the running configuration file and remains within the configuration session.

Step 5

rx-high-threshold rx-high

Example:


RP/0/RP0/CPU0:router(config-Optics)# rx-high-threshold 200

Configures the high receive power threshold. The range is -400 to 300 (in the units of 0.1 dBm).

Step 6

tx-high-threshold tx-high

Example:


RP/0/RP0/CPU0:router(config-Optics)# tx-high-threshold 300

Configures the high transmit power threshold. The range is -400 to 300 dBm (in the units of 0.1 dBm).

Step 7

no shutdown

Example:


RP/0/RP0/CPU0:router(config-Optics)# no shutdown

Removes the shutdown configuration on the optics controller.

Step 8

commit

Example:


RP/0/RP0/CPU0:router(config-Optics)# commit

Saves the configuration changes to the running configuration file and remains within the configuration session.

Configure Port Mode Speed

To configure the port mode speed, use the following commands:

Before you begin

Ensure that you shut down the controller before you configure the controller or restore a saved configuration.

Procedure

  Command or Action Purpose

Step 1

configure

Example:


RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

controller optics r/s/i/p

Example:


RP/0/RP0/CPU0:router(config)# controller optics 0/3/0/0

Enters optics controller configuration mode

Step 3

shutdown

Example:


RP/0/RP0/CPU0:router(config-Optics)# shutdown

Shuts down the optics controller.

Step 4

commit

Example:


RP/0/RP0/CPU0:router(config-Optics)# commit

Saves the configuration changes to the running configuration file and remains within the configuration session.

Step 5

port-mode speed { 100G | 150G | 200G } mod { 16qam | 8qam |qpsk } fec { 15sdfec | 15sdfecde | 25sdfec | otu7staircase } diff { enable | disable }

Example:


RP/0/RP0/CPU0:router(config-Optics)# port-mode speed 100G mod qpsk fec 15sdfec diff

Configures the port mode speed.

Step 6

no shutdown

Example:


RP/0/RP0/CPU0:router(config-Optics)# no shutdown

Removes the shutdown configuration on the optics controller.

Step 7

commit

Example:


RP/0/RP0/CPU0:router(config-Optics)# commit

Saves the configuration changes to the running configuration file.

If you need to change the port-mode speed, ensure that you remove the existing port mode speed configuration by entering the no port-mode command. You can then change the port mode speed.

The following example shows how to change the port mode speed to 100Gbps.


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# controller optics 0/3/0/0
RP/0/RP0/CPU0:router(config-Optics)# shutdown
RP/0/RP0/CPU0:router(config-Optics)# commit
RP/0/RP0/CPU0:router(config-Optics)# no port-mode
RP/0/RP0/CPU0:router(config-Optics)# commit
RP/0/RP0/CPU0:router(config-Optics)# port-mode speed 100G mod qpsk fec 15sdfec diff enable
RP/0/RP0/CPU0:router(config-Optics)# commit
RP/0/RP0/CPU0:router(config-Optics)# no shutdown
RP/0/RP0/CPU0:router(config-Optics)# commit
RP/0/RP0/CPU0:router(config-Optics)# exit
RP/0/RP0/CPU0:router(config)#

To modify the default 25Gpbs mode into 10Gbps mode, perform the below configuration:

Before Cisco IOS XR Release 7.5.1:

RP/0/RP0/CPU0:router(config)# hw-module quad 0 location 0/0/CPU0

RP/0/RP0/CPU0:router(config-quad-0x0)# mode 10g

From Cisco IOS XR Release 7.5.1:

RP/0/RP0/CPU0:router(config)# hw-module quad 0 location 0/0/CPU0 instance 1 mode 10g

RP/0/RP0/CPU0:router(config-quad-0x0)# mode 10g


Note

A quad number always starts from 0 to the maximum supported number. The number of quads supported varies from platform to platform and the CLI validates it. For example, the NCS 540 Series Router supports two quads (0 and 1). If you enter X=3, the CLI returns an error.

Here, instance indicates the MPA card instance. It can range from 0-5. For Cisco NCS 540 Series Routers, it is always 0. Whereas, for Cisco NCS 5500 Series Routers, the instance can be between 0-5, adding 1 for every MPA instance. The default value is 0.

To modify the default 25Gbps into 50Gbps mode, perform the following configuration:

Starting with Cisco IOS XR Release 24.2.1, you can configure 50Gpbs mode only on NC-57-48Q2D-S and NC-57-48Q2D-SE-S line cards.

RP/0/RP0/CPU0:router(config)# hw-module quad 0 location 0/0/CPU0 instance 0 mode 50g

RP/0/RP0/CPU0:router(config-quad-0x0)# mode 50g


Note

A quad number always starts from 0 to the maximum supported number. The number of quads supported varies from platform to platform and the CLI validates it. For example, the NCS 540 Series Router supports two quads (0 and 1). If you enter X=3, the CLI returns an error.

Here, instance indicates the MPA card instance. It can range from 0-5. For Cisco NCS 540 Series Routers, it is always 0. Whereas, for Cisco NCS 5500 Series Routers, the instance can be between 0-5, adding 1 for every MPA instance. The default value is 0.


Note

To revert to the default 25Gbps mode, use the no form of the hw-module quad command.

After you configure the port-mode speed, you can configure the following interfaces:

  • 100G – Each optics controller configuration creates a single 100GE port:

    • interface HundredGigE r/s/i/p/0 (wherep = CTP2 port 0-5)

      0/3/0/0/0

      0/3/0/1/0

      0/3/0/2/0

      0/3/0/3/0

      0/3/0/4/0

      0/3/0/5/0

  • 200G – Each optics controller configuration creates two 100GE ports:

    • interface HundredGigE r/s/i/p/0, r/s/i/p/1 (wherep = CTP2 port 0-5

      0/3/0/0/0, 0/3/0/0/1

      0/3/0/1/0, 0/3/0/1/1

      0/3/0/2/0, 0/3/0/2/1

      0/3/0/3/0, 0/3/0/3/1

      0/3/0/4/0, 0/3/0/4/1

      0/3/0/5/0, 0/3/0/5/1

  • 150G (coupled) – Coupled optics controller configuration creates three 100GE port:

    • interface HundredGigE r/s/i/p/0, r/s/i/p/1, r/s/i/p+1/0 (wherep = CTP2 port: 0, 2, 4 [port p and p +1 are coupled])

      0/3/0/0/0, 0/3/0/0/1, 0/3/0/1/0

      0/3/0/2/0, 0/3/0/2/1, 0/3/0/3/0

      0/3/0/4/0, 0/3/0/4/1, 0/3/0/5/0

For more information, see the Configuring Ethernet Interfaces chapter.

Configuring Wavelength

To configure wavelength, use the following commands:

Before you begin

  • Before configuring the wavelength, use the show controllers opticsr/s/i/p dwdm-carrrier-map command to display the wavelength and channel mapping for optics controllers.

  • You must shut down the controller before you configure the controller or restore a saved configuration.

Procedure

  Command or Action Purpose

Step 1

configure

Example:


RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2

controller optics r/s/i/p

Example:


RP/0/RP0/CPU0:router(config)# controller optics 0/3/0/1

Enters optics controller configuration mode.

Step 3

shutdown

Example:


RP/0/RP0/CPU0:router(config-Optics)# shutdown

Shuts down the optics controller.

Step 4

commit

Example:


RP/0/RP0/CPU0:router(config-Optics)# commit

Saves the configuration changes to the running configuration file and remains within the configuration session.

Step 5

dwdm-carrier {100MHz-grid frequency frequency } | {50GHz-grid [ frequency frequency | channel-number ] }

Example:


RP/0/RP0/CPU0:router(config-Optics)# dwdm-carrier 100MHz-grid frequency 1960875

Configures the frequency on the trunk port.

Step 6

no shutdown

Example:


RP/0/RP0/CPU0:router(config-Optics)# no shutdown

Removes the shutdown configuration on the optics controller.

Step 7

commit

Example:


RP/0/RP0/CPU0:router(config-Optics)# commit

Saves the configuration changes to the running configuration file and remains within the configuration session.

To configure a DWDM carrier with the required frequency:
RP/0/RP0/CPU0:router#config
RP/0/RP0/CPU0:router(config)#controller Optics0/3/0/0
RP/0/RP0/CPU0:router(config-Optics)#dwdm-carrier
RP/0/RP0/CPU0:router(config-Optics)#dwdm-carrier 100MHz-grid
RP/0/RP0/CPU0:router(config-Optics)#dwdm-carrier 100MHz-grid frequency
RP/0/RP0/CPU0:router(config-Optics)#dwdm-carrier 100MHz-grid frequency 1960625

The output of show run controller optics 0/3/0/0 command is: 

RP/0/RP0/CPU0:router#show run controller optics 0/3/0/0
Wed Nov  6 13:47:33.178 UTC
controller Optics0/3/0/0
transmit-power -7
port-mode speed 100G mod qpsk fec 25sdfec diff disable
dwdm-carrier 100MHz-grid frequency 1960625

Note

When you bring up the local optics controller, you might briefly see transient loss of signal (LOS) alarms on the console. This behavior might be observed during the initial tuning of the channel. 


PKT_INFRA-FM-2-FAULT_CRITICAL : ALARM_CRITICAL :LOS-P :DECLARE :CoherentDSP0/3/0/1: 
PKT_INFRA-FM-2-FAULT_CRITICAL : ALARM_CRITICAL :LOS-P :CLEAR :CoherentDSP0/3/0/1:

During the laser-on process, you might briefly see transient loss of line (LOL) alarms on the console. This alarm is cleared when the laser-on process is complete. 


PKT_INFRA-FM-3-FAULT_MAJOR : ALARM_MAJOR :CTP2 RX LOL :DECLARE ::  
PKT_INFRA-FM-3-FAULT_MAJOR : ALARM_MAJOR :CTP2 RX LOL :CLEAR ::

Admin sleep mode for optical transceivers

Admin sleep mode is a power management feature for optical transceivers that

  • enables administrators to place supported transceivers into a lower power state

  • maintains accessibility to the optics module for monitoring and configuration, and

  • reduces power consumption without physically removing the module.

provides a controlled way to place supported optical transceivers into a low power state. When you configure shutdown under controller optics <R/S/I/P>, the system transitions the associated transceiver to low power mode.

Table 2. Feature History Table

Feature Name

Release Information

Feature Description

Admin sleep mode for optical transceivers

Release 26.3.1

This feature provides a controlled way to reduce transceiver power consumption while keeping the optics accessible by adding an admin sleep mode or low power mode for optical transceivers on NCS 540 routers.

When a user applies shutdown under controller optics, the router places the corresponding optical module into a low power state.

Admin sleep mode for optical transceivers

Starting with Cisco IOS XR 26.3.1, Cisco IOS XR introduces support for administratively placing supported optical transceivers into a low power state on NCS540 platforms. When shutdown is configured under controller optics, the corresponding optics module transitions to low power mode. This helps reduce transceiver power consumption while keeping the module accessible. .

This feature adds a power mode field to the show controller optics output to display the current optics power state as High or Low. This field helps you confirm whether the optics is operating in the normal power state or the low power state.

Supported optics

The feature supports optics in the following families:

  • SFP

  • SFP+

  • SFP28

  • QSFP

  • QSFP+

  • QSFP-DD

Supported power mode values for optical transceivers

The following table lists the power mode values supported by optical transceivers and describes what each value means:

Power mode value Description
High The optics module operates in the normal power state.
Low The optics module operates in the low power state when the corresponding optics controller is shut down.

Configure admin sleep mode for optical transceivers

Reduce power consumption or disable specific optical transceivers by enabling admin sleep mode.

Admin sleep mode lets you shut down individual optics controllers to save power or prepare for maintenance. Use this process when you need the laser and power mode to be reduced for a transceiver.

Before you begin

Identify the target optics controller location in the R/S/I/P format.

Follow these steps to configure admin sleep mode for optical transceivers:

Procedure

Step 1

Execute the show controllers optics command to check the current power mode status.

Example:

Router# show controllers optics 0/0/3/0 
Fri Jun 19 07:35:45.618 UTC

 Controller State: Up 

 Transport Admin State: In Service 

 Laser State: On 
 
 Host Squelch Status: Enable 

 Media linkdown preFEC degrade : Disabled 

 LED State: Yellow 

 Power Mode: High

The current power mode is displayed as High.

Step 2

Enter global configuration mode, then optics controller configuration mode for the transceiver you want to modify.

Example:

Router# config
Router# controller optics 0/0/3/0

Step 3

Execute the shutdown to configure the administrative sleep mode.

Example:

Router(config-Optics)# shutdown
Router(config-Optics)# commit

Step 4

Run the show controllers optics command again to verify whether the current power mode status has changed..

Example:

Router# show controllers optics 0/0/3/0 
Fri Jun 19 07:44:08.730 UTC

 Controller State: Administratively Down 

 Transport Admin State: Out Of Service 

 Laser State: Off 
 
 Host Squelch Status: Enable 

 Media linkdown preFEC degrade : Disabled 

 LED State: Yellow 

 Power Mode: Low 

 Dom Data Status: Not Ready 

 Last link flapped: 00:03:52
 
 Optics Status 

         Optics Type:  QSFPDD 400G DR4
         Wavelength = 1311.00 nm 
         Loopback Host : None 
         Loopback Media : None 

         Alarm Status:
         -------------

Ensure that the power mode status is now Low and the laser state is Off.

The optical transceiver enters admin sleep mode; power mode is reduced, and laser is disabled.

What to do next

  • Confirm that the required optics controllers are shutdown.

  • Restore service by re-enabling the controller when needed.