The following table lists the AINS states.

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.

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.

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

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

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

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:
    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

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
         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

         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

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 
 
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                                           
         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

Note	This configuration does not persist after an RP reload operation.

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
         ------------------------  ----------  ---------  ------------  -----------
         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                                            

RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#automatic-in-service controller SixteenGigFibreChanCtrlr  0/0/0/6/2 hours 0 minutes 15
RP/0/RP0/CPU0:ios(config)#commit

 show controllers SixteenGigFibreChanCtrlr 0/0/0/6/2 on XR

+++ 15:04:25 ne(default) exec +++
show controllers SixteenGigFibreChanCtrlr 0/0/0/6/2

Wed Apr 13 15:04:25.206 UTC

Operational data for Fibre Channel controller SixteenGigFibreChanCtrlr0/0/0/6/2

State:
        Admin State           : Up
        Operational state     : Up
        LED state             : Green On
        Secondary admin state : Automatic In Service
        AINS Soak             : Running
            Total Duration    : 0 hour(s) 15 minute(s)
            Remaining Duration: 0 hour(s) 14 minute(s) 29 second(s)
        Laser Squelch         : Disabled

Performance Monitoring is enabled

Operational values:
        Speed                    : 16 Gbps
        Loopback                 : None
        BER monitoring:
            Not supported
        Hold-off Time            : 0 ms
        Forward Error Correction : Not Configured

RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#automatic-in-service controller ThirtyTwoGigFibreChanCtrlr  0/0/0/0/4 hours 0 minutes 15
RP/0/RP0/CPU0:ios(config)#commit

 show controllers ThirtyTwoGigFibreChanCtrlr 0/0/0/0/4 on XR

+++ 15:04:25 ne(default) exec +++
show controllers ThirtyTwoGigFibreChanCtrlr 0/0/0/0/4

Wed Apr 13 15:04:25.393 UTC

Operational data for Fibre Channel controller ThirtyTwoGigFibreChanCtrlr0/0/0/0/4

State:
        Admin State           : Up
        Operational state     : Up
        LED state             : Green On
        Secondary admin state : Automatic In Service
        AINS Soak             : Running
            Total Duration    : 0 hour(s) 15 minute(s)
            Remaining Duration: 0 hour(s) 14 minute(s) 29 second(s)
        Laser Squelch         : Disabled

Performance Monitoring is enabled

Operational values:
        Speed                    : 32 Gbps
        Loopback                 : None
        BER monitoring:
            Not supported
        Hold-off Time            : 0 ms
        Forward Error Correction : Standard(Reed Solomon)

RP/0/RP0/CPU0:ne#

RP/0/RP0/CPU0:ios#automatic-in-service controller coherentDSP 0/0/0/12 hours 0 minutes 15
Tue May 24 17:51:06.979 UTC

RP/0/RP0/CPU0:ios#show controllers coherentDSP 0/0/0/12
Tue May 24 17:52:29.558 UTC

Port                                            : CoherentDSP 0/0/0/12
Controller State                                : Up
Inherited Secondary State                       : Automatic-In-Service
Configured Secondary State                      : Automatic-In-Service
Derived State                                   : Automatic-In-Service
Loopback mode                                   : None
BER Thresholds                                  : SF = 1.0E-5  SD = 1.0E-7
Performance Monitoring                          : Enable
Bandwidth                                       : 400.0Gb/s

Alarm Information:
LOS = 0 LOF = 0 LOM = 0
OOF = 4 OOM = 0 AIS = 3
IAE = 0 BIAE = 0        SF_BER = 0
SD_BER = 0      BDI = 3 TIM = 1
FECMISMATCH = 0 FEC-UNC = 0     FLEXO_GIDM = 2
FLEXO-MM = 0    FLEXO-LOM = 0   FLEXO-RDI = 2
FLEXO-LOF = 0
Detected Alarms                                 : None

Bit Error Rate Information
PREFEC  BER                                     : 1.42E-04
POSTFEC BER                                     : 0.00E+00
Q-Factor                                        : 11.10 dB

Q-Margin                                        : 4.60dB

TTI :
        Remote hostname                         : ios
        Remote interface                        : CoherentDSP 0/0/0/12
        Remote IP addr                          : 0.0.0.0

FEC mode                                        : O_FEC

Flexo-Mode                                      : Enable
Flexo Details:
        Tx GID                                  : 10
        TX IID                                  : 1, 2, 3, 4,
        Rx GID                                  : 10
        RX IID                                  : 1, 2, 3, 4,

AINS Soak                                       : Running
AINS Timer                                      : 0h, 15m
AINS remaining time                             : 855 seconds

RP/0/RP0/CPU0:ios#configure terminal
Tue May 24 17:51:34.545 UTC
RP/0/RP0/CPU0:ios(config)#ains-soak hours 0 minutes 15
RP/0/RP0/CPU0:ios(config)#commit
Tue May 24 17:51:44.144 UTC

RP/0/RP0/CPU0:ios#show controllers optics 0/0/0/12
Tue May 24 17:52:34.445 UTC

Controller State: Up

Transport Admin State: Automatic In Service

Laser State: On

LED State: Green

Optics Status

         Optics Type:  CFP2 DWDM
         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 = 1
         WVL-OOL = 0                MEA  = 0
         IMPROPER-REM = 0
         TX-POWER-PROV-MISMATCH = 0
         Laser Bias Current = 0.0 %
         Actual TX Power = 0.47 dBm
         RX Power = 0.40 dBm
         RX Signal Power = 0.30 dBm
         Frequency Offset = -1358 MHz

         Performance Monitoring: Enable

         THRESHOLD VALUES
         ----------------

         Parameter                 High Alarm  Low Alarm  High Warning  Low Warning
         ------------------------  ----------  ---------  ------------  -----------
         Rx Power Threshold(dBm)          3.0      -25.5           0.0          0.0
         Tx Power Threshold(dBm)          3.0      -12.0           0.0          0.0
         LBC Threshold(mA)                N/A        N/A          0.00         0.00

         LBC High Threshold = 90 %
         Configured Tx Power = 0.50 dBm
         Configured CD High Threshold = 48000 ps/nm
         Configured CD lower Threshold = -48000 ps/nm
         Configured OSNR lower Threshold = 22.00 dB
         Configured DGD Higher Threshold = 67.00 ps
         Baud Rate =  63.1394679230 GBd
         Bits per Symbol = 4.0000000000  bits/symbol
         Modulation Type: 16QAM
         Chromatic Dispersion -1 ps/nm
         Configured CD-MIN -24000 ps/nm  CD-MAX 24000 ps/nm
         Polarization Mode Dispersion = 0.0 ps
         Second Order Polarization Mode Dispersion = 52.00 ps^2
         Optical Signal to Noise Ratio = 35.90 dB
         SNR = 19.40 dB
         Polarization Dependent Loss = 1.70 dB
         Polarization Change Rate = 0.00 rad/s
         Differential Group Delay = 2.00 ps
         DAC RATE:  1x1.50

Transceiver Vendor Details

         Form Factor            : CFP2
         Name                   : CISCO-ACACIA
         Part Number            : 10-3555-01
         Rev Number             : A0
         Serial Number          : ACA25420007
         PID                    : DP04CFP2-M25-K9
         VID                    : VES1
         Date Code(yy/mm/dd)    : 21/09/28
         Fiber Connector Type: LC
         Otn Application Code: Not Set
         Sonet Application Code: Not Set
         Ethernet Compliance Code: Not set

Transceiver Temperature : 41 Celsius



AINS Soak                : Running
AINS Timer               : 0h, 15m
AINS remaining time      : 850 seconds

The following table lists the FEC states for the Ethernet controller.

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

• QDD-400G-DR4-S

• QDD-400G-LR8-S

• QDD-4X100G-LR-S

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
    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
 

Note	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.

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

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

The following table lists the FEC states for the coherentDSP controllers.

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.

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 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.

To view Q-margin and enhanced Q-margin values for FEC on CoherentDSP controllers, see Verifying FEC on CoherentDSP Controllers.

To view Q-margin and enhanced Q-margin values for performance monitoring on CoherentDSP controllers, see Configuring PM Parameters.

To configure FEC on the CoherentDSP controller, use the following command:

configure

controller coherentDSP R/S/I/P

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

FEC is supported on the CoherentDSP controllers for the OTN-XP card and O-FEC is the default FEC option configured on the card.

From Release 7.3.1 onwards, CFP2-DCO trunk is configured with 0-FEC.

Note	The options enhanced SD15 and SD17 are not supported on the OTN-XP card.

Note	CFEC is not supported on CFP2-DCO.

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

