Automating Cisco Device Info Collection: Scripts and Best Practices

Cisco Device Info: Quick Reference Guide for Network Engineers

Purpose

A concise go-to reference for quickly finding and interpreting essential information about Cisco routers, switches, and other devices during configuration, troubleshooting, audits, or inventory.

Key show commands (most useful)

• show version — OS version, device model, uptime, boot image, license, memory/flash.
• show running-config — active configuration (interfaces, VLANs, routing, access lists).
• show startup-config — saved config that loads on boot.
• show inventory — hardware module/FRU details and serial numbers.
• show ip interface brief — interface list, IPs, and status.
• show interfaces — interface counters, errors, bandwidth, duplex.
• show logging — system log buffer; use with terminal logging or logging host checks.
• show platform (or show tech-support) — platform-specific hardware and diagnostics.
• show processes cpu | memory — CPU/memory utilization and top processes.
• show version | include uptime|System image file|license — quick filtered outputs.

Common fields to note and why

• Model & PID: ensures correct hardware capabilities and replacement parts.
• Serial number (SN): needed for RMA and warranty checks.
• IOS/IOS XE/IOS XR version: compatibility, feature availability, bugs, and upgrade planning.
• Uptime: helps correlate recent changes or incidents.
• License type & feature set: determines enabled features (e.g., security, UC).
• Active config vs startup-config differences: reveals unsaved changes.
• Interface status & IPs: core for connectivity and routing issues.
• MAC addresses: layer‑2 troubleshooting and ARP resolution.
• Memory/CPU stats and errors: performance troubleshooting.

Quick troubleshooting checklist

1. Confirm device reachable (ping/traceroute) and management access (SSH/console).
2. Check interface status: physical/link errors, duplex, speed.
3. Verify IP addressing and routing table entries.
4. Review recent logs for errors or reloads.
5. Check CPU/memory spikes and offending processes.
6. Inspect ACLs and NAT affecting traffic.
7. Confirm licenses and feature availability if features missing.
8. If hardware suspected, review inventory and platform diagnostics.

Useful one-liners and filters

• show version | include IOS
• show running-config | section interface GigabitEthernet0/1
• show interfaces GigabitEthernet0/1 | include line protocol|input errors|output errors
• show logging | include %SYS-5-RESTART

Automation & collection tips

• Use SSH with scripts (Python + Netmiko/NAPALM) to collect show outputs regularly.
• Store outputs centrally with timestamps and device metadata for audits.
• Run config diff tools to detect unsaved changes or unauthorized edits.
• Include serials, model, IOS, and license in inventory exports.

Security & change control notes

• Avoid sharing full configs or show tech-support publicly—redact passwords, keys, and user data.
• Keep backups of startup-config and record configuration changes in change management.
• Regularly check for IOS security advisories and apply patches per maintenance windows.

Quick command reference (cheat sheet)

• show version
• show inventory
• show running-config
• show ip interface brief
• show interfaces
• show logging
• show processes cpu | memory
• show tech-support

If you want, I can generate a printable one‑page cheat sheet or a script to collect these outputs from multiple devices.