Cisco NCS 1004 User manual

Configuring Controllers
There are three types of controllers for the line card. The controllers are the optics controller, the ethernet
controller, and the coherent DSP controller. This chapter describes the procedures used to configure these
controllers.
Unless otherwise specified, “line cards” refers to 1.2T and 1.2TL line cards.
Note
•AINS, on page 1
•FEC, on page 10
•Laser Squelching, on page 17
•Idle Insertion, on page 19
•LLDP Drop, on page 21
•Link Layer Discovery Protocol (LLDP) Support on Management Interface, on page 24
•MAC Address Snooping on Client Ports, on page 28
•Transmit Shutdown, on page 30
•Loopback, on page 32
•Restore Factory Settings, on page 38
•Headless Mode, on page 40
•Trail Trace Identifier, on page 40
•Chromatic Dispersion, on page 42
•Transmit Power, on page 43
•Frequency, on page 44
•Pseudo Random Binary Sequence, on page 45
•FlexO GID and IID, on page 51
AINS
The Automatic-In-Service (AINS) feature allows the controller to automatically move to the
automatic-in-service state after the maintenance window is completed. A soak time period is associated with
the AINS state. The controller automatically moves to the In-Service state after the soak time period is
completed. During the AINS maintenance window, alarms are not propagated to the EMS/NMS monitoring
system.
You can configure AINS on the client ports of the card.
Configuring Controllers
1

AINS States
The following table lists the AINS states.
DescriptionState
AINS is not enabled on the controller or the soak time period is complete.None
AINS is configured on the controller. However, the soak time period has
not started because either the primary state of controller is in Shutdown,
Admin down, or Not ready state or the secondary state is in Maintenance
state. AINS can also move to Pending state if alarms are raised during the
soak time period.
Pending
AINS is enabled on the controller. The primary state of the controller is
Up and the secondary state is AINS.
Running
If there are any service-affecting alarms when AINS is runring on ethernet or optics controllers, the AINS
state moves to Pending state. When the alarms are cleared, the AINS state moves to Running state.
The AINS soak time period restarts when there are line card reloads, XR reloads, line card warm reloads,
power cycles, or alarm conditioning.
Soak Time Period
You can configure the soak time period to be between 1 minute to 48 hours.
All alarms are suppressed during the AINS state. When the optical and ethernet alarms are raised on the port
during the soak time period, the AINS state moves to Pending. These alarms are not displayed in the output
of the show alarms brief card location 0/RP0/CPU0 active command but in the output of the show alarms
brief card location 0/RP0/CPU0 conditions command. When all the alarms clear, the soak time period starts,
and the AINS state moves to Running. When the soak time period expires, the port moves to IS state.
Configuring AINS
To configure AINS on a muxponder, use the following command:
configure
hw-module location location mxponder client-port-ains-soak hours hours minutes minutes
commit
The following is a sample in which all client ports are configured with AINS with soak time period specified
to be 15 minutes.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#hw-module location 0/3 mxponder client-port-ains-soak hours 0
minutes 15
RP/0/RP0/CPU0:ios(config)#commit
To configure AINS on a muxponder slice, use the following command:
configure
Configuring Controllers
2
Configuring Controllers
AINS States

hw-module location location mxponder-slice slice-number client-port-ains-soak hours hours minutes
minutes
commit
The following is a sample in which slice 0 client ports are configured with AINS with soak time period
specified to be 40 minutes.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#hw-module location 0/3 mxponder-slice 0 client-port-ains-soak
hours 0 minutes 40
RP/0/RP0/CPU0:ios(config)#commit
Disabling AINS
To disable AINS on all muxponder client ports, set the hours and minutes to 0. Use the following commands:
configure
hw-module location location mxponder client-port-ains-soak hours hours minutes minutes
commit
The following is a sample in which AINS is disabled on all client ports.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#hw-module location 0/3 mxponder client-port-ains-soak hours 0
minutes 0
RP/0/RP0/CPU0:ios(config)#commit
To disable AINS on a muxponder slice, set the hours and minutes to 0. Use the following command:
configure
hw-module location location mxponder-slice slice-number client-port-ains-soak hours hours minutes
minutes
commit
The following is a sample in which AINS is disabled on all client ports of slice 0.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#hw-module location 0/3 mxponder-slice 0 client-port-ains-soak
hours 0 minutes 0
RP/0/RP0/CPU0:ios(config)#commit
Displaying the AINS Configuration
The AINS Soak field in the output indicates the current state of AINS. The current state can be None, Pending,
or Running. The Total Duration field indicates the total soak time period that is configured. The Remaining
Duration field indicates the soak time that remains, after which, the AINS state moves to None.
This example displays the ethernet controller statistics with AINS Soak in running state.
RP/0/RP0/CPU0:ios#show controller HundredGigECtrlr 0/1/0/2
Thu Feb 21 19:52:55.001 UTC
Operational data for interface HundredGigECtrlr0/1/0/2:
State:
Configuring Controllers
3
Configuring Controllers
Disabling AINS

