Cisco NCS 1010 and NCS 1020 Datapath Configuration Guide, IOS XR Releases 26.x.x

PDF

Cisco NCS 1010 and NCS 1020 Datapath Configuration Guide, IOS XR Releases 26.x.x

Automatic-In-Service (AINS) state

Updated: September 1, 2026

Want to summarize with AI?

Log in

This section explains how the Automatic-In-Service (AINS) state manages controller transitions and alarm reporting during system bootup and soak periods in NCS 1010.

The AINS state is an administrative state that

  • allows the OTS, OMS, and OCH datapath controllers to automatically move to the Automatic In Service state after a system bootup,

  • prevents alarms reporting to the EMS/NMS monitoring system during the soak time period, and

  • helps the affected ports to transition to the In-Service state after the soak time period expires.

In NCS 1010, AINS state affects the

  • OTS controllers on the COM ports for the OLT and E-OLT cards. See

  • OTS-OCH controllers after the optical cross connections are configured on the OLT and E-OLT cards.

  • OMS and OCH controllers for the passive devices. See

AINS does not affect for the line side OTS-OCH controllers on OLT, E-OLT, ILA and E-ILA cards. Line side OTS-OCH controllers are labeled as OTS-OCH 0/0/0/0/x.

AINS soak time period

Soak time period is a timed delay that

  • keeps the affected NCS 1010 ports in the AINS state for defined duration after system boot,

  • suppress active alarms until the ports transition to the In-Service state, and

  • lasts for one minute by default.

Characteristics of soak time period

The characteristics of soak timer period are:

  • The soak time period for the AINS state is fixed and not configurable.

  • The soak timer restarts automatically during line card cold reloads or power cycles.

  • During the soak time period, any alarms are suppressed and can be viewed using the show alarms brief system conditions command.

  • When all alarms are resolved, the system transitions the affected ports to the In-Service state.

After an NCS 1010 chassis boots up, its COM ports for OLT and E-OLT cards enter the AINS state. The soak time period begins, lasting one minute. During this time, alarms are suppressed. When the soak time ends, if ther are no outstanding alarms, the ports move into In-Service.

  • The soak time period is a predefined value.

  • If an active alarm persists after the soak time, the affected port will not transition to In-Service.

A soak time period acts like a 'buffer zone' that delays action, ensuring that transient issues do not trigger alarms during initial startup or recovery.

Verify the AINS state and the suppressed alarms

Follow the steps to verify the administrative state of the affected controller types that are in AINS state.

  • OLT and E-OLT cards: OTS and OTS-OCH controllers

  • Passive modules: OCH and OMS controllers

When add/drop COM ports enter the AINS state, the alarms reported on those ports are suppressed during the soak time period. Use the steps in this task to check the adminstrative state of those ports and their alarms.

Procedure

  1. Use the show controllers ots R/S/I/P command to check the adminstrative status of the OTS controller.

    Example:

    This command displays the OTS controller statistics for Add/Drop 2 port in OLT and E-OLT cards.

    RP/0/RP0/CPU0:ios#show controllers ots 0/0/0/2

    This output displays the OTS controller statistics highlighting the adminstrative state as Automatic In Service.

    Wed Jun 22 09:43:04.356 UTC

Controller State: Down 

Transport Admin State: Automatic In Service 

LED State: Red 

Alarm Status:
-------------
Detected Alarms:
RX-LOS-P
TX-POWER-FAIL-LOW

Alarm Statistics:
-----------------
RX-LOS-P = 1
RX-LOC = 0
TX-POWER-FAIL-LOW = 1
INGRESS-AUTO-LASER-SHUT = 0
INGRESS-AUTO-POW-RED = 0
INGRESS-AMPLI-GAIN-LOW = 0
INGRESS-AMPLI-GAIN-HIGH = 0
EGRESS-AUTO-LASER-SHUT = 0
EGRESS-AUTO-POW-RED = 0
EGRESS-AMPLI-GAIN-LOW = 0
EGRESS-AMPLI-GAIN-HIGH = 0
HIGH-TX-BR-PWR = 0
HIGH-RX-BR-PWR = 0
SPAN-TOO-SHORT-TX = 0
SPAN-TOO-SHORT-RX = 0

Parameter Statistics:
---------------------
Total RX Power = -50.00 dBm
Total TX Power = -50.00 dBm
Ingress Ampli Gain = 0.0 dB
Ingress Ampli Tilt = 0.0 dB



Configured Parameters:
------------
Ingress Ampli Gain = 16.0 dB
Ingress Ampli Tilt = 0.0 dB

  2. Use the show controllers ots-och R/S/I/P/x command to check the adminstrative status of the OTS-OCH controller.

    Example:

    This command displays the OTS-OCH cross-connect controller statistics for Add/Drop 13 port in E-OLT cards.

    RP/0/RP0/CPU0:ios#show controllers ots-och 0/0/0/13/20

    This output displays the OTS-OCH controller statistics highlighting the adminstrative state as Automatic In Service.

    
Tue Jul 12 10:19:48.838 UTC

 Controller State: Down 

 Transport Admin State: Automatic In Service 

         Alarm Status:
         -------------
         Detected Alarms: 
                 RX-LOS-P    
                 TX-POWER-FAIL-LOW    

         Alarm Statistics:
         -----------------
         RX-LOS-P = 1          
         TX-POWER-FAIL-LOW = 1          

         Parameter Statistics:
         ---------------------
         Total RX Power = -50.00 dBm 
         Total TX Power = -50.00 dBm 


         Cross Connect Info:
         ---------------------
         line Channel  = Ots-Och0/0/0/0/20
          
          
          
          
         Configured Parameters:
         -------------
         Rx Low Threshold = -50.0 dBm 
         Tx Low Threshold = -50.0 dBm

  3. Use the show controllers och R/S/I/P command to check the adminstrative status of the OCH controller in passive modules.

    Example:

    This command displays the OCH controller statistics for port 0 in passive modules.

    RP/0/RP0/CPU0:ios#show controllers och 0/1/0/0

    This output displays the OCH controller statistics highlighting the adminstrative state as Automatic In Service.

    Wed Jul 6 14:28:12.500 UTC

