Cisco NCS 1010 Optical Applications Configuration Guide, IOS XR Release 25.x.x

PDF

Automatic OTDR scans

Updated: February 5, 2026

Overview

This topic explains how automatic OTDR scans function as a fiber diagnostics feature, automatically triggering OTDR tests in response to events such as span faults and restorations. It also describes bidirectional scanning capabilities for comprehensive fault detection and rapid fault localization through alarm monitoring.

An automatic OTDR scan is a fiber diagnostics feature that

  • automatically triggers OTDR tests in response to specific events such as span fault, span restoration, device power cycling, and line card cold reload that affect the optical span,

  • enables RX directionscanning for comprehensive fault detection and prevents scan collisions, and

  • provides rapid fault localization by monitoring and raising relevant alarms during scan execution.

Table 1. Feature History
Feature Name Release Information Feature Description

Automatic OTDR Scan

Cisco IOS XR Release 7.11.1

An OTDR scan is automatically triggered on Rx direction, whenever events such as span fault, span restore, device power cycle, and line card cold reload occur. The automatic scan lets you quickly identify fiber failure type and fault location.

Commands added to enable and view OTDR results:

otdr auto-scan [enable | disable]

show olc otdr-status [details]

Autoscan direction and duration

In Release 7.11.1, autoscan is performed only in the Rx direction, regardless of whether the span fault is unidirectional or bidirectional.

In both span up and span down events, the bidirectional OTDR scan process terminates after both Rx and Tx scans have been completed successfully. You can stop the scan sequence by disabling the autoscan feature.

The OTDR autoscan takes less than three minutes to complete. During the autoscan, the OTDR-SCAN-IN-PROGRESS-RX alarm is raised and gets cleared once the scan is finished.


Autoscan behavior

Autoscan manages OTDR scanning by coordinating access to scanning resources and responding to interactions with manual and application-triggered scans:

Autoscan manages OTDR scanning operations in these ways:

  • Autoscan locks the OTDR resource to prevent manual scan triggers using the otdr-start command. However, if a manual scan is already in progress, autoscan waits for its completion before proceeding.

  • Autoscan terminates any ongoing scan that was triggered by other applications, such as Raman turn-up.

  • During autoscan, if a change in Span Status is detected, it terminates the ongoing scan and automatically initiates a new autoscan.


Criteria for span fault and restoration events

This table lists the detection criteria for span fault and restoration events.
Table 1. Definition of span up and span down events
Events Non-Raman span Raman span Raman span with dual safety configured

Span Down

Raise of RX-LOS-P alarm at OSC controller

Raise of RX-LOS-P alarm at DFB controller

Raise of RX-LOS-P alarm at both OSC and DFB controllers

Span Up

Clearing of RX-LOS-P alarm at OSC controller

Clearing of RX-LOS-P alarm at DFB controller

Clearing of RX-LOS-P alarm at both OSC and DFB controllers


Fault and restoration scenarios in bidirectional OTDR

This reference describes how bidirectional OTDR performs automatic scans in fiber networks during both fault (cut) and restoration conditions between nodes, detailing differences for OLT and ILA node types.

Unidirectional and bidirectional failures between two OLT nodes

This image illustrates the timeslot-based OTDR automatic scans in the event of bidirectional and unidirectional fiber cuts between Node A and Node B.

Figure 1. Bidirectional autoscan during span fault scenarios
Table 1. Bidirectional autoscan during span fault scenarios
Span fault How bidirectional scan is performed

Scenario 1:A unidirectional fiber cut occurs first, followed by a bidirectional fiber cut after some time.

The fiber cut happens in one fiber. This is marked as a red cross in the image:

  • In the first timeslot, Node A performs an Rx scan (NA-RX) for the cut fiber.

  • In the subsequent timeslot, Node A and Node B perform scan in the Tx direction (NA-TX, NB-TX).