Administrative state: enabled
Operational state: Up
LED state: Green On
Maintenance: Disabled
AINS Soak: Running
Total Duration: 0 hour(s) 15 minute(s)
Remaining Duration: 0 hour(s) 5 minute(s) 37 second(s)
Laser Squelch: Disabled
Phy:
Media type: Not known
Autonegotiation disabled.
Operational values:
Speed: 100Gbps
Duplex: Full Duplex
Flowcontrol: None
Loopback: None (or external)
BER monitoring:
Not supported
Holdoff Time: 0ms
This example displays the ethernet controller statistics with AINS Soak in pending state.
RP/0/RP0/CPU0:ios#show controllers HuC 0/0/0/2
Thu Mar 12 13:52:12.129 UTC
Operational data for interface HundredGigECtrlr0/0/0/2:
State:
Administrative state: enabled
Operational state: Down (Reason: State undefined)
LED state: Red On
Maintenance: Disabled
AINS Soak: Pending
Total Duration: 0 hour(s) 30 minute(s)
Remaining Duration: 0 hour(s) 30 minute(s) 0 second(s)
Laser Squelch: Disabled
Phy:
Media type: Not known
Alarms:
Current:
Local Fault
Statistics:
FEC:
Corrected Codeword Count: 0
Uncorrected Codeword Count: 9
Autonegotiation disabled.
Operational values:
Speed: 100Gbps
Duplex: Full Duplex
Flowcontrol: None
Loopback: None (or external)
BER monitoring:
Not supported
Forward error correction: Standard (Reed-Solomon)
Holdoff Time: 0ms
This example displays the optics controller statistics with AINS Soak in running state.
RP/0/RP0/CPU0:ios#show controller optics 0/1/0/3
Configuring Controllers
4
Configuring Controllers
Displaying the AINS Configuration

Thu Feb 21 19:45:41.088 UTC
Controller State: Up
Transport Admin State: Automatic In Service
Laser State: On
LED State: Green
Optics Status
Optics Type: Grey optics
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 = 0
WVL-OOL = 0 MEA = 0
IMPROPER-REM = 0
TX-POWER-PROV-MISMATCH = 0
Performance Monitoring: Enable
THRESHOLD VALUES
----------------
Parameter High Alarm Low Alarm High Warning Low Warning
------------------------ ---------- --------- ------------ -----------
Rx Power Threshold(dBm) 4.9 -12.0 0.0 0.0
Tx Power Threshold(dBm) 3.5 -10.1 0.0 0.0
LBC Threshold(mA) N/A N/A 0.00 0.00
LBC High Threshold = 98 %
Polarization parameters not supported by optics
Total TX Power = 6.39 dBm
Total RX Power = 5.85 dBm
Lane Laser Bias TX Power RX Power Output Frequency
---- ---------- ---------- ---------- ----------------
1 75.0 % 0.59 dBm 0.63 dBm 230.43 THz
2 68.6 % 0.06 dBm -0.68 dBm 230.43 THz
3 69.0 % 0.26 dBm -0.63 dBm 230.43 THz
4 69.1 % 0.56 dBm -0.10 dBm 230.43 THz
Transceiver Vendor Details
Form Factor : QSFP28
Name : CISCO-FINISAR
Part Number : FTLC1152RGPL-C2
Rev Number : CISCO-FINISAR
Serial Number : FNS22150LEC
Configuring Controllers
5
Configuring Controllers
Displaying the AINS Configuration

