Cisco NCS 1002 Troubleshooting: General Diagnostics Guide

The Cisco NCS 1002 is a compact optical transport platform, and when a node goes unreachable or a trunk port fails to come up, the right diagnostic order saves hours of guesswork. This guide condenses Cisco's official NCS 1002 troubleshooting chapter (IOS XR releases 6.3.x through 7.3.x) into a practical procedure set: validating software installation, isolating node and management-plane failures, using loopbacks to section optical connectivity problems, and verifying alarms and onboard failure logs. It is written for transport engineers who need the exact commands, not a theory lecture.

Validate the Software Installation

Start by confirming the running software and package state:

RP/0/RP0/CPU0:ios# show version
RP/0/RP0/CPU0:ios# show install active summary

Node Unreachable or Console Unresponsive

When the node is unreachable, work through in order: check the management interface state and IP configuration, verify the console connection parameters, then inspect hardware module status:

show platform
show environment
show controllers management Ethernet0/RP0/CPU0/0

Optical Connectivity: Use Loopbacks

Loopbacks are the fastest way to section optical faults. A facility loopback loops the signal back at the port without transmitting downstream; a terminal (inward) loopback loops it at the card. Test each segment of the path — source node, intermediate nodes, destination node — to isolate whether the problem is in the client side, the trunk, or the line system. Useful companion checks:

• LLDP snooping — discover the far-end device and validate the optical link is carrying frames.
• Trail trace identifier (TTI) — confirm the expected path trace is received on each section.

Troubleshoot Trunk and Breakout Ports

For trunk port issues, verify the controller state and configuration; for breakout ports, confirm the breakout mapping matches the optics installed and that the channel configuration is consistent on both ends. A failed commit after a config change is typically a semantic error — review with:

show configuration failed

Alarms, Logs and Failure Data

Check active alarms and pull failure logs before contacting support:

show alarms brief
show logging
show tech-support

Onboard failure logging (OBFL) and process crash dumps help identify hardware versus software faults. For optical module issues, also see our H3C 光模块故障排查手册 and the Infinera DWDM resource guide.

原文链接：https://www.cisco.com/c/en/us/td/docs/optical/ncs1000/63x/troubleshooting/guide/troubleshooting-guide-63x/general-troubleshooting.html