Fast-Squelching provides increased protection switching speed when there’s a trunk fault or a client fault.

The following sample topology includes a Far End (FE) station and a Near End (NE) station. Each station includes an NCS 1004 node having two line cards. The nodes are connected to the respective Traffic generators through a Protection Switching Module (PSM).

Protection Switching Principle (Trunk fault)

If there is a fiber cut in the trunk working path from the FE station to the NE station, an LOS alarm is raised on the NE working trunk. This results in the squelching of all client ports mapped to the working NE trunk port. As the laser of the client port is squelched, LOS is reported on the W-RX2 port of the PSM2. As the received optical power on the W-RX2 port of PSM is below the threshold, PSM2 switches to receive the optical signal in the P-RX2 port instead of the W-RX2 port. Hence switching happens for traffic from work to protect in FE station to NE station direction. In this way, bidirectional switching is implemented.

In the case of a unidirectional trunk fault, switching happens in one direction as explained above. In the other direction, when LOS is received at the W-RX2 port of PSM2, W-TX2 sends LOS for 25 milliseconds. When LOS is reported on the NE client port, fault gets propagated over the trunk, resulting in the squelching of FE station client ports. Finally, the LOS on the PSM port results in switching in this direction as well.

Protection Switching Principle (Client fault)

When a client failure happens on the FE station, a Client Signal Failure (CSF) alarm is raised on the NE station trunk. The CSF on the trunk results in the squelching of the corresponding client port, and the PSM switching happens. In summary, a fault on the NE station client RX port results in CSF on the FE station trunk, and the switching happens. And, a fault on the NE station client TX port results in LOS on the PSM ports, and the switching happens.

Note

PSM must be in the standalone mode. PSM alarm threshold must be set to +/ –3 dBm from the actual power received in the PSM RX port. If line card protection is required, the working and protect path must be configured in two different line cards. If only client protection is required, the working and protection path can be configured in the same line card. If the LC trunk configuration is x50 rate, then we can’t use a single-line card for work and protection due to x50 coupled mode limitations (coupled trunk). Manual switch, Force switch, and lock-out protection on PSM, result in bidirectional switching.

The PSM supports both C2B (4x100G-MXP-400G-TXP) and C3B (40x10G-4x100G-MXP) cards. The C2B card allows client data rates of 100G and 400G, while the C3B card supports client data rates of 10G and 100G. The PSM supports upto 400G with the GL-2 pluggable module.

The PAM4 and QDD pluggable modules take more than 50ms to recover traffic when switching between working and protection modes.

The GL-2 DP04CFP2-M25-K9 pluggable module supports both Flexcoh streaming and ODUCn termination modes. Compared to Flexcoh streaming mode, the ODUCn termination mode with chromatic dispersion configuration of +/- 10000 has a shorter switching time.

The following table lists 400G client pluggables that do not support switching from the active path to the protection path within 50 milliseconds:

Note

According to the QDD pluggable standard, if an electrical (TP1) or optical (TP3) signal is interrupted or disturbed at a client pluggable, and the Clock and Data Recovery (CDR) inside the QDD loses the lock, the QDD pluggable requires some time to recover the signal. Hence, when a fault is identified on the trunk port, the client port Rx loses the lock. The recovery takes between 1.5 to 2 seconds depending on the pluggable standard.

From R7.2.1 onwards, laser squelching is supported on 10GE controllers for the OTN-XP card.

From R7.3.1 onwards, laser squelching is supported on 100GE or 400GE controllers for the OTN-XP card.

From Release 7.5.2 onwards, laser squelching is supported on the 16G FC and 32G FC controllers 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

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: 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: 10Gbps
Duplex: Full Duplex
Flowcontrol: None
Loopback: None (or external)
Inter-packet gap: standard (12)
BER monitoring:
Not supported
Holdoff Time: 0ms

RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller HundredGigECtrlr 0/0/0/1
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#laser-squelch
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#commit

RP/0/RP0/CPU0:ios#show controller hundredGigECtrlr 0/0/0/1
Fri Jul 23 16:07:11.541 UTC
Operational data for interface HundredGigECtrlr0/0/0/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: Enabled

Phy:
    Media type: Not known
Statistics:
FEC:
Corrected Codeword Count: 134967789
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

RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller fourHundredGigECtrlr 0/0/0/8
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#laser-squelch
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#commit

RP/0/RP0/CPU0:ios#show controller fourhundredGigECtrlr 0/0/0/8
Fri Jul 23 16:07:11.541 UTC
Operational data for interface fourHundredGigECtrlr0/0/0/8:

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: 134967789
Uncorrected Codeword Count: 0
Autonegotiation disabled.

Operational values:
    Speed: 400Gbps
    Duplex: Full Duplex
    Flowcontrol: None
    Loopback: None (or external)
    BER monitoring:
        Not supported
    Forward error correction: Standard (Reed-Solomon)
    Holdoff Time: 0ms

RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller SixteenGigFibreChanCtrlr 0/1/0/0/2 laser-squelch
RP/0/RP0/CPU0:ios(config)#commit
Sat Apr  9 13:03:26.746 UTC
RP/0/RP0/CPU0:ios(config)#end

RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller ThirtyTwoGigFibreChanCtrlr 0/1/0/6/4 laser-squelch
RP/0/RP0/CPU0:ios(config)#commit
Sat Apr  9 13:05:26.746 UTC
RP/0/RP0/CPU0:ios(config)#end

RP/0/RP0/CPU0:ios#show controllers SixteenGigFibreChanCtrlr 0/1/0/0/2

+++ 13:03:44 fe(default) exec +++
show controllers SixteenGigFibreChanCtrlr 0/1/0/0/2

Sat Apr  9 13:03:43.743 UTC

Operational data for Fibre Channel controller SixteenGigFibreChanCtrlr0/1/0/0/2

State:
	Admin State           : Up
	Operational state     : Up
	LED state             : Green On
	Secondary admin state : Normal
	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

Performance Monitoring is enabled

Operational values:
	Speed                    : 16 Gbps
	Loopback                 : None
	BER monitoring:
	    Not supported
	Hold-off Time            : 0 ms
	Forward Error Correction : Not Configured
RP/0/RP0/CPU0:ios#

RP/0/RP0/CPU0:ios#show controllers ThirtyTwoGigFibreChanCtrlr 0/1/0/6/4

+++ 13:03:44 fe(default) exec +++
show controllers ThirtyTwoGigFibreChanCtrlr 0/1/0/6/4

Sat Apr  9 13:03:43.923 UTC

Operational data for Fibre Channel controller ThirtyTwoGigFibreChanCtrlr0/1/0/6/4

State:
	Admin State           : Up
	Operational state     : Up
	LED state             : Green On
	Secondary admin state : Normal
	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

Performance Monitoring is enabled

Operational values:
	Speed                    : 32 Gbps
	Loopback                 : None
	BER monitoring:
	    Not supported
	Hold-off Time            : 0 ms
	Forward Error Correction : Standard(Reed Solomon)

From R7.2.1 onwards, you can enable the idle insertion feature on the 10GE controller for OTN-XP card.

From R7.3.1 onwards, you can enable the idle insertion feature on 100GE or 400GE controllers for the 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

RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller HundredGigECtrlr 0/0/0/1
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#holdoff-time trunk-fault 3000
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#commit

RP/0/RP0/CPU0:ios#show controller hundredGigECtrlr 0/0/0/1
Fri Jul 23 16:07:11.541 UTC
Operational data for interface HundredGigECtrlr0/0/0/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: Enabled

Phy:
    Media type: Not known
Statistics:
FEC:
Corrected Codeword Count: 134967789
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: 3000ms

RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller fourHundredGigECtrlr 0/0/0/10
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#holdoff-time trunk-fault 2000
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#commit

RP/0/RP0/CPU0:ios#show controller fourhundredGigECtrlr 0/0/0/10
Fri Jul 23 16:07:11.541 UTC
Operational data for interface fourHundredGigECtrlr0/0/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: 134967789
Uncorrected Codeword Count: 0

Autonegotiation disabled.

Operational values:
    Speed: 400Gbps
    Duplex: Full Duplex
    Flowcontrol: None
    Loopback: None (or external)
    BER monitoring:
        Not supported
        Forward error correction: Standard (Reed-Solomon)
    Holdoff Time: 2000ms

From R7.8.1 onwards, you can enable idle insertion on 100GE or 400GE controllers for the QXP card such as the NCS1K4-QXP-K9 card.

RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller HundredGigECtrlr 0/1/0/1
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#holdoff-time trunk-fault 3000
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#commit