The fiber cut happens in another fiber some time after the unidirectional cut. This is marked as a yellow cross in the image.

  • Only Node B performs the Rx scan. Node A does not perform any scan as there are no changes detected in Node A.

Scenario 2: Bidirectional cuts happen simultaneously

Both Node A and Node B perform the scans in the RX direction in the first timeslot (t0), and in the Tx direction for the subsequent timeslot.

Scenario 3: Node B is busy for some time when bidirectional cuts occur.

Node A performs an Rx scan in one timeslot and continues with the Tx scan in the next timeslot. While Node B waits for the current scan to complete, it starts the Tx scan in the second timeslot and continues the Rx scan in the following timeslot.

Unidirectional and bidirectional failure restoration between two OLT nodes

When a fiber fault is restored (span up), the NE and FE nodes coordinate Rx and Tx scans to prevent simultaneous scanning and scan collisions. In this process:

  • Rx and Tx scans are performed sequentially, one immediately after the other.

  • After restoration, both Tx and Rx scans are performed on the restored fiber, regardless of whether the original cut was unidirectional or bidirectional.

Unidirectional and bidirectional failure and restoration between two ILA nodes

Bidirectional autoscan behavior between two ILA nodes is the same as that of OLT nodes. The only difference is that the OTDR module is shared between the two line ports in an ILA node. If a simultaneous fault occurs on both sides, the two ports must serialize the scan operations. Each port performs its scan one after the other to avoid overlap and ensure accurate fault detection and restoration.


Configure automatic OTDR scan

Use this task to enable OTDR scan to run automatically during certain events.

Procedure

1.

Enter OTS controller configuration mode for the port on which you want to enable automatic OTDR scan.

Example:

RP/0/RP0/CPU0:ios#configure
RP/0/RP0/CPU0:ios(config)#optical-line-control controller Ots 0/0/0/0
2.

Enable automatic OTDR scan.

Example:


RP/0/RP0/CPU0:ios(config-olc-ots)#otdr auto-scan enable
RP/0/RP0/CPU0:ios(config)#commit
RP/0/RP0/CPU0:ios(config)#exit

If you want to disable the automatic OTDR scan, use the otdr auto-scan disable command.

Automatic OTDR scans are enabled for the selected port. The system will now run OTDR scans automatically during applicable events, allowing you to proactively monitor fiber links and detect faults without manual intervention.


Verify autoscan status

Use this procedure to verify the status of the autoscan.

Procedure

View the automatic OTDR scan results using the command show olc otdr-status [details].

Example:

This sample display the status of autoscan triggered due to a span fault. See Automatic OTDR scan results for more examples.

RP/0/RP0/CPU0:ios#show olc otdr-status details
Mon Sep 18 13:16:16.461 UTC
Controller                                    : Ots0/0/0/0
Auto-scan Start Time                          : NA
OTDR Auto-scan Status                         : RUNNING
Status Detail                                 : Starting on Span Down
Optical Span Status                           : Down
Trigger Event                                 : Span Fault
Last Trigger Event                            : Span Restore

RP/0/RP0/CPU0:ios#show olc otdr-status details
Mon Sep 18 13:16:33.304 UTC
Controller                                    : Ots0/0/0/0
Auto-scan Start Time                          : 2023-09-18 13:16:27
OTDR Auto-scan Status                         : RUNNING
Status Detail                                 : Waiting Scan Completion on Span Down
Optical Span Status                           : Down
Trigger Event                                 : Span Fault
Last Trigger Event                            : Span Restore

RP/0/RP0/CPU0:ios#show olc otdr-status details
Mon Sep 18 13:18:54.154 UTC
Controller                                    : Ots0/0/0/0
Auto-scan Start Time                          : 2023-09-18 13:16:27
OTDR Auto-scan Status                         : COMPLETED
Status Detail                                 : Completed on Span Down
Optical Span Status                           : Down
Trigger Event                                 : Span Fault
Last Trigger Event                            : Span Fault

