Cisco IOS XR TAC Command List: Collect Before the Case

Nothing slows down a Cisco TAC case more than a back-and-forth asking for missing command output. The official IOS XR quick-reference command list tells you exactly what to collect before you open the ticket — platform state, install history, configuration commits, routing and forwarding counters. This article explains the list, groups the commands by what they diagnose, and shows why each block matters for ASR 9000, NCS and Cisco 8000 platforms.

Why Collect IOS XR Diagnostic Output Up Front

IOS XR is a distributed, commit-based operating system: configuration errors, FPD issues and NP drops each hide in different subsystems. The TAC list is designed so one paste session captures every subsystem snapshot, letting engineers triage without repeated calls. Enable logging on your SSH/telnet client and paste the blocks exactly as shown.

Core System State Commands

term length 0
show platform
show install active summary
show version
show hw-module fpd
show diag
show logging
show install log
show running
show configuration failed
show configuration commit changes all
show configuration history

These answer the three questions that start every case: what hardware is present, what software is running (including committed installs and FPD versions), and whether any configuration commit has failed.

Redundancy and Hardware Health

show redundancy
show redundancy summary
show environment
admin show environment
show led
show context location all
show processes cpu
show processes blocked location all
show watchdog memory-state

RP failover state, environment thresholds and blocked processes catch the classic "router reloads itself" causes before they become outages.

Routing, Forwarding and MPLS Plane Commands

show ospf neighbor
show bgp sessions
show bgp summary
show rib update-groups
show tcp brief
show l2vpn xconnect
show mpls traffic-eng tunnels
show bfd session
show drops
show controllers np counters all

These expose control-plane adjacency health (OSPF/BGP), label-switched path state (L2VPN xconnect, TE tunnels, BFD) and data-plane drops — the first place packet loss shows up on ASR 9000 and NCS platforms. For NCS family, add show asic-errors all detail location 0/RP0/CPU0 and show alarms brief system active.

Combine this collection routine with our multi-vendor CLI cheat sheet and OSPF neighbor troubleshooting guide for day-to-day triage. Automation-minded teams can wrap these commands in Ansible playbooks to collect them fleet-wide.

原文链接：https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-xr-software/215365-quick-reference-guide-to-collect-tac-req.pdf