PID : QSFP-100G-CWDM4-S
VID : V02
CISCO-FINISAR
Date Code(yy/mm/dd) : 18/04/11
Fiber Connector Type: LC
Sonet Application Code: Not Set
Ethernet Compliance Code: 100GBASE-CWDM4
Transceiver Temperature : 32 Celsius
AINS Soak : Running
AINS Timer : 0h, 15m
AINS remaining time : 771 seconds
When the soak time expires, AINS state changes from Running to None. The Transport Admin State of optics
controller changes from Automatic In Service to In Service.
RP/0/RP0/CPU0:ios# show controllers optics 0/1/0/3
Thu Feb 21 20:02:34.126 UTC
Controller State: Up
Transport Admin State: In Service
Laser State: On
LED State: Green
Optics Status
Optics Type: Grey optics
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 = 0
WVL-OOL = 0 MEA = 0
IMPROPER-REM = 0
TX-POWER-PROV-MISMATCH = 0
Performance Monitoring: Enable
THRESHOLD VALUES
----------------
Parameter High Alarm Low Alarm High Warning Low Warning
------------------------ ---------- --------- ------------ -----------
Rx Power Threshold(dBm) 4.9 -12.0 0.0 0.0
Tx Power Threshold(dBm) 3.5 -10.1 0.0 0.0
LBC Threshold(mA) N/A N/A 0.00 0.00
Configuring Controllers
6
Configuring Controllers
Displaying the AINS Configuration

LBC High Threshold = 98 %
Polarization parameters not supported by optics
Total TX Power = 6.41 dBm
Total RX Power = 5.85 dBm
Lane Laser Bias TX Power RX Power Output Frequency
---- ---------- ---------- ---------- ----------------
1 74.9 % 0.60 dBm 0.63 dBm 230.43 THz
2 68.6 % 0.06 dBm -0.70 dBm 230.43 THz
3 69.0 % 0.30 dBm -0.63 dBm 230.43 THz
4 69.1 % 0.57 dBm -0.11 dBm 230.43 THz
Transceiver Vendor Details
Form Factor : QSFP28
Name : CISCO-FINISAR
Part Number : FTLC1152RGPL-C2
Rev Number : CISCO-FINISAR
Serial Number : FNS22150LEC
PID : QSFP-100G-CWDM4-S
VID : V02
CISCO-FINISAR
Date Code(yy/mm/dd) : 18/04/11
Fiber Connector Type: LC
Sonet Application Code: Not Set
Ethernet Compliance Code: 100GBASE-CWDM4
Transceiver Temperature : 32 Celsius
AINS Soak : None
AINS Timer : 0h, 0m
AINS remaining time : 0 seconds
Configuring AINS on OTN-XP Card
You can configure the default AINS settings for all controllers on the OTN-XP card using the shared plane
configuration. The configuration is applied to any line card that is installed in the NCS 1004. Use the following
commands:
configure
ains-soak hours hours minutes minutes
commit
The following is a sample in which all the controllers on the OTN-XP card are configured with AINS with
soak time period specified to be two minutes.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#ains-soak hours 0 minutes 2
RP/0/RP0/CPU0:ios(config)#commit
RP/0/RP0/CPU0:ios(config)#do show controllers optics 0/1/0/0
Tue Apr 28 11:50:15.431 UTC
Controller State: Down
Transport Admin State: Automatic In Service
Configuring Controllers
7
Configuring Controllers
Configuring AINS on OTN-XP Card

Laser State: On
LED State: Red
Optics Status
Optics Type: 100G QSFP28 LR4
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 = 0
WVL-OOL = 0 MEA = 0
IMPROPER-REM = 0
TX-POWER-PROV-MISMATCH = 0
Performance Monitoring: Enable
THRESHOLD VALUES
----------------
Parameter High Alarm Low Alarm High Warning Low Warning
------------------------ ---------- --------- ------------ -----------
Rx Power Threshold(dBm) 4.9 -12.0 0.0 0.0
Tx Power Threshold(dBm) 3.5 -10.1 0.0 0.0
LBC Threshold(mA) N/A N/A 0.00 0.00
LBC High Threshold = 98 %
Polarization parameters not supported by optics
Total TX Power = 7.74 dBm
Total RX Power = -40.00 dBm
Lane Laser Bias TX Power RX Power Output Frequency
---- ---------- ---------- ---------- ----------------
1 67.2 % 1.85 dBm -40.00 dBm 231.39 THz
2 67.9 % 1.55 dBm -40.00 dBm 230.59 THz
3 67.5 % 1.58 dBm -40.00 dBm 229.79 THz
4 66.8 % 1.89 dBm -40.00 dBm 230.25 THz
Transceiver Vendor Details
Form Factor : QSFP28
Name : CISCO-FINISAR
Part Number : 10-3204-01
Rev Number : B
Serial Number : FNS20510YUB
PID : ONS-QSFP28-LR4
VID : V01
Date Code(yy/mm/dd) : 16/12/15
Fiber Connector Type: LC
Otn Application Code: 4I1-9D1F
Sonet Application Code: Not Set
Configuring Controllers
8
Configuring Controllers
Configuring AINS on OTN-XP Card

