Cisco NCS 1002 - Troubleshooting the Trunk Port

Indentifier Mismatch
What to do next
1. If the transmit or expected string was changed, restore the original string.
2. Use a loopback. For more information, see Using Loopbacks, on page 18.
Troubleshooting the Trunk Port
Step 1 show controller coherentDSP R/S/I/P
Displays details of the coherent DSP controller.
Example:
RP/0/RP0/CPU0:ios# show controller coherentDSP 0/0/0/6
Tue Nov 17 22:57:20.724 UTC
Port : CoherentDSP 0/0/0/6
Controller State : Down
Secondary State : Normal
Derived State : In Service
Loopback mode : None
BER Thresholds : SF = 1.0E-5 SD = 1.0E-7
Performance Monitoring : Enable
Alarm Information:
LOS = 2 LOF = 1 LOM = 2
OOF = 0 OOM = 0 AIS = 0
IAE = 0 BIAE = 0 SF_BER = 0
SD_BER = 0 BDI = 0 TIM = 0
FECMISMATCH = 0 FEC-UNC = 0
Detected Alarms : LOS
OTU TTI Sent
OPERATOR SPECIFIC ASCII :
:
OPERATOR SPECIFIC HEX : 00000000000000000000000000000000
: 00000000000000000000000000000000
OTU TTI Expected
OPERATOR SPECIFIC ASCII :
:
OPERATOR SPECIFIC HEX : 00000000000000000000000000000000
: 00000000000000000000000000000000
FEC mode : Soft-Decision 7
Network SRLG values : Not Configured
In the above output, you can verify the state of the controller and also verify the alarms related to the trunk port.
Step 2 show controller optics R/S/I/P
Displays details of the optics controller.
Example:
Troubleshooting Guide for Cisco NCS 1002, IOS XR Release 6.3.x
23
General Troubleshooting
Troubleshooting the Trunk Port