RP/0/RP0/CPU0:ios#show controller hundredGigECtrlr 0/1/0/1
Fri Jul 23 16:07:11.541 UTC
Operational data for interface HundredGigECtrlr0/1/0/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: Enabled

Phy:
    Media type: Not known
Statistics:
FEC:
Corrected Codeword Count: 134967789
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: 3000ms

RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller fourHundredGigECtrlr 0/0/0/10
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#holdoff-time trunk-fault 2000
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#commit

RP/0/RP0/CPU0:ios#show controller fourhundredGigECtrlr 0/0/0/10
Fri Jul 23 16:07:11.541 UTC
Operational data for interface fourHundredGigECtrlr0/0/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: 134967789
Uncorrected Codeword Count: 0

Autonegotiation disabled.

Operational values:
    Speed: 400Gbps
    Duplex: Full Duplex
    Flowcontrol: None
    Loopback: None (or external)
    BER monitoring:
        Not supported
        Forward error correction: Standard (Reed-Solomon)
    Holdoff Time: 2000ms

The following diagram describes the recommended topology for link verification:

The following steps describe the sequence for link verification using this topology:

1. Both the near-end and far-end clients have the LOCAL-FAULT alarm if the trunk is up on both the ends.

2. Enable idle ingress on the near-end client. The idle frame transmits toward the trunk link and reaches the far-end client. The LOCAL-FAULT alarm is then cleared on the far-end client.

3. As the far-end client has fiber loop, the idle frame is inserted again into the same client RX toward the trunk link and reaches the near-end client. The LOCAL-FAULT alarm is then cleared on the near-end client as well.

4. When you enable idle insertion on any client and in any direction, the idle frame transmits in loop similar to this topology and all the LOCAL-FAULT and the REMOTE-FAULT alarms are cleared.

5. The link can be monitored after all the alarms are cleared. The link has a problem if any alarm is reported during the link test.

Before You Begin:

• Do not configure idle frame insertion with hold-off timer.

• Do not configure PRBS on the trunk.

You can configure this feature by using the following commands:

configure

controller hundredGigECtrlr Rack/Slot/Instance/Port

insert-idle ingress

insert-idle egress

commit

end

The following is a sample for enabling the idle ingress and idle egress in 100GE controllers:

RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller hundredGigECtrlr 0/2/0/2
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#insert-idle ingress
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#insert-idle egress
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#commit
RP/0/RP0/CPU0:ios(config-eth-ctrlr)#end

You can disable this feature by using the following commands:

configure

controller hundredGigECtrlr Rack/Slot/Instance/Port

no insert-idle ingress

no insert-idle egress

commit

end

To verify the idle ingress and idle egress that is configured on the Ethernet controllers, use the following command:

RP/0/RP0/CPU0:ios# show controllers hundredGigECtrlr Rack/Slot/Instance/Port

Example

RP/0/RP0/CPU0:ios#show controllers hundredGigECtrlr 0/2/0/2
Wed Mar 30 06:56:58.878 UTC
Operational data for interface HundredGigECtrlr0/2/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
    
    Insert Idle Ingress: Enabled
    Insert Idle Egress: 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
    Forward error correction: Standard (Reed-Solomon)
    Holdoff Time: 0ms

Daisy Chain must be configured only on the management port 1.

Before You Begin:

• Enable Storm Control on TOR Switch

• Disable DAD on Management​ Port

• STP must be running on the TOR switch.

• Management port 0 must not be in shut down state and must be configured with either IPv4 or IPv6 address.

• Management port 1 must not be configured with either IPv4 or IPv6 address.

• LLDP is not supported on the management port 1 if Daisy Chain is configured​.

To configure Daisy Chain on the management port 1, enter the following commands:

configure

interface mgmtEth 0/RP0/CPU0/1

no ipv4 address

no ipv6 address

bridge-port routed-interface mgmtEth 0/RP0/CPU0/0

To verify the daisy chain that is configured on the management port, use the following commands.

!         
interface MgmtEth0/RP0/CPU0/0
 ipv4 address 10.127.60.220 255.255.255.0
!         
interface MgmtEth0/RP0/CPU0/1
 bridge-port routed-interface MgmtEth0/RP0/CPU0/0
!         
interface MgmtEth0/RP0/CPU0/2
 shutdown 
!      

In Daisy Chain configuration, one of the Top of the Rack (TOR) switch ports is in blocked state, provided NCS 1004 forwards STP BPDU in periodic intervals. Three consecutive hello misses move the port state from blocked to forwarding state.

When the NCS 1004 node reboots, the other port state of the TOR switch changes from blocking to forwarding state. Hence, a loop is created momentarily when both the TOR switch ports are in forwarding state. This loop results in duplication of packets on the network. Hence, storm control must be enabled on the TOR switch.

Enter the following commands from the TOR switch to enable storm control.

errdisable recovery interval 60​

errdisable recovery cause storm-control

By default, IPv6 Duplicate Address Detection (DAD) is enabled on the management ports. Similar to storm control scenario, when IPv6 is configured for a management port, DAD happens due to looping in the network. Since DAD was enabled, management port will be down. In order to avoid management port being down due to momentary looping, DAD must be disabled on the management port 0.

Enter the following commands to disable DAD on the management port 0.

configure

interface mgmtEth0/RP0/CPU0/0

ipv6 nd dad attempts 0

You can configure DHCPv6 client on management Ethernet interfaces. You can configure different DHCPv6 client options to differentiate between clients as required. The different DHCPv6 client options are also configured to differentiate how a DHCPv6 client communicates with a DHCPv6 server. The different DHCPv6 client options that can be configured are:

• DUID: If the DUID DHCPv6 client option is configured on an interface, DHCPv6 client communicates with the DHCPv6 server through the link layer address.

• Rapid Commit: If the Rapid Commit DHCPv6 client option is configured on an interface, DHCPv6 client can obtain configuration parameters from the DHCPv6 server through a rapid two-step exchange (solicit and reply) instead of the default four-step exchange (solicit, advertise, request, and reply).

• DHCP Options: The various other DHCPv6 options that can be configured on a DHCPv6 client are:

  • Option 15: Option 15 is also known as the User Class option and it is used by a DHCPv6 client to identify the type or category of users or applications it represents.

  • Option 16: Option 16 is also known as the Vendor ID option and it is used by a DHCPv6 a client to identify the vendor that manufactured the hardware on which the client is running.

  • Option 23: Option 23 is also known as the Domain name Server (DNS) option provides a list of one or more IPv6 addresses of DNS recursive name servers to which a client's DNS resolver can send DNS queries.

  • Option 24: Option 24 is also known as the Domain List option and it specifies the domain search list that the client uses to resolve hostnames with the DNS.

• DHCP Timers: This option is used to set different timer value for DHCP client configurations. The various DHCP timer options are:

  • Release-timeout: It is used to set retransmission timeout value for the initial release message.

  • Req-max-rt: It is used to set the maximum retransmission timeout value for the request message.

  • Req-max-rt: It is used to set the maximum retransmission timeout value for the request message.

  • Sol-max-delay: It is used to set the maximum delay time of the first solicit message.

  • Sol-max-rt: It is used to set the maximum solicit retransmission time.

  • Sol-time-out: It is used to set the intial timeout value of the solicit message.

To enable DHCP client on the management Ethernet interface, use the following command:

configure

interface MgmtEth R/S/I/P

ipv6 address dhcp-client-options

duid linked-layer-address

rapid-commit

{option 16 vendor | option 15 ciscoupnnp | option 23 | option 24}

timers sol-max-delay value | timers sol-time-out value | timers req-timeout value | timers req-max-rt value | timers release-timeout value}

ipv6 address dhcp

commit

The following sample shows to enable DHCP client on the management Ethernet interface:

RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#interface MgmtEth0/0/CPU0/0
RP/0/RP0/CPU0:ios(config)#ipv6 address dhcp-client-options
RP/0/RP0/CPU0:ios(config-dhcpv6-client)#duid linked-layer-address
RP/0/RP0/CPU0:ios(config-dhcpv6-client)#rapid-commit
RP/0/RP0/CPU0:ios(config-dhcpv6-client)#option 16 vendor
RP/0/RP0/CPU0:ios(config-dhcpv6-client)#option 15 ciscoupnnp
RP/0/RP0/CPU0:ios(config-dhcpv6-client)#option 23
RP/0/RP0/CPU0:ios(config-dhcpv6-client)#option 24
RP/0/RP0/CPU0:ios(config-dhcpv6-client)#timers sol-max-delay 1
RP/0/RP0/CPU0:ios(config-dhcpv6-client)#timers sol-time-out 1
RP/0/RP0/CPU0:ios(config-dhcpv6-client)#timers sol-max-rt 120
RP/0/RP0/CPU0:ios(config-dhcpv6-client)#timers req-timeout 1
RP/0/RP0/CPU0:ios(config-dhcpv6-client)#timers req-max-rt 30
RP/0/RP0/CPU0:ios(config-dhcpv6-client)#timers release-timeout 1
RP/0/RP0/CPU0:ios(config-dhcpv6-client)#commit