Ethernet Compliance Code: 100GBASE-LR4
Transceiver Temperature : 27 Celsius
AINS Soak : Pending
AINS Timer : 0h, 2m
AINS remaining time : 120 seconds
To override the default AINS settings on a specific controller, use the following commands:
automatic-in-service controller optics R/S/I/P hours hours minutes minutes
This configuration does not persist after a RP reload operation.
Note
The following is a sample in which the optics controller on the OTN-XP card is configured with a soak time
period of 45 minutes.
RP/0/RP0/CPU0:ios#automatic-in-service controller optics 0/1/0/0 hours 0 minutes 45
Tue Apr 28 11:55:15.666 UTC
RP/0/RP0/CPU0:ios#show controllers optics 0/1/0/0
Tue Apr 28 11:55:30.323 UTC
Controller State: Down
Transport Admin State: Automatic In Service
Laser State: On
LED State: Red
Optics Status
Optics Type: 100G QSFP28 LR4
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 = 0
WVL-OOL = 0 MEA = 0
IMPROPER-REM = 0
TX-POWER-PROV-MISMATCH = 0
Performance Monitoring: Enable
THRESHOLD VALUES
----------------
Parameter High Alarm Low Alarm High Warning Low Warning
Configuring Controllers
9
Configuring Controllers
Configuring AINS on OTN-XP Card

------------------------ ---------- --------- ------------ -----------
Rx Power Threshold(dBm) 4.9 -12.0 0.0 0.0
Tx Power Threshold(dBm) 3.5 -10.1 0.0 0.0
LBC Threshold(mA) N/A N/A 0.00 0.00
LBC High Threshold = 98 %
Polarization parameters not supported by optics
Total TX Power = 7.74 dBm
Total RX Power = -40.00 dBm
Lane Laser Bias TX Power RX Power Output Frequency
---- ---------- ---------- ---------- ----------------
1 67.2 % 1.85 dBm -40.00 dBm 231.39 THz
2 67.9 % 1.55 dBm -40.00 dBm 230.59 THz
3 67.5 % 1.58 dBm -40.00 dBm 229.79 THz
4 66.8 % 1.89 dBm -40.00 dBm 230.25 THz
Transceiver Vendor Details
Form Factor : QSFP28
Name : CISCO-FINISAR
Part Number : 10-3204-01
Rev Number : B
Serial Number : FNS20510YUB
PID : ONS-QSFP28-LR4
VID : V01
Date Code(yy/mm/dd) : 16/12/15
Fiber Connector Type: LC
Otn Application Code: 4I1-9D1F
Sonet Application Code: Not Set
Ethernet Compliance Code: 100GBASE-LR4
Transceiver Temperature : 27 Celsius
AINS Soak : Pending
AINS Timer : 0h, 45m
AINS remaining time : 2700 seconds
FEC
Forward error correction (FEC) is a feature that is used for controlling errors during data transmission. This
feature works by adding data redundancy to the transmitted message using an algorithm. This redundancy
allows the receiver to detect and correct a limited number of errors occurring anywhere in the message, instead
of having to ask the transmitter to resend the message.
FEC States for Ethernet Controller
The following table lists the FEC states for the Ethernet controller.
DescriptionState
FEC is not enabled on the Ethernet controller.None
Configuring Controllers
10
Configuring Controllers
FEC