What to do next

If events indicate potential fiber issues, review the SOR file or perform additional analysis as needed.

Automatic OTDR scan results

This table presents automatic OTDR scan results observed across different network scenarios.

Table 1. Automatic scan results
Network scenarios Sample OTDR scan results

Non-Raman span

RP/0/RP0/CPU0:ios#show olc otdr-status
Mon Sep 18 13:10:57.733 UTC
Controller                                     : Ots0/0/0/0
Auto-scan Start Time                           : NA
OTDR Auto-scan Status                          : DISABLED
Status Detail                                  : NA
Optical Span Status                            : UP
Trigger Event                                  : NA

RP/0/RP0/CPU0:ios#show olc otdr-status details
Mon Sep 18 13:11:00.565 UTC
Controller                                     : Ots0/0/0/0
Auto-scan Start Time                           : NA
OTDR Auto-scan Status                          : DISABLED
Status Detail                                  : NA
Optical Span Status                            : UP
Trigger Event                                  : NA
Last Trigger Event                             : NA

Raman span

RP/0/RP0/CPU0:ios#show olc otdr-status
Mon Sep 18 13:41:05.088 UTC
Controller                                     : Ots0/0/0/0
Auto-scan Start Time                           : NA
OTDR Auto-scan Status                          : DISABLED
Raman Turn Up Fiber Check                      : NA
Status Detail                                  : NA
Optical Span Status                            : UP
Trigger Event                                  : NA

RP/0/RP0/CPU0:ios#show olc otdr-status details
Mon Sep 18 13:41:08.825 UTC
Controller                                     : Ots0/0/0/0
Auto-scan Start Time                           : 2023-09-20 13:58:17
OTDR Auto-scan Status                          : DISABLED
Status Detail                                  : NA
Raman Turn Up Fiber Check                      : NA
Optical Span Status                            : UP
Trigger Event                                  : NA
Last Raman Turn Up Scan Time                   : NA     
Last Raman Turn Up Fiber Check                 : NA
Last Trigger Event                             : NA

Span restore

RP/0/RP0/CPU0:ios#show olc otdr-status details
Mon Sep 18 13:12:40.430 UTC
Controller                                    : Ots0/0/0/0
Auto-scan Start Time                          : NA
OTDR Auto-scan Status                         : RUNNING
Status Detail                                 : Starting on Span Up
Optical Span Status                           : Up
Trigger Event                                 : Span Restore
Last Trigger Event                            : NA

RP/0/RP0/CPU0:ios#show olc otdr-status details
Mon Sep 18 13:15:06.153 UTC
Controller                                    : Ots0/0/0/0
Auto-scan Start Time                          : 2023-09-18 13:12:42
OTDR Auto-scan Status                         : RUNNING
Status Detail                                 : Waiting Scan Completion on Span Up
Optical Span Status                           : Up
Trigger Event                                 : Span Restore
Last Trigger Event                            : NA

RP/0/RP0/CPU0:ios#show olc otdr-status details
Mon Sep 18 13:15:06.153 UTC
Controller                                    : Ots0/0/0/0
Auto-scan Start Time                          : 2023-09-18 13:12:42
OTDR Auto-scan Status                         : COMPLETED
Status Detail                                 : Completed on Span Up
Optical Span Status                           : Up
Trigger Event                                 : Span Restore
Last Trigger Event                            : Span Restore

Autoscan is unable to lock the OTDR resource

RP/0/RP0/CPU0:ios# show olc otdr-status details
Wed Sep 20 14:09:37.011 UTC
Controller                                     : Ots0/0/0/0
Auto-scan Start Time                           : 2023-09-20 13:58:17
OTDR Auto-scan Status                          : COMPLETED
Status Detail                                  : Failed due to Timeout
Raman Turn Up Fiber Check                      : NA
Optical Span Status                            : UP
Trigger Event                                  : Span Restore
Last Raman Turn Up Scan Time                   : NA     
Last Raman Turn Up Fiber Check                 : NA
Last Trigger Event                             : NA

