Configuration Guide for Cisco NCS 1004, IOS XR Release 25.x.x

PDF

Configuration Guide for Cisco NCS 1004, IOS XR Release 25.x.x

Trail trace identifier

Updated: July 31, 2026

Want to summarize with AI?

Log in

This section explains how Trail Trace Identifiers (TTIs) function on the NCS 1004 platform, enabling operators to trace optical signals from source to destination, ensuring signal integrity and facilitating troubleshooting.

A trail trace identifier is a network signaling feature that

  • enables identification of a signal's path from the source to the destination within the network,

  • allows configuration of the sent or expected identifier string in ASCII format, and

  • supports up to 64 characters for each identifier string.

TTI behavior

When the expected TTI string does not match the received TTI trace string, the controller goes down and the OTUK-TIM alarm is raised.

Configure TTI on OTN-XP card

Configure the Trail Trace Identifier (TTI) string (sent or expected) on supported controller types for the OTN-XP card.

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 Release 7.3.1, coherentDSP controller supports only the full ASCII string format.

From Release 7.3.2, coherentDSP controller supports SAPI/DAPI string format in addition to the full ASCII string format.

You can configure TTI for these muxponder modes:

  • 10G-Grey-MXP

  • 4x100G-MXP-400G-TXP

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

Table 1. ASCII format supported on each muxponder mode

Muxponder mode

ASCII with character string

Controller

10G Grey

Full ASCII

64-character

OTU2, OTU2E, OTU4, ODU4, ODU2E (10G mapper)

SAPI ASCII

15-character

OTU2, OTU2E, OTU4, ODU4, ODU2E (10G mapper)

DAPI ASCII

15-character

OTU2, OTU2E, OTU4, ODU4, ODU2E (10G mapper)

Operator-specific ASCII

32-character

OTU2, OTU2E, OTU4, ODU4, ODU2E (10G mapper)

4x100G-MXP-400G-TXP

Full ASCII

64-character

OTU4, coherentDSP, ODUC4, ODU4 (100G mapper), and ODU-FLEX (400G mapper)

SAPI ASCII

15-character

OTU4, coherentDSP, ODUC4, ODU4 (100G mapper), and ODU-FLEX (400G mapper)

DAPI ASCII

15-character

OTU4, coherentDSP, ODUC4, ODU4 (100G mapper), and ODU-FLEX (400G mapper)

Operator-specific ASCII

32-character

OTU4, coherentDSP, ODUC4, ODU4 (100G mapper), and ODU-FLEX (400G mapper)
Follow these steps to configure TTI on an OTN-XP card:

Procedure

Run the configure controllercontroller-type R/S/I/P tti {sent | expected} {ascii | sapi ascii | dapi ascii | operator-specific ascii } tti-string to configure the TTI on controllers.

Example:

Note

It is recommened to configure TTI in the SAPI/DAPI ASCII format.

Note

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

Example:

This is a sample configuration on ODU4 controller.


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

This is a sample output of the TTI configuration on the ODU4 controller.


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

Example:

To configure TTI on OTUCn-REGEN mode on the OTN-XP card.

This sample displays how to configure TTI on a coherent DSPcontroller port 12 on the OTUCn-REGEN mode.

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

This sample verifies the TTI configuration on the inverse muxponder configured on the OTUCn-REGEN mode.


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

Example:

To configure TTI on Inverse Muxponder Configuration on the OTN-XP Card.

This 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

This 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

TTI is configured on the controller.

Configure TTI on QXP card

Enable and customize the Trail Trace Identifier (TTI) parameters for increased traceability and service assurance on NCS 1004 QXP card controllers.

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

This table lists the ASCII format that is supported for TTI:

Table 2. ASCII formats supported for TTI
ASCII with character string Controller

Full ASCII

64-character

CoherentDSP,odu4,odu-flex

SAPI ASCII

15-character

CoherentDSP,odu4,odu-flex

DAPI ASCII

15-character

CoherentDSP,odu4,odu-flex

Operator-specific ASCII

32-character

CoherentDSP,odu4,odu-flex

Follow these steps to configure the TTI on a QXP card controller:

Procedure

Run the configure controllercontroller-type R/S/I/P tti {sent | expected} {ascii | sapi ascii | dapi ascii | operator-specific ascii } tti-string command to configure the TTI sent and expected strings on the CoherentDSP controller.

Example:

This 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

This 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

This 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

This 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

This 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

This 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

TTI is configured on the QXP card controller.