DescriptionState
Standard (Reed-Solomon) FEC is enabled on the
Ethernet controller.
Standard
FEC configuration is automatically enabled for only the pluggables that support Auto-FEC. If you manually
configure FEC, the manual configuration overrides the Auto-FEC.
The supported pluggables for Auto-FEC are:
• QSFP-100G-SR4-S
• QSFP-100G-CWDM4-S
• QSFP-100G-SM-SR
• QSFP-100G-AOC-1M
• QSFP-100G-AOC-3M
• QSFP-100G-AOC-10M
• QDD-400-AOC15M
• QDD-400G-FR4-S
• QSFP-100G-ER4L
The LR4 pluggable is a 1310nm long range band pluggable that does not require you to enable FEC.
The software automatically enables FEC mode on the pluggables installed in the Cisco NCS 1004. When you
upgrade the software of an NCS 1004 with pluggables in the FEC disabled mode, traffic is affected.
The following sample shows the running FEC configuration on the LR4 pluggable:
RP/0/RP0/CPU0:ios#show controller HundredGigECtrlr 0/0/0/4
Thu Aug 8 15:41:20.857 IST
Operational data for interface HundredGigECtrlr0/0/0/4:
State:
Administrative state: enabled
Operational state: Up
LED state: Green On
Maintenance: Disabled
AINS Soak: None
Total Duration: 0 hour(s) 0 minute(s)
Remaining Duration: 0 hour(s) 0 minute(s) 0 second(s)
Laser Squelch: Enabled
Phy:
Media type: Not known
Autonegotiation disabled.
Operational values:
Speed: 100Gbps
Duplex: Full Duplex
Flowcontrol: None
Loopback: None (or external)
BER monitoring:
Not supported
Configuring Controllers
11
Configuring Controllers
FEC States for Ethernet Controller

Holdoff Time: 0ms
The following sample shows the running FEC configuration on the non LR4 pluggable:
RP/0/RP0/CPU0:ios#show controller HundredGigECtrlr 0/0/0/2
Thu Aug 8 15:41:56.457 IST
Operational data for interface HundredGigECtrlr0/0/0/2:
State:
Administrative state: enabled
Operational state: Up
LED state: Green On
Maintenance: Disabled
AINS Soak: None
Total Duration: 0 hour(s) 0 minute(s)
Remaining Duration: 0 hour(s) 0 minute(s) 0 second(s)
Laser Squelch: Disabled
Phy:
Media type: Not known
Statistics:
FEC:
Corrected Codeword Count: 0
Uncorrected Codeword Count: 66
Autonegotiation disabled.
Operational values:
Speed: 100Gbps
Duplex: Full Duplex
Flowcontrol: None
Loopback: None (or external)
BER monitoring:
Not supported
Forward error correction: Standard (Reed-Solomon)
Holdoff Time: 0ms
Configuring FEC on the Ethernet Controller
The FEC configuration is not required for the supported pluggables. The configuration is required only in the
case of non-Cisco qualified non-LR4 pluggables.
Note
To configure FEC on the Ethernet controller, use the following command:
configure
controller HundredGigECtrlr R/S/I/P fec { none | standard }
commit
The following sample shows how to configure FEC on the Ethernet controller:
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller HundredGigECtrlr 0/1/0/10 fec standard
RP/0/RP0/CPU0:ios(config)#commit
Configuring Controllers
12
Configuring Controllers
Configuring FEC on the Ethernet Controller

The following sample shows the running FEC configuration on the Ethernet controller:
RP/0/RP0/CPU0:BH-SIT2#show controller HundredGigECtrlr 0/1/0/10
Tue Jul 16 15:30:30.165 IST
Operational data for interface HundredGigECtrlr0/1/0/10:
State:
Administrative state: enabled
Operational state: Down (Reason: State undefined)
LED state: Red On
Maintenance: Disabled
AINS Soak: None
Total Duration: 0 hour(s) 0 minute(s)
Remaining Duration: 0 hour(s) 0 minute(s) 0 second(s)
Laser Squelch: Disabled
Phy:
Media type: Not known
Alarms:
Current:
Loss of Frequency Sync Data
Statistics:
FEC:
Corrected Codeword Count: 0
Uncorrected Codeword Count: 0
Autonegotiation disabled.
Operational values:
Speed: 100Gbps
Duplex: Full Duplex
Flowcontrol: None
Loopback: None (or external)
BER monitoring:
Not supported
Forward error correction: Standard (Reed-Solomon)
Holdoff Time: 0ms
FEC States for CoherentDSP Controller
The following table lists the FEC states for the coherentDSP controllers.
Table 1: FEC State for CoherentDSP Controllers
DescriptionState
FEC Soft-Decision 15.EnhancedSD15
FEC Soft-Decision 27. Default.EnhancedSD27
Q-Margin Support
Q-margin is an important optical parameter that characterizes the health of an optical link. The Q-margin
value is calculated based on the average bit error rate (BER) in the optical link.
Configuring Controllers
13
Configuring Controllers
FEC States for CoherentDSP Controller