Autoscan on one port is waiting for the OTDR resource, because the autoscan is running on another port.

RP/0/RP0/CPU0:ios#show olc otdr-status details
Mon Sep 18 15:57:43.671 UTC 
Controller                                     : Ots0/0/0/0
Auto-scan Start Time                           : 2023-09-18 15:57:43
OTDR Auto-scan Status                          : COMPLETED
Status Detail                                  : Waiting for OTDR Resource
Raman Turn Up Fiber Check                      : NA
Optical Span Status                            : UP
Trigger Event                                  : Span Restore
Last Raman Turn Up Scan Time                   : NA     
Last Raman Turn Up Fiber Check                 : NA
Last Trigger Event                             : NA

Autoscan is enabled and Raman turnup is disabled on a Raman span

In this case

  • On the span down event, the autoscan is triggered.

  • On the span up event, autoscan is not triggered and OTDR Autoscan Status will be IDLE, because Raman pumps are turned on before the start of autoscan.

  • On the span up event, autoscan is triggered and OTDR Autoscan Status is displayed as RUNNING.

RP/0/RP0/CPU0:ios#show olc otdr-status details
Sat Sep 23 12:42:11.304 UTC
Controller                                     : Ots0/0/0/0
Auto-scan Start Time                           : NA
OTDR Auto-scan Status                          : IDLE
Status Detail                                  : NA
Raman Turn Up Fiber Check                      : NA
Optical Span Status                            : UP
Trigger Event                                  : Span Fault
Last Raman Turn Up Scan Time                   : NA     
Last Raman Turn Up Fiber Check                 : NA
Last Trigger Event                             : Span Restore

Ongoing autoscan is stopped by the user

RP/0/RP0/CPU0:ios#show olc otdr-status details
Mon Sep 18 15:08:27.370 UTC
Controller                                     : Ots0/0/0/0
Auto-scan Start Time                           : 2023-09-18 15:08:09
OTDR Auto-scan Status                          : COMPLETED
Status Detail                                  : Stopped by User
Raman Turn Up Fiber Check                      : NA
Optical Span Status                            : DOWN
Trigger Event                                  : Span Fault
Last Raman Turn Up Scan Time                   : 2023-09-18 14:55:40     
Last Raman Turn Up Fiber Check                 : Success
Last Trigger Event                             : Span Restore

See OTDR scan status for a list of the different OTDR scan statuses and their definitions.


OTDR scan status

This section describes and explains the various OTDR statuses that appear when using the show olc controller ots R/S/I/P otdr-status and show controller ots R/S/I/P otdr-info commands.
Table 1. OTDR scan status
Scan status Description

Measuring

OTDR scan is currently in progress.

Data Processing

OTDR scan has completed, and the data is ready for review

Data Ready

OTDR scan is stopped by the user, when it is in progress.

Stopped

OTDR is processing data just before populating the event table.

Error

The OTDR status may occasionally enter an Error state for various unpredictable reasons. One possible cause is a timeout event, which occurs if the scan is not completed within five minutes. In such cases, no SOR files or event table is generated. It is important to note that this is a rare occurrence. You can still initiate the OTDR scan to obtain the scan results.

This table explains the various OTDR scan statuses that are applicable for manual and autoscan.

Table 2. OTDR scan status applicable for manual and autoscan
Type of OTDR scan Scan Status

show olc controller ots R/S/I/P otdr-status

show controller ots R/S/I/P otdr-info

Manual

NA

  • Measuring

  • Data Processing

  • Data Ready

  • Stopped

  • Error

Autoscan

  • Measuring

  • Data Processing

  • Data Ready

  • Stopped

  • Error

  • Measuring

  • Data Processing

  • Data Ready

  • Stopped

  • Error