Controller State: Down

Transport Admin State: Automatic In Service

LED State: Red

Alarm Status:
-------------
Detected Alarms:
RX-LOS-P

Alarm Statistics:
-----------------
RX-LOS-P = 1
TX-POWER-FAIL-LOW = 0

Parameter Statistics:
---------------------
TX Power = -50.00 dBm
RX Power = -20.72 dBm

    This example displays the OCH controller statistics after AINS Soak time expiry. When the soak time expires, the Transport Admin State of OCH controller changes from Automatic In Service to In Service.

    Wed Jul 6 14:29:59.242 UTC

Controller State: Up

Transport Admin State: In Service

LED State: Off

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


Alarm Statistics:
-----------------
RX-LOS-P = 1
TX-POWER-FAIL-LOW = 0

Parameter Statistics:
---------------------
TX Power = -50.00 dBm
RX Power = 2.79 dBm

  4. Use the show controllers oms R/S/I/P command to check the adminstrative status of the OMS controller in passive modules.

    Example:

    This command displays the OMS controller statistics for port 25 in NCS1K-MD-32O/E-C passive module.

    RP/0/RP0/CPU0:ios#show controllers oms 0/1/0/25

    This output displays the OMS controller statistics highlighting the administrative state as Automatic In Service.

    
Tue Jul 12 10:32:05.258 UTC

 Controller State: Down 

 Transport Admin State: Automatic In Service 

 LED State: Red 

         Alarm Status:
         -------------
         Detected Alarms: 
                 RX-LOS-P    

         Alarm Statistics:
         -----------------
         RX-LOS-P = 1          
         TX-POWER-FAIL-LOW = 0          

         Parameter Statistics:
         ---------------------
         TX Power = -7.40 dBm 
         RX Power = -19.91 dBm

  5. (Optional) Use the show alarms brief system conditions command to check the alarms suppressed for the controllers in AINS state.

    Example:

    This command displays the suppressed alarms in AINS state. 
    RP/0/RP0/CPU0:ios#show alarms brief system conditions

    This output displays the alarms reported for the affected controller types in AINS state.

    Mon Jul 25 05:43:50.073 UTC

------------------------------------------------------------------------------------
Conditions 
------------------------------------------------------------------------------------
Location        Severity     Group            Set Time                   Description                                                                                                                                                                                                                                                
------------------------------------------------------------------------------------
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Och0/1/0/1 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Och0/1/0/2 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Och0/1/0/4 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Och0/1/0/5 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Och0/1/0/6 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Och0/1/0/7 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Och0/1/0/8 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Och0/1/0/9 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Och0/1/0/10 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Och0/1/0/11 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Och0/1/0/12 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Och0/1/0/13 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Och0/1/0/14 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Och0/1/0/15 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Och0/1/0/16 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Och0/1/0/17 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Och0/1/0/18 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Och0/1/0/19 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Och0/1/0/21 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Och0/1/0/22 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Oms0/1/0/31 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Oms0/1/0/26 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Oms0/1/0/27 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Oms0/1/0/28 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Oms0/1/0/29 - Loss of Signal - Payload
0/1             Critical     Controller       07/21/2022 11:11:54 UTC    Oms0/1/0/30 - Loss of Signal - Payload
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/33 - Output OTS Power Reading Below The Fail-Low Threshold
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/33 - Loss of Signal - Payload
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/9 - Output OTS Power Reading Below The Fail-Low Threshold
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/9 - Loss of Signal - Payload 
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/8 - Output OTS Power Reading Below The Fail-Low Threshold
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/8 - Loss of Signal - Payload 
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/7 - Output OTS Power Reading Below The Fail-Low Threshold
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/7 - Loss of Signal - Payload 
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/6 - Output OTS Power Reading Below The Fail-Low Threshold
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/6 - Loss of Signal - Payload 
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/5 - Output OTS Power Reading Below The Fail-Low Threshold
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/5 - Loss of Signal - Payload 
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/4 - Output OTS Power Reading Below The Fail-Low Threshold
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/4 - Loss of Signal - Payload 
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/3 - Output OTS Power Reading Below The Fail-Low Threshold
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/3 - Loss of Signal - Payload 
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/2 - Output OTS Power Reading Below The Fail-Low Threshold
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/2 - Loss of Signal - Payload 
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/32 - Output OTS Power Reading Below The Fail-Low Threshold
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/32 - Loss of Signal - Payload
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/31 - Output OTS Power Reading Below The Fail-Low Threshold
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/31 - Loss of Signal - Payload
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/30 - Output OTS Power Reading Below The Fail-Low Threshold
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/30 - Loss of Signal - Payload
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/29 - Output OTS Power Reading Below The Fail-Low Threshold
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/29 - Loss of Signal - Payload
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/28 - Output OTS Power Reading Below The Fail-Low Threshold
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/28 - Loss of Signal - Payload
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/25 - Output OTS Power Reading Below The Fail-Low Threshold
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/25 - Loss of Signal - Payload
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/10 - Output OTS Power Reading Below The Fail-Low Threshold
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/10 - Loss of Signal - Payload
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/11 - Output OTS Power Reading Below The Fail-Low Threshold
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/11 - Loss of Signal - Payload
0/0             Critical     Controller       07/21/2022 11:12:00 UTC    Ots0/0/0/12 - Output OTS Power Reading Below The Fail-Low Threshold