Table 2: Feature History
DescriptionRelease InformationFeature Name
Enhanced Q-Margin is supported
for Forward error correction (FEC)
and performance monitoring on
CoherentDSP Controllers for 1.2T
and 1.2TL cards. This enhanced
Q-margin value is calculated based
on the maximum number of errors
for each frame. An attribute that is
called instantaneous Q-margin is
displayed in the output of the show
controllers coherentDSP
command. The lower the delta
value between the instantaneous
Q-margin value with the Q-margin
value, the better the FEC
performance of the NCS 1004
system. The instantaneous
Q-margin values thus help you to
optimize the system with
continuous error correction in
subsea transport networks.
Command modified:
•show controllers
coherentDSP
Cisco IOS XR Release 7.3.1Enhanced Q-Margin Support
Enhanced Q-Margin Support
From Release 7.3.1 onwards, enhanced Q-Margin is supported for Forward error correction (FEC) and
performance monitoring on CoherentDSP controllers for 1.2T and 1.2TL cards. Enhanced Q-margin provides
a better error free signal in the optical link. The enhanced Q-margin value is calculated based on the maximum
number of errors per frame. An attribute that is called instantaneous Q-margin is displayed in the output of
the showcontrollerscoherentDSP command. The lower the delta value between the instantaneous Q-margin
value with the Q-margin value, the better the FEC performance of the NCS 1004 system.
To view Q-margin and enhanced Q-margin values for FEC on CoherentDSP controllers, see Verifying FEC
on CoherentDSP Controllers, on page 15.
To view Q-margin and enhanced Q-margin values for performance monitoring on CoherentDSP controllers,
see Configuring PM Parameters.
Configuring FEC on CoherentDSP Controllers
To configure FEC on the CoherentDSP controller, use the following command:
configure
controller coherentDSP R/S/I/P
Configuring Controllers
14
Configuring Controllers
Configuring FEC on CoherentDSP Controllers

fec {EnhancedSD15 |EnhancedSD27}
commit
The following sample shows how to configure FEC on the CoherentDSP controller:
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller coherentDSP 0/0/0/0
RP/0/RP0/CPU0:ios(config-CoDSP)#fec EnhancedSD15
Tue Feb 25 11:25:52.670 UTC
WARNING! Changing FEC mode can impact traffic
RP/0/RP0/CPU0:ios(config-CoDSP)#commit
Verifying FEC on CoherentDSP Controllers
The following sample shows the FEC configuration on the CoherentDSP controller:
RP/0/RP0/CPU0:ios#show controllers coherentDSP 0/0/0/0
Tue Feb 25 11:26:08.235 UTC
Port : CoherentDSP 0/0/0/0
Controller State : Up
Inherited Secondary State : Normal
Configured Secondary State : Normal
Derived State : In Service
Loopback mode : None
BER Thresholds : SF = 1.0E-5 SD = 1.0E-7
Performance Monitoring : Enable
Bandwidth : 50.0Gb/s
Alarm Information:
LOS = 1 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
Detected Alarms : None
Bit Error Rate Information
PREFEC BER : 0.00E+00
POSTFEC BER : 0.00E+00
Q-Factor : 0.00 dB
Q-Margin : -5.00dB
Instantaneous Q_margin : 0 dB
TTI :
Remote IP addr : 0.0.0.0
FEC mode : Soft-Decision 15
AINS Soak : None
AINS Timer : 0h, 0m
AINS remaining time : 0 seconds
Configuring FEC on OTN-XP Card
FEC is supported on the CoherentDSP controllers for the OTN-XP card and O-FEC is the default FEC option
configured on the card.
Configuring Controllers
15
Configuring Controllers
Verifying FEC on CoherentDSP Controllers