To verify DHCP client options on the management Ethernet interface, use the show dhcp ipv6 client and show dhcp ipv6 client detail commands:

RP/0/0/CPU0:ios#show dhcp ipv6 client
Thu Sep 17 10:45:44.493 IST

Interface name IPv6 Address State Lease Time Rem
---------------------- -------------- --------------- --------------------
MgmtEth0/0/1/0 500:1::1a/128 BOUND 7116


RP/0/RP0/CPU0:ios#show dhcp ipv6 client detail
Thu Sep 17 10:45:48.880 IST

-----------------------------------------------------
Client Interface name : MgmtEth0/0/`/0
Client Interface handle : 0x4040
Client MACAddr : 0219.bc81.e750
Client State : BOUND
Client Link Local Address : fe80::19:bcff:fe81:e750
Client IPv6 Address (Dhcp) : 500:1::1a/128
Lease Remaining (in secs) : 7112
DUID : 000300010219bc81e750

Client Configuration
Timers
SOL_MAX_DELAY : 1 secs (00:00:01)
SOL_TIMEOUT : 1 secs (00:00:01)
SOL_MAX_RT : 120 secs (00:02:00)
REQ_TIMEOUT : 1 secs (00:00:01)
REQ_MAX_RT : 30 secs (00:00:30)
REL_TIMEOUT : 1 secs (00:00:01)

Options
RAPID-COMMIT : True
USER-CLASS : ciscoupnnp
VENDOR-CLASS : vendor
DNS-SERVERS : True
DOMAIN-LIST : True

DUID Type : DUID_LL

Server Information
Server Address : fe80::1a:19ff:fe03:99ca
Preference : 255
DUID : 000300010206826e2e00
Status : SUCCESS
IA-NA
Status : SUCCESS
IAID : 0x40400001
T1 : 3600 secs (01:00:00)
T2 : 5760 secs (01:36:00)
IA-ADDR
IA NA Address : 500:1::1a
Preferred Time : 7200 secs (02:00:00)
Valid Time : 7200 secs (02:00:00)
Flags : 0x0
-----------------------------------------------------

You can configure MAC address or ARP snoop on slice in Muxponder slice mode using the following commands.

configure

hw-module location location mxponder-slice slice-number

client-rate 100GE

trunk-rate 600G { 100G | 150G | 200G | 250G | 300G | 350G | 400G | 450G | 500G | 550G | 600G }

arp-snoop

commit

Example

The following is a sample in which, MAC address or ARP snoop is configured on the client ports of slice 0 in Muxponder slice mode.

RP/0/RP0/CPU0:ios#configure
Mon Mar 16 19:30:33.933 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/3 mxponder-slice 0
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-rate 100GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 600G
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#arp-snoop
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
Mon Mar 16 19:30:52.636 UTC
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#end

The following is a sample in which, MAC address or ARP snoop is configured in Muxponder mode.

RP/0/RP0/CPU0:ios#configure 
Mon Mar 16 19:08:17.154 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder arp-snoop 
RP/0/RP0/CPU0:ios(config)#commit

The following sample shows the output of show controllers hundredGigEctrlr command, before configuring MAC address or ARP snoop on client ports.

RP/0/RP0/CPU0:ios#show controllers hundredGigECtrlr 0/1/0/2 
Mon Mar 16 19:40:37.434 UTC
Operational data for interface HundredGigECtrlr0/1/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

Autonegotiation disabled.

Operational values:
    Speed: 100Gbps
    Duplex: Full Duplex
    Flowcontrol: None
    Loopback: None (or external)
    BER monitoring:
        Not supported
    Holdoff Time: 0ms

You can view the neighbor's physical address after enabling MAC address or ARP snoop using the following command. MAC address snoop output is enabled after ARP packets are received on the respective 100G client.

show controllers hundredGigEctrlr R/S/I/P

The following sample shows the neighbor's MAC address after configuring MAC address or ARP snoop on client ports.

RP/0/RP0/CPU0:ios#show controllers hundredGigECtrlr 0/1/0/2 
Mon Mar 16 19:41:08.047 UTC
Operational data for interface HundredGigECtrlr0/1/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
    Neighbor Address:
    0010.9400.5502

Phy:
    Media type: Not known

Autonegotiation disabled.

Operational values:
    Speed: 100Gbps
    Duplex: Full Duplex
    Flowcontrol: None

To perform transmit shutdown, enter the following commands:

RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller Optics R/S/I/P
RP/0/RP0/CPU0:ios(config-Optics)#transmit-shutdown
RP/0/RP0/CPU0:ios(config-Optics)#commit
RP/0/RP0/CPU0:ios(config-Optics)#exit
RP/0/RP0/CPU0:ios(config)#exit

The following is a sample to perform transmit shutdown on the trunk port:

RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller Optics 0/1/0/12
RP/0/RP0/CPU0:ios(config-Optics)#transmit-shutdown
RP/0/RP0/CPU0:ios(config-Optics)#commit
RP/0/RP0/CPU0:ios(config-Optics)#exit
RP/0/RP0/CPU0:ios(config)#exit

The following is a sample to perform transmit shutdown on the trunk port in the 4x100GE-MXP-DD muxponder mode:

RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller Optics 0/1/0/9
RP/0/RP0/CPU0:ios(config-Optics)#transmit-shutdown
RP/0/RP0/CPU0:ios(config-Optics)#commit
RP/0/RP0/CPU0:ios(config-Optics)#exit
RP/0/RP0/CPU0:ios(config)#exit

RP/0/RP0/CPU0:ios#sh controllers optics 0/1/0/12
Fri Feb 26 21:36:16.009 UTC

Controller State: Up

Transport Admin State: In Service

Laser State: Off

LED State: Yellow

Optics Status

Optics Type: CFP2 DWDM
DWDM carrier Info: C BAND, MSA ITU Channel=61, Frequency=193.10THz,
Wavelength=1552.524nm

Alarm Status:
-------------
Detected Alarms:
LOW-TX-PWR

LOS/LOL/Fault Status:

Alarm Statistics:

-------------
HIGH-RX-PWR = 0 LOW-RX-PWR = 1
HIGH-TX-PWR = 0 LOW-TX-PWR = 1
HIGH-LBC = 0 HIGH-DGD = 0
OOR-CD = 0 OSNR = 0
WVL-OOL = 0 MEA = 0
IMPROPER-REM = 0
TX-POWER-PROV-MISMATCH = 0
Laser Bias Current = 0.0 %
Actual TX Power = -40.00 dBm
RX Power = -1.02 dBm
RX Signal Power = -12.20 dBm
Frequency Offset = -8 MHz

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 %
Configured Tx Power = -1.50 dBm
Configured CD High Threshold = 180000 ps/nm
Configured CD lower Threshold = -180000 ps/nm
Configured OSNR lower Threshold = 0.00 dB
Configured DGD Higher Threshold = 180.00 ps
Baud Rate = 63.1394691467 GBd
Bits per Symbol = 4.0000000000 bits/symbol
Modulation Type: 16QAM
Chromatic Dispersion 0 ps/nm
Configured CD-MIN -26000 ps/nm CD-MAX 26000 ps/nm
Polarization Mode Dispersion = 0.0 ps
Second Order Polarization Mode Dispersion = 16.00 ps^2
Optical Signal to Noise Ratio = 35.90 dB
SNR = 17.00 dB
Polarization Dependent Loss = 0.70 dB
Polarization Change Rate = 0.00 rad/s
Differential Group Delay = 1.00 ps

Transceiver Vendor Details

Form Factor : CFP2
Name : CISCO-ACACIA
Part Number : 10-3500-01
Rev Number : 01
Serial Number : ACA24230026
PID : ONS-CFP2D-400G-C
VID : VES1
Date Code(yy/mm/dd) : 10/09/Í
Fiber Connector Type: LC
Otn Application Code: Not Set
Sonet Application Code: Not Set
Ethernet Compliance Code: Not set

Transceiver Temperature : 55 Celsius



AINS Soak : None
AINS Timer : 0h, 0m
AINS remaining time : 0 seconds

RP/0/RP0/CPU0:ios#show controller optics 0/1/0/9
Wed Sep 15 00:41:22.027 UTC

 Controller State: Up 

 Transport Admin State: In Service 

 Laser State: On 

 LED State: Green 
 
 Optics Status 

         Optics Type:  QSFP-DD DWDM
         DWDM carrier Info: C BAND, MSA ITU Channel=49, Frequency=193.70THz,
         Wavelength=1547.715nm 

         Alarm Status:
         -------------
         Detected Alarms: None


         LOS/LOL/Fault Status:

         Alarm Statistics:
          
         -------------
         HIGH-RX-PWR = 0            LOW-RX-PWR = 3          
         HIGH-TX-PWR = 0            LOW-TX-PWR = 5          
         HIGH-LBC = 0               HIGH-DGD = 0          
         OOR-CD = 0                 OSNR = 4          
         WVL-OOL = 0                MEA  = 0          
         IMPROPER-REM = 6          
         TX-POWER-PROV-MISMATCH = 0          
         Laser Bias Current = 0.0 %
         Actual TX Power = -11.10 dBm 
         RX Power = -11.56 dBm 
         RX Signal Power = -11.62 dBm 
         Frequency Offset = -66 MHz 

   Performance Monitoring: Enable 

         THRESHOLD VALUES
         ----------------

         Parameter                 High Alarm  Low Alarm  High Warning  Low Warning
         ------------------------  ----------  ---------  ------------  -----------
         Rx Power Threshold(dBm)          3.0      -24.5           0.0          0.0
         Tx Power Threshold(dBm)          0.0      -16.0           0.0          0.0
         LBC Threshold(mA)                N/A        N/A          0.00         0.00

         LBC High Threshold = 90 % 
         Configured Tx Power = -10.00 dBm 
         Configured CD High Threshold = 52000 ps/nm 
         Configured CD lower Threshold = -52000 ps/nm 
         Configured OSNR lower Threshold = 21.10 dB 
         Configured DGD Higher Threshold = 67.00 ps 
         Baud Rate =  60.1385467980 GBd
         Bits per Symbol = 4.0000000000  bits/symbol 
         Modulation Type: 16QAM 
         Chromatic Dispersion 0 ps/nm 
         Configured CD-MIN -13000 ps/nm  CD-MAX 13000 ps/nm 
         Polarization Mode Dispersion = 0.0 ps 
         Second Order Polarization Mode Dispersion = 24.00 ps^2 
         Optical Signal to Noise Ratio = 35.70 dB 
         SNR = 19.40 dB 
         Polarization Dependent Loss = 0.20 dB 
         Polarization Change Rate = 0.00 rad/s 
         Differential Group Delay = 1.00 ps 

 Transceiver Vendor Details
          
         Form Factor            : QSFP-DD
         Name                   : CISCO-ACACIA
         Part Number            : DP04QSDD-E
         Rev Number             : A
         Serial Number          : ACA2524006W
         PID                    : QDD-400G-ZRP-S
         VID                    : V01
         Date Code(yy/mm/dd)    : 21/06/18
         Fiber Connector Type: LC 
         Otn Application Code: Not Set 
         Sonet Application Code: Not Set 
         Ethernet Compliance Code: Not set 

 Transceiver Temperature : 62 Celsius
 AINS Soak                : None 
 AINS Timer               : 0h, 0m

You can configure the TTI sent or expected string in the full ASCII format, or Source Access Point Identifier (SAPI)/Destination Access Point Identifier (DAPI) format on OTU, ODU, ODU-flex, ODUCn, and coherentDSP controllers for the OTN-XP card.

From R7.3.1 onwards, coherentDSP controller supports only the full ASCII string format.

From R7.3.2 onwards, coherentDSP controller supports SAPI/DAPI string format in addition to the full ASCII string format.

You can configure TTI for the following muxponder modes:

• 10G-Grey-MXP

• 4x100G-MXP-400G-TXP

The following table lists the ASCII format that is supported on each muxponder mode for TTI:

To configure TTI, use the following commands:

configure

controller controller-type R/S/I/P tti {sent | expected} {ascii | sapi ascii | dapi ascii | operator-specific ascii } tti-string

commit

Note	We recommend that you configure TTI in the SAPI/DAPI ASCII format.

Restriction

For OC192 and STM 64 payloads, configure both sides for ASCII and hex on mapper ODU2. For OC192 and STM 64 payloads, do not edit operator specific hex on mapper ODU2. Instead, delete and create the operator specific hex.

RP/0/RP0/CPU0:ios#configure 
Thu Sep 30 17:19:11.804 UTC
Current Configuration Session  Line       User     Date                     Lock
00001000-00005c15-00000000     vty0       root     Thu Sep 30 11:50:12 2021 
RP/0/RP0/CPU0:ios(config)#controller odU4 0/1/0/12/7 tti sent sapi ascii cisco123
RP/0/RP0/CPU0:ios(config)#controller odU4 0/1/0/12/7 tti expect sapi ascii 123cisco
RP/0/RP0/CPU0:ios(config)#controller odU4 0/1/0/12/7 tti sent dapi ascii dapistring123
RP/0/RP0/CPU0:ios(config)#controller odU4 0/1/0/12/7 tti expected dapi ascii 123stringdapi
RP/0/RP0/CPU0:ios(config)#controller odU4 0/1/0/12/7 tti sent operator-specific ascii operation123
RP/0/RP0/CPU0:ios(config)#controller odU4 0/1/0/12/7 tti expected operator-specific ascii 123operator
RP/0/RP0/CPU0:ios(config)#commit 
Thu Sep 30 17:21:49.521 UTC
RP/0/RP0/CPU0:ios(config)#end

RP/0/RP0/CPU0:ios#show controllers odU4 0/1/0/12/7 
Thu Sep 30 17:22:30.658 UTC

Port                                            : ODU4 0/1/0/12/7
Controller State                                : Down
Inherited Secondary state                       : Normal
Configured Secondary state                      : Normal
Derived State                                   : In Service
Loopback mode                                   : None
BER Thresholds                                  : SF = 1.0E-6  SD = 1.0E-7

Performance Monitoring                          : Enable 

Path Monitoring Mode                            : Operational 
PM TIM-CA state                                 : Disable 

Alarm Information:
AIS = 3 IAE = 0 BIAE = 0
SF_BER = 0      SD_BER = 0      BDI = 1
OCI = 0 LCK = 2 PTIM = 0
TIM = 1 CSF = 0 GFP LFD = 0
GFP LOCS = 0    GFP LOCCS = 0   GFP UPM = 0

Detected Alarms                                 : TIM 

ODU TTI Sent 
     SAPI  ASCII                                : c i s c o 1 2 3 
     SAPI  HEX                                  : 00636973636F31323300000000000000
     DAPI  ASCII                                : d a p i s t r i n g 1 2 3 
     DAPI  HEX                                  : 0064617069737472696E673132330000
     OPERATOR SPECIFIC ASCII                    : operation123
     OPERATOR SPECIFIC HEX                      : 6F7065726174696F6E3132330000000000000000000000000000000000000000
ODU TTI Received 

ODU TTI Expected 
     SAPI  ASCII                                : 1 2 3 c i s c o 
     SAPI  HEX                                  : 00313233636973636F00000000000000
     DAPI  ASCII                                : 1 2 3 s t r i n g d a p i 
     DAPI  HEX                                  : 00313233737472696E67646170690000
     OPERATOR SPECIFIC ASCII                    : 123operator
     OPERATOR SPECIFIC HEX                      : 3132336F70657261746F72000000000000000000000000000000000000000000
AINS Soak                                       : None
AINS Timer                                      : 0h, 0m
AINS remaining time                             : 0 seconds

Private Line Emulation(PLE) supported           : No

Mon Dec 27 12:03:53.642 UTC
RP/0/RP0/CPU0:ios(config)#controller CoherentDSP 0/3/0/12 tti sent ascii 1234cisco
RP/0/RP0/CPU0:ios(config)#commit
Mon Dec 27 12:03:54.333 UTC
RP/0/RP0/CPU0:ios(config)#end
Mon Dec 27 12:03:55.434 UTC
RP/0/RP0/CPU0:ios(config)#controller CoherentDSP 0/3/0/12 tti expected ascii cisco1234
RP/0/RP0/CPU0:ios(config)#commit
Mon Dec 27 12:03:56.137 UTC
RP/0/RP0/CPU0:ios(config)#end

RP/0/RP0/CPU0:ios#show controllers coherentDSP 0/0/0/12
Tue May 24 17:49:14.301 UTC

Port                                            : CoherentDSP 0/0/0/12
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                                       : 400.0Gb/s

Alarm Information:
LOS = 0 LOF = 0 LOM = 0
OOF = 0 OOM = 0 AIS = 0
IAE = 0 BIAE = 0        SF_BER = 0
SD_BER = 0      BDI = 1 TIM = 1
FECMISMATCH = 0 FEC-UNC = 0     FLEXO_GIDM = 0
FLEXO-MM = 0    FLEXO-LOM = 0   FLEXO-RDI = 0
FLEXO-LOF = 0
Detected Alarms                                 : None

Bit Error Rate Information
PREFEC  BER                                     : 1.55E-04
POSTFEC BER                                     : 0.00E+00
Q-Factor                                        : 11.10 dB

Q-Margin                                        : 4.70dB

OTU TTI Sent
     FULL TTI ASCII                             : cisco123
                                                :
     FULL TTI HEX                               : 636973636F3132330000000000000000
                                                : 00000000000000000000000000000000
OTU TTI Received
     FULL TTI ASCII                             : 123cisco
                                                :
     FULL TTI HEX                               : 313233636973636F0000000000000000
                                                : 00000000000000000000000000000000
OTU TTI Expected
     FULL TTI ASCII                             : 123cisco
                                                :
     FULL TTI HEX                               : 313233636973636F0000000000000000
                                                : 00000000000000000000000000000000
FEC mode                                        : O_FEC

Flexo-Mode                                      : Enable
Flexo Details:
        Tx GID                                  : 1
        TX IID                                  : 1, 2, 3, 4,
        Rx GID                                  : 1
        RX IID                                  : 1, 2, 3, 4,

AINS Soak                                       : None
AINS Timer                                      : 0h, 0m
AINS remaining time                             : 0 seconds


RP/0/RP0/CPU0:ios#
RP/0/RP0/CPU0:ios#show running-config controller coherentDSP 0/0/0/12
Tue May 24 17:49:21.749 UTC
controller CoherentDSP0/0/0/12
tti
  expected ascii 123cisco
  sent ascii cisco123
!
!

Configure TTI on Inverse Muxponder Configuration on the OTN-XP Card

The following sample displays how to configure TTI on a coherent DSP controller port 12 on the OTN-XP in inverse muxponder configuration mode.

Note	TTI configuration is not supported on the DSP controller port 13.

RP/0/RP0/CPU0:ios#configure
Thu Sep 30 14:18:13.288 UTC
RP/0/RP0/CPU0:ios(config)#controller coherentDSP 0/2/0/12 
RP/0/RP0/CPU0:ios(config-CoDSP)#tti sent sapi ascii cisco
RP/0/RP0/CPU0:ios(config-CoDSP)#commit

The following sample verifies the TTI configuration on the inverse muxponder configured on the OTN-XP Card.

RP/0/RP0/CPU0:ios#show controllers coherentDSP 0/2/0/12 
Thu Sep 30 14:19:05.367 UTC

Port                                            : CoherentDSP 0/2/0/12
Controller State                                : Up
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                                       : 200.0Gb/s

Alarm Information:
LOS = 2 LOF = 0 LOM = 0
OOF = 1 OOM = 0 AIS = 1
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 = 1
FLEXO-LOF = 0   
Detected Alarms                                 : None

Bit Error Rate Information
PREFEC  BER                                     : 4.11E-09 
POSTFEC BER                                     : 0.00E+00 
Q-Factor                                        : 14.90 dB 

Q-Margin                                        : 8.60dB 

OTU TTI Sent 
     SAPI  ASCII                                : c i s c o 
     SAPI  HEX                                  : 00636973636F00000000000000000000
     DAPI  ASCII                                : 
     DAPI  HEX                                  : 
     OPERATOR SPECIFIC ASCII                    : 
     OPERATOR SPECIFIC HEX                      : CDCDCDCDED00DBBE2100000000000000050D9D29AD7F00007603BADC7698BADC
OTU TTI Received 
     SAPI  ASCII                                : c i s c o 
     SAPI  HEX                                  : 00636973636F00000000000000000000
FEC mode                                        : O_FEC

Flexo-Mode                                      : Enable
Flexo Details:
        Tx GID                                  : 1
        TX IID                                  : 1, 2, 
        Rx GID                                  : 1
        RX IID                                  : 1, 2, 

Flexo Peers Information:
        Controller                              : CoherentDSP0_2_0_13 
        OTUCn rate                              : OTUC2


AINS Soak                                       : None
AINS Timer                                      : 0h, 0m
AINS remaining time                             : 0 seconds

From R7.10.1, you can configure the TTI sent or expected string in the full ASCII format, or Source Access Point Identifier (SAPI)/Destination Access Point Identifier (DAPI) format on ODU-flex, ODU4, and coherentDSP controllers for the QXP card.

Note	TTI operates only in trunk mode OR .

The following table lists the ASCII format that is supported for TTI:

To configure TTI, use the following commands:

configure

controller controller-type R/S/I/P tti {sent | expected} {ascii | sapi ascii | dapi ascii | operator-specific ascii } tti-string

commit

The following is a sample configuration for FULL TTI for coherentDSP controller

RP/0/RP0/CPU0:ios(config)#controller coherentDSP 0/0/0/8
RP/0/RP0/CPU0:ios(config-CoDSP)#tti sent ascii cisco
RP/0/RP0/CPU0:ios(config-CoDSP)#tti  expected ascii cisco123
RP/0/RP0/CPU0:ios(config-CoDSP)#commit

The following is a sample configuration for TTI HEX for coherentDSP controller

RP/0/RP0/CPU0:ios(config)#controller coherentDSP 0/0/0/8
RP/0/RP0/CPU0:ios(config-CoDSP)#tti sent hex 6E6E6E2A2A2A
RP/0/RP0/CPU0:ios(config-CoDSP)#tti  expected hex 3F4B4B4B3D3E3A
RP/0/RP0/CPU0:ios(config-CoDSP)#commit

The following is a sample configuration for Operator specific TTI for coherentDSP controller

RP/0/RP0/CPU0:ios(config)#controller coherentDSP 0/0/0/8
RP/0/RP0/CPU0:ios(config-CoDSP)#tti sent operator-specific ascii hellooo
RP/0/RP0/CPU0:ios(config-CoDSP)#tti expected operator-specific ascii hellooo
RP/0/RP0/CPU0:ios(config-CoDSP)#commit

The following is a sample configuration for Operator specific TTI HEX for coherentDSP controller

RP/0/RP0/CPU0:ios(config)#controller coherentDSP 0/0/0/8
RP/0/RP0/CPU0:ios(config-CoDSP)#tti  sent operator-specific hex 6E6E6E2A2A2A3D3E3A3A6E6E6E2A2A2A3D
RP/0/RP0/CPU0:ios(config-CoDSP)#tti  expected operator-specific hex 5A5A6D3A3B3C3F4B4B4B3D3E3A
RP/0/RP0/CPU0:ios(config-CoDSP)#commit

The following is a sample configuration for SAPI for coherentDSP controller

RP/0/RP0/CPU0:ios(config)#controller coherentDSP 0/0/0/8
RP/0/RP0/CPU0:ios(config-CoDSP)#tti sent operator-specific ascii hellooo
RP/0/RP0/CPU0:ios(config-CoDSP)#tti expected operator-specific ascii hellooo
RP/0/RP0/CPU0:ios(config-CoDSP)#commit

The following is a sample configuration for DAPI for coherentDSP controller

RP/0/RP0/CPU0:ios(config)#controller coherentDSP 0/0/0/8
RP/0/RP0/CPU0:ios(config-CoDSP)#tti sent dapi ascii cisco123
RP/0/RP0/CPU0:ios(config-CoDSP)#tti  expected dapi ascii hello
RP/0/RP0/CPU0:ios(config-CoDSP)#commit

The secondary admin state of the coherentDSP or ODU4 controller must be set to maintenance before enabling PRBS.

To enable the PRBS on the trunk port, use the following configuration command at the coherentDSP controller:

controller coherentDSP R/S/I/P prbs mode {source | sink | source-sink} pattern {pn31 | pn23 | pn15 | pn7}

To enable the PRBS on the trunk port, use the following configuration command at the ODU4 controller:

controller odu4 R/S/I/P/L opu prbs mode {source | sink | source-sink} pattern {pn31 | pn23 | pn15 | pn7}

When the PRBS is enabled on the trunk ports, you can view the following impacts in the corresponding client ports:

• Client traffic is dropped in the direction of source to sink as the frames are overwritten by the PRBS pattern.

• Remote fault is raised on the client ports nearer to the PRBS sink.

The following are the ODU4 PRBS combinations. The client ports must have physical loop back in all the combinations.

• Near End client and Near End trunk ODU4

• Near End client and Far End client ODU4

• Near End client and Far End trunk ODU4

• Near End trunk and Far End trunk ODU4

The following sample diagram describes the ODU4 PRBS combination for Near End client and Near End trunk.

You can monitor the status of Pseudo Random Binary Sequence (PRBS) on the CoherentDSP or ODU4 controller using the following command:

show controllers coherentDSP | ODU4 R/S/I/P prbs-details

RP/0/RP0/CPU0:ios#show controllers coherentDSP 0/1/0/0 prbs-details
Wed Nov  6 23:12:22.464 UTC

----------------------PRBS details------------------
PRBS Test               : Enable
PRBS Mode               : Source
PRBS Pattern            : PN7
PRBS Status             : Not Applicable

---------------------------------------------------

RP/0/RP0/CPU0:ios#show controllers ODU4 0/3/0/8 prbs-details
Mon Jan 11 05:29:12.436 UTC

 -------------------------PRBS details----------------------------------
PRBS Test                       : Enable
PRBS Mode                       : Source
PRBS Pattern                    : PN7
PRBS Status                     : Not Applicable

---------------------------------------------------

RP/0/RP0/CPU0:ios#show controllers ODU4 0/3/0/1/1 prbs-details
Mon Jan 11 05:27:56.370 UTC

 -------------------------PRBS details----------------------------------
PRBS Test                       : Enable
PRBS Mode                       : Sink
PRBS Pattern                    : PN7
PRBS Status                     : Locked

---------------------------------------------------

• You cannot view any details, if the PRBS is not enabled on the trunk.

• PRBS status is shown as Not Applicable, when the mode is Source.

• PRBS status is shown as unlocked, when the signal is not locked on the receiving side in the Sink or Source-Sink mode.

PRBS PM parameters are not available for the controllers in Source mode. PRBS PM parameters are reset when PRBS configuration changes on the controller.

To view the PRBS PM parameters on the coherentDSP controller, use the following command:

show controllers coherentDSP | ODU4 R/S/I/P pm {current | history }{15-min|24-hour} prbs

The following tables describes the fields of PRBS PM parameters.

RP/0/RP0:ios#show controllers coherentDSP 0/0/0/1 pm current 15-min prbs
Mon Feb 13 00:58:48.327 UTC 
 
PRBS in the current interval [00:45:00 - 00:58:48 Mon Feb 13 2019] 
PRBS current bucket type : Valid 
EBC                      : 40437528165 
FOUND-COUNT              : 1 FOUND-AT-TS : 00:51:22 Mon Feb 13 2019
LOST-COUNT               : 1 LOST-AT-TS  : 00:52:52 Mon Feb 13 2019
CONFIG-PTRN              : PRBS_PATTERN_PN31 
Last clearing of "show controllers OTU" counters never 

RP/0/RP0:ios#show controllers ODU4 0/3/0/1/1 pm current 15-min prbs
Mon Jan 11 00:58:48.327 UTC 
 
PRBS in the current interval [00:45:00 - 00:58:48 Mon Jan 11 2021] 
PRBS current bucket type : Valid 
EBC                      : 40437528165 
FOUND-COUNT              : 1 FOUND-AT-TS : 00:51:22 Mon Jan 11 2021
LOST-COUNT               : 1 LOST-AT-TS  : 00:52:52 Mon Jan 11 2021
CONFIG-PTRN              : PRBS_PATTERN_PN7
Last clearing of "show controllers ODU" counters never 

To configure PBRS mode on the ODU2e controller, you must configure Optical Channel Payload Unit (OPU) on the ODU2e controller followed by the PRBS mode and the pattern. The PRBS supported pattern on the OTN-XP card is invertedPN31.

From R7.3.1 onwards, you can configure PRBS on client or mapper ODU4 and ODU flex controllers.

For fiber channel controllers, PRBS is supported on mapper ODU flex controllers.

Note	ODU2e PRBS is not supported for OTU2E client rates.

To configure PRBS mode on the ODU2e controller, enter the following commands:

configure

controller odu2e | oduflex R/S/I/P/client-port/lane-number

secondary-admin-state maintenance

opu

prbs mode {source | sink | source-sink} pattern invertedpn31 {direction {system | line}}

end

commit

The following example shows how to configure PRBS mode as source-sink with pattern as invertedpn31:

RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller odu2e0/2/0/12/3/2   
RP/0/RP0/CPU0:ios(config-odu2e)#secondary-admin-state maintenance
RP/0/RP0/CPU0:ios(config-odu2e)#opu
RP/0/RP0/CPU0:ios(config-Opuk)#prbs mode source-sink pattern invertedpn31
RP/0/RP0/CPU0:ios(config-Opuk)#end
RP/0/RP0/CPU0:ios(config-odu2e)#commit

The following is a sample output of show controller odu2e command.

RP/0/RP0/CPU0(config-odu2e)#show controller odu2e 0/2/0/12/3/2 prbs-details 
Mon Mar 14 21:33:02.293 UTC

 -------------------------PRBS details----------------------------------
PRBS Test                       : Enable
PRBS Mode                       : Source-Sink
PRBS Pattern                    : INVERTED PN31
PRBS Status                     : Locked
PRBS Lock Time(in seconds)      : 1190
PRBS Bit Errors                 : 0

---------------------------------------------------

The following example shows how to configure PRBS mode as source-sink with pattern as invertedpn31 with direction as system:

RP/0/RP0/CPU0:ios#configure
Wed Nov 11 00:38:11.789 UTC
RP/0/RP0/CPU0:ios(config)#controller odu4 0/2/0/5
RP/0/RP0/CPU0:ios(config-odu4)#secondary-admin-state maintenance
RP/0/RP0/CPU0:ios(config-odu4)#opu prbs mode source-sink pattern invertedpn31 direction system
RP/0/RP0/CPU0:ios(config-odu4)#commit
Wed Nov 11 00:38:26.391 UTC

The following example shows how to configure PRBS mode as source-sink with pattern as invertedpn31 with direction as line:

RP/0/RP0/CPU0:ios#configure
Wed Nov 11 00:38:11.789 UTC
RP/0/RP0/CPU0:ios(config)#controller odu4 0/2/0/5
RP/0/RP0/CPU0:ios(config-odu4)#secondary-admin-state maintenance
RP/0/RP0/CPU0:ios(config-odu4)#opu prbs mode source-sink pattern invertedpn31 direction line
RP/0/RP0/CPU0:ios(config-odu4)#commit
Wed Nov 11 00:38:26.391 UTC

The following example shows how to configure PRBS on the mapper controller:

RP/0/RP0/CPU0:ios#configure
Thu Oct 7 13:17:27.267 UTC
RP/0/RP0/CPU0:ios(config)#controller odu4 0/2/0/13/8
RP/0/RP0/CPU0:ios(config-odu4)#secondary-admin-state maintenance
RP/0/RP0/CPU0:ios(config-odu4)#opu prbs mode source-sink pattern invertedpn31
RP/0/RP0/CPU0:ios(config-odu4)#commit

The following example shows how to configure PRBS on the mapper controller with PRBS mode as source-sink and pattern as invertedpn31 with direction as line:

RP/0/RP0/CPU0:ios(config)#controller odu4 0/3/0/7
RP/0/RP0/CPU0:ios(config-odu4)#secondary-admin-state maintenance
RP/0/RP0/CPU0:ios(config-odu4)#opu prbs mode source-sink pattern invertedpn31 direction line
RP/0/RP0/CPU0:ios(config-odu4)#commit
Tue Oct 12 13:17:07.840 UTC

Lock time is the time that is elapsed since the last PRBS lock is detected.

The following sample shows that bit errors are observed during the PRBS test:

RP/0/RP0/CPU0:ios#show controllers odu4 0/2/0/5 prbs-details
Fri Nov 13 03:21:44.191 UTC

-------------------------PRBS details----------------------------------
PRBS Test : Enable
PRBS Mode : Source-Sink
PRBS Pattern : INVERTED PN31
PRBS Status : Locked
PRBS Direction : Line
PRBS Lock Time(in seconds) : 28
PRBS Bit Errors : 23776

---------------------------------------------------

To clear the lock time and bit errors before the PRBS test, use the clear command:

RP/0/RP0/CPU0:ios#clear controller odu4 0/2/0/5 prbs-details
Fri Nov 13 03:21:50.726 UTC
PRBS bit errors cleared

The following sample displays the bit errors and lock time are removed.

RP/0/RP0/CPU0:ios#show controllers odu4 0/2/0/5 prbs-details
Fri Nov 14 03:21:44.191 UTC
-------------------------PRBS details----------------------------------
PRBS Test : Enable
PRBS Mode : Source-Sink
PRBS Pattern : INVERTED PN31
PRBS Status : Locked
PRBS Direction : Line
PRBS Lock Time(in seconds) : 2
PRBS Bit Errors : 0

To configure flexO GID and IID on the coherentDSP controller, enter the following commands:

configure

controller coherentDSP R/S/I/P

flexo

gid <gid-no> iid <iid-no>

commit

Note	You must configure the iid number based on the trunk bandwidth. You must add 1, 2, 3, and 4 iid numbers for 100G, 200G, 300G, and 400G respectively.

The following sample shows how to configure flexO GID and IID on the CoherentDSP controller:

RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#controller coherentDSP0/2/0/12
RP/0/RP0/CPU0:ios(config-CoDSP)#flexo
RP/0/RP0/CPU0:ios(config-CoDSP)#gid 2 iid 5,6,7,8
RP/0/RP0/CPU0:ios(config-CoDSP)#commit

The following sample shows the flexO GID and IID configuration on the CoherentDSP controller:

RP/0/RP0/CPU0:ios#show controllers coherentDSP 0/2/0/12                                                                                    
Tue Jan 12 11:26:08.235 UTC  
Port : CoherentDSP 0/2/0/12
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 : 400.0Gb/s

Alarm Information:
LOS = 0 LOF = 3 LOM = 0
OOF = 3 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 = 1
FLEXO-MM = 1 FLEXO-LOM = 0 FLEXO-RDI = 3
FLEXO-LOF = 0 
Detected Alarms : None

Bit Error Rate Information
PREFEC BER : 6.43E-04 
POSTFEC BER : 0.00E+00 

TTI :
Remote hostname : ios
Remote interface : CoherentDSP 0/0/0/13
Remote IP addr : 0.0.0.0

FEC mode : O_FEC

Flexo-Mode : Enable
Flexo Details:
Tx GID : 2
TX IID : 5,6,7,8, 
Rx GID : 2
RX IID 5,6,7,8, 

AINS Soak : None
AINS Timer : 0h, 0m
AINS remaining time : 0 seconds

By default, the value of flexo parameters for the coherentDSP controllers in the 400G inverse muxponder, are as follows:

• CoherentDSP 0/0/0/12―GID is 1 and IID is 1, 2.

• CoherentDSP 0/0/0/13―GID is 1 IID is 3, 4.

The following example displays the default configurations on the transmission side:

RP/0/RP0/CPU0:ios#show controllers coherentDSP 0/0/0/13
Wed Jun  9 23:17:30.794 UTC

Port                                            : CoherentDSP 0/0/0/13
Controller State                                : Admin Down
Inherited Secondary State                       : Normal
Configured Secondary State                      : Normal
Derived State                                   : Out Of Service
Loopback mode                                   : None
BER Thresholds                                  : SF = 1.0E-5  SD = 1.0E-7
Performance Monitoring                          : Enable
Bandwidth                                       : 200.0Gb/s

Alarm Information:
LOS = 0 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 = 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                                        : 0.00dB 

TTI :
        Remote IP addr                          : 0.0.0.0

FEC mode                                        : O_FEC

Flexo-Mode                                      : Enable
Flexo Details:
        Tx GID                                  : 1
        TX IID                                  : 3, 4, 
        Rx GID                                  : 0
        RX IID                                  : 0, 0, 

Flexo Peers Information:
        Controller                              : CoherentDSP0_0_0_12 
        OTUCn rate                              : OTUC2


AINS Soak                                       : None
AINS Timer                                      : 0h, 0m
AINS remaining time                             : 0 seconds

For 400G inverse muxponder, the flexo configuration on these coherent DSP controllers must be such that GID is the same on coherentDSP controllers on both port 12 and port 13, and IIDs are in the incremental order. In case if one of the node configurations is invalid, the Provisioning Failed alarm is raised on that particular controller. The Provisioning Failed alarm moves to the slice level in case you perform a line card reload.

The following sample configures the same IID on the coherentDSP 0/0/0/12 as that of coherentDSP 0/0/0/13 and shows the resulting Provisioning Failed alarm.

RP/0/RP0/CPU0:ios#configure 
Wed Jun  9 23:19:28.101 UTC
RP/0/RP0/CPU0:ios(config)#controller coherentDSP 0/0/0/12
RP/0/RP0/CPU0:ios(config-CoDSP)#flexo gid 1 iid 3,4
RP/0/RP0/CPU0:ios(config-CoDSP)#commit 
Wed Jun  9 23:20:08.971 UTC
RP/0/RP0/CPU0:ios(config-CoDSP)#end
RP/0/RP0/CPU0:ios#show alarms brief system active
Wed Jun  9 23:20:11.940 UTC

------------------------------------------------------------------------------------
Active Alarms 
------------------------------------------------------------------------------------
Location Severity Group     Set Time                 Description                                                                                                                                                                                                                                                
------------------------------------------------------------------------------------                                                                                                                                                                                                                         
0/0      Major  Controller 06/09/202123:20:10 UTC CoherentDSP0/0/0/12-Provisioning Failed

The following sample configures incremental IIDs in the coherentDSP 0/0/0/12 and coherent DSP 0/0/0/13 and verifies that the Provisioning Failed alarms cleared:

RP/0/RP0/CPU0:ios(config)#controller coherentDSP 0/0/0/12
RP/0/RP0/CPU0:ios(config-CoDSP)#flexo gid 1 iid 5,6            
RP/0/RP0/CPU0:ios(config-CoDSP)#controller coherentDSP 0/0/0/13
RP/0/RP0/CPU0:ios(config-CoDSP)#flexo gid 1 iid 7,8            
RP/0/RP0/CPU0:ios(config-CoDSP)#commit 
Wed Jun  9 23:21:06.335 UTC
RP/0/RP0/CPU0:ios(config-CoDSP)#end

The following sample verifies the IID configurations in the coherentDSP 0/0/0/12 and coherentDSP 0/0/0/13:

RP/0/RP0/CPU0:ios#show controllers coherentDSP 0/0/0/12
Wed Jun  9 23:21:15.321 UTC

Port                                            : CoherentDSP 0/0/0/12
Controller State                                : Admin Down
Inherited Secondary State                       : Normal
Configured Secondary State                      : Normal
Derived State                                   : Out Of Service
Loopback mode                                   : None
BER Thresholds                                  : SF = 1.0E-5  SD = 1.0E-7
Performance Monitoring                          : Enable
Bandwidth                                       : 200.0Gb/s

Alarm Information:
LOS = 0 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 = 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                                        : 0.00dB 

TTI :
        Remote IP addr                          : 0.0.0.0

FEC mode                                        : O_FEC

Flexo-Mode                                      : Enable
Flexo Details:
        Tx GID                                  : 1
        TX IID                                  : 5, 6, 
        Rx GID                                  : 0
        RX IID                                  : 0, 0, 

Flexo Peers Information:
        Controller                              : CoherentDSP0_0_0_13 
        OTUCn rate                              : OTUC2


AINS Soak                                       : None
AINS Timer                                      : 0h, 0m
AINS remaining time                             : 0 seconds


RP/0/RP0/CPU0:ios#show controllers coherentDSP 0/0/0/13
Wed Jun  9 23:21:20.348 UTC

Port                                            : CoherentDSP 0/0/0/13
Controller State                                : Admin Down
Inherited Secondary State                       : Normal
Configured Secondary State                      : Normal
Derived State                                   : Out Of Service
Loopback mode                                   : None
BER Thresholds                                  : SF = 1.0E-5  SD = 1.0E-7
Performance Monitoring                          : Enable
Bandwidth                                       : 200.0Gb/s

Alarm Information:
LOS = 0 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 = 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                                        : 0.00dB 

TTI :
        Remote IP addr                          : 0.0.0.0

FEC mode                                        : O_FEC

Flexo-Mode                                      : Enable
Flexo Details:
        Tx GID                                  : 1
        TX IID                                  : 7, 8, 
        Rx GID                                  : 0
        RX IID                                  : 0, 0, 

Flexo Peers Information:
        Controller                              : CoherentDSP0_0_0_12 
        OTUCn rate                              : OTUC2


AINS Soak                                       : None
AINS Timer                                      : 0h, 0m
AINS remaining time                             : 0 seconds

The following sample verifies that the Provisioning Failed alarm was cleared:

                 
RP/0/RP0/CPU0:ios#show alarms brief system history

------------------------------------------------------------------------------------
History Alarms 
------------------------------------------------------------------------------------ --------------------------------- 
Location Severity Group       Set Time                Description                                Clear Time
                                                                                                                                                                                                                                  
                                                                                                                       
-----------------------------------------------------------------------------------------------------------------------
0/2      Major   Controller  09/30/2021 14:42:01 UTC  CoherentDSP0/2/0/12 - Provisioning Failed 09/30/2021 14:42:25 UTC