From Release 7.3.1 onwards, CFP2-DCO trunk is configured with 0-FEC.
The options enhanced SD15 and SD17 are not supported on the OTN-XP card.
Note
To configure FEC on the CoherentDSP controller for the OTN-XP card, use the following command:
configure
controller coherentDSP R/S/I/P
fec OFEC
commit
The following sample shows how to configure O-FEC option on the CoherentDSP controller for the OTN-XP
card:
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller coherentDSP 0/0/0/0
RP/0/RP0/CPU0:ios(config-CoDSP)#fec OFEC
Tue Feb 25 11:25:52.670 UTC
WARNING! Changing FEC mode can impact traffic
RP/0/RP0/CPU0:ios(config-CoDSP)#commit
Verifying FEC on OTN-XP Card
The following sample shows the FEC configuration on the CoherentDSP controller for the OTN-XP card:
RP/0/RP0/CPU0:ios#show controllers coherentDSP 0/0/0/0
Tue Feb 25 11:26:08.235 UTC
Port : CoherentDSP 0/0/0/0
Controller State : Up
Inherited Secondary State : Normal
Configured Secondary State : Normal
Derived State : In Service
Loopback mode : None
BER Thresholds : SF = 1.0E-5 SD = 1.0E-7
Performance Monitoring : Enable
Bandwidth : 50.0Gb/s
Alarm Information:
LOS = 1 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
Detected Alarms : None
Bit Error Rate Information
PREFEC BER : 0.00E+00
POSTFEC BER : 0.00E+00
Q-Factor : 0.00 dB
Q-Margin : -5.00dB
Instantaneous Q_margin : 0 dB
TTI :
Remote IP addr : 0.0.0.0
Configuring Controllers
16
Configuring Controllers
Verifying FEC on OTN-XP Card

FEC mode : O-FEC
AINS Soak : None
AINS Timer : 0h, 0m
AINS remaining time : 0 seconds
Laser Squelching
You can enable laser squelching on ethernet controllers. When laser squelching is enabled, the laser is shut
down in the event of trunk faults (LOS, LOF) and a SQUELCHED alarm is raised.
To configure laser squelching on the ethernet controllers, use the following commands:
configure
controller HundredGigECtrlr Rack/Slot/Instance/Port
laser-squelch
commit
The following is a sample where laser squelching is enabled on the ethernet controller.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller HundredGigECtrlr 0/1/0/10
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#laser-squelch
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#commit
The following is a sample to view the laser squelch status on the controller.
RP/0/RP0/CPU0:ios#show controller HundredGigECtrlr 0/1/0/10
Fri Feb 22 15:18:47.011 UTC
Operational data for interface HundredGigECtrlr0/1/0/10:
State:
Administrative state: enabled
Operational state: Up
LED state: Green On
Maintenance: Disabled
AINS Soak: None
Total Duration: 0 hour(s) 0 minute(s)
Remaining Duration: 0 hour(s) 0 minute(s) 0 second(s)
Laser Squelch: Enabled
Phy:
Media type: Not known
Statistics:
FEC:
Corrected Codeword Count: 0
Uncorrected Codeword Count: 0
Autonegotiation disabled.
Operational values:
Speed: 100Gbps
Duplex: Full Duplex
Flowcontrol: None
Loopback: None (or external)
BER monitoring:
Not supported
Configuring Controllers
17
Configuring Controllers
Laser Squelching

Forward error correction: Standard (Reed-Solomon)
Holdoff Time: 0ms
Configuring Laser Squelching on OTN-XP Card
From R7.2.1 onwards, laser squelching is supported on 10GE controllers for the OTN-XP card.
To configure laser squelching on the 10GE controllers for the OTN-XP card, use the following commands:
configure
controller tenGigECtrlr Rack/Slot/Instance/Port/Lanenumber
laser-squelch
commit
The range of Lanenumber is from 1 to 4.
The following is a sample where laser squelching is enabled on the 10GE controller for the OTN-XP card.
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller tenGigECtrlr 0/0/0/4/1
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#laser-squelch
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#commit
The following is a sample to view the laser squelch status on the 10GE controller.
P/0/RP0/CPU0:ios#show controllers tenGigECtrlr 0/0/0/4/1
Wed May 6 06:28:29.603 UTC
Operational data for interface TenGigECtrlr0/0/0/4/1:
State:
Administrative state: enabled
Operational state: Up
LED state: Red On
Maintenance: Disabled
AINS Soak: None
Total Duration: 0 hour(s) 0 minute(s)
Remaining Duration: 0 hour(s) 0 minute(s) 0 second(s)
Laser Squelch: Enabled
Phy:
Media type: Not known
Autonegotiation disabled.
Operational values:
Speed: 10Gbps
Duplex: Full Duplex
Flowcontrol: None
Loopback: None (or external)
Inter-packet gap: standard (12)
BER monitoring:
Not supported
Holdoff Time: 0ms
Configuring Controllers
18
Configuring Controllers
Configuring Laser Squelching on OTN-XP Card

Idle Insertion
When a fault occurs on the trunk port, you can hold the propagation of local faults using the idle insertion
feature. This feature is enabled on the ethernet controller by configuring the hold-off timer.
When the fault occurs on the trunk, idles are inserted in the traffic stream from the trunk port to the client port
for the duration of the configured holdoff-time. If the trunk port remains faulty beyond the configured
holdoff-time, a local fault is transmitted towards the client device. If the trunk recovers from the fault before
the holdoff-time expires, traffic resumes.
This feature can be used on customer deployments to prevent reset of client ports during a PSM switchover.
You can enable the idle insertion feature by using the following commands:
configure
controller HundredGigECtrlr Rack/Slot/Instance/Port
holdoff-time trunk-fault time-value
The range of timevalue is from 0 ms to 3000 ms.
The following is a sample for enabling the hold off -timer in 100GE controllers:
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller HundredGigECtrlr 0/1/0/10
RP/0/RP0/CPU0:ios (config-eth-ctrlr)#holdoff-time trunk-fault 3000
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#commit
To view the hold-off time that is configured on 100GE controller, use the following command:
show controllers hundredGigECtrlr Rack/Slot/Instance/Port
Example
RP/0/RP0/CPU0:ios#show controllers HundredGigECtrlr 0/1/0/10
Fri Feb 22 18:58:06.888 UTC
Operational data for interface HundredGigECtrlr0/1/0/10:
State:
Administrative state: enabled
Operational state: Up
LED state: Green On
Maintenance: Disabled
AINS Soak: None
Total Duration: 0 hour(s) 0 minute(s)
Remaining Duration: 0 hour(s) 0 minute(s) 0 second(s)
Laser Squelch: Enabled
Phy:
Media type: Not known
Statistics:
FEC:
Corrected Codeword Count: 0
Uncorrected Codeword Count: 0
Autonegotiation disabled.
Operational values:
Speed: 100Gbps
Duplex: Full Duplex
Flowcontrol: None
Loopback: None (or external)
Configuring Controllers
19
Configuring Controllers
Idle Insertion

BER monitoring:
Not supported
Forward error correction: Standard (Reed-Solomon)
Holdoff Time: 3000ms
Enabling Idle Insertion on OTN-XP Card
From R7.2.1 onwards, you can enable the idle insertion feature on the 10GE controller for OTN-XP card.
To enable idle insertion on the 10GE controller, enter the following commands:
configure
controller tenGigECtrlr Rack/Slot/Instance/Port/Lanenumber
holdoff-time trunk-fault time-value
commit
The range of Lanenumber is from 1 to 4 and the range of holdoff-time trunk-fault time-value is from 0 to 3000
ms.
The following is a sample for enabling the idle insertion feature in 10GE controllers:
RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller tenGigECtrlr 0/0/0/4/1
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#holdoff-time trunk-fault 2000
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#commit
To view the hold-off time that is configured on 10GE controllers, use the following command:
show controllers tenGigECtrlr Rack/Slot/Instance/Port/Lanenumber
Example
RP/0/RP0/CPU0:ios#show controllers TenGigECtrlr 0/0/0/4/1
Thu Mar 26 12:46:16.543 UTC
Operational data for interface TenGigECtrlr0/0/0/4/1:
State:
Administrative state: enabled
Operational state: Up
LED state: Green On
Maintenance: Disabled
AINS Soak: None
Total Duration: 0 hour(s) 0 minute(s)
Remaining Duration: 0 hour(s) 0 minute(s) 0 second(s)
Laser Squelch: Disabled
Phy:
Media type: Not known
Autonegotiation disabled.
Operational values:
Speed: 10Gbps
Duplex: Full Duplex
Flowcontrol: None
Loopback: None (or external)
Inter-packet gap: standard (12)
BER monitoring:
Not supported
Holdoff Time: 2000ms
Configuring Controllers
20
Configuring Controllers
Enabling Idle Insertion on OTN-XP Card