Cisco switch fleet: How to generate a compliance report

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

What this guide covers

Catalyst Center Compliance dashboard OR custom Python script comparing config baselines.

Resolve

1. Define golden baseline (security hardening, AAA, NTP, etc.).
2. Pull each device's running config.
3. Diff against baseline; flag deltas.
4. Output to JSON / HTML report.
5. Schedule weekly + alert on drift.

Sample

# Python snippet using netmiko + diff
for device in inventory:
    conn = ConnectHandler(**device)
    cfg = conn.send_command('show running-config')
    diff = list(difflib.unified_diff(baseline, cfg.splitlines(keepends=True)))
    if diff:
        print(f'DRIFT on {device["host"]}')

Best practices

• Always test on a single device or sandbox before fleet rollout.
• Keep configurations in version control (Git).
• Use AAA + RBAC for the automation account; never embed credentials in code.
• Build pre/post-change validation into your pipeline.

Frequently asked questions

Will this work on my exact IOS-XE / ASA version?

The procedure reflects current IOS-XE 17.x and ASA 9.20 behaviour. Older trains (15.x, 9.16 ASA) may need minor syntax adjustments, use ? in the CLI.

Should I open a TAC case immediately?

Open one if you suspect hardware failure or the symptom persists after a maintenance-window reload. Make sure your SmartNet is active first.

Where can I find the Cisco official documentation?

https://www.cisco.com/c/en/us/support/all-products.html: search the product family + feature name.

Is this procedure safe in production?

Test in a lab or maintenance window first. Capture pre-change state so you can roll back.

Related guides

• All Cisco fix guides → /cisco/
• Cisco IOS error messages → /cisco/section/ios_error_messages.html
• Cisco troubleshooting by symptom → /cisco/section/troubleshoot_symptoms.html

References

• Cisco System Message Guide for IOS-XE / IOS
• Cisco Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/
• Cisco Smart Software Manager: https://software.cisco.com
• Cisco TAC: https://mycase.cloudapps.cisco.com/case

Reference material, not professional advice. Validate against your specific IOS-XE version and test in a non-production environment before applying.

Identify

When this symptom shows up on a Cisco device, three patterns repeat:

1. Recent firmware update changed behavior, the symptom started within a week of an OTA push. Rollback or wait for the hotfix. 2. Environmental trigger. temperature, humidity, line voltage, network changes. Look at what changed in the environment. 3. Cumulative wear, components like batteries, gaskets, fans degrade over time. Replace the consumable rather than chasing a software fix.

Knowing which pattern applies saves time on the wrong fix.

Safety + preconditions

Before any work on a Cisco device:

• Unplug from mains for any internal-access procedure.
• Discharge stored energy (capacitors in PSUs, residual battery charge) per manufacturer guidance.
• Use ESD-safe handling for boards and modules: no carpet, no wool sleeves.
• Avoid moisture; never apply liquids near vents or connectors.
• If you smell smoke, see scorch marks, or feel uneven heat, stop and escalate.

Validate

On a Cisco device, the test is rarely "reboot and see". Use this list:

• Active reproduction: trigger the original failure path on purpose.
• Indirect reproduction: do an activity that would expose the same subsystem.
• Status indicator review: every LED / display / app status should be green.
• 24-hour soak: leave the device under normal load overnight; check the next morning.
• Telemetry check: review the device or app's diagnostic log for new error entries.

When to call Cisco support instead

Escalate if:

• The same symptom returns within 24 hours of a clean fix.
• You see physical damage (burn marks, swollen battery, cracked PCB).
• The device is in warranty and a hardware replacement is the cheaper outcome.
• Repair requires specialised tools you don't own (alignment jigs, calibration software).
• Following the official path keeps the warranty intact, which matters more than the time spent.

More frequently asked questions

Can I roll this back if something breaks?

Yes for software-level changes (firmware rollback, config rollback). Hardware changes are usually one-way. Always back up settings before starting.

Why is this happening on a brand-new unit?

Out-of-box defects do occur. If you've owned the device under 30 days and the symptom persists after a factory reset, escalate to the seller for replacement under DOA terms before opening a manufacturer support case.

Does this affect other devices on my network?

Generally no. The procedure is local to this device. Network-side changes (firmware updates that affect TLS, SMB, or routing) are flagged explicitly in the steps.

What if the fix returns after a reboot?

Persistent fault returns mean either: a hardware fault (escalate), a configuration that's being overwritten by a sync source (check cloud profiles), or a regression in a recent firmware update (rollback).

How often should I run preventive checks?

Quarterly for most consumer devices; monthly for production / commercial devices. Set a calendar reminder so the device stays healthy between issues.

Field notes from real incidents on Deployment Automation

When I work on Cisco switch fleet: How to generate a compliance report the rhythm I lean on is the one I have built over years of these tickets. The newer Cisco IOS-XE traceability tools (show platform hardware fed) are massively underused; they answer questions the old CLI cannot. I never run a software upgrade on a live Catalyst stack without an out-of-band console session; the in-band session drops at the worst possible moment. Cisco TAC will ask for show tech-support and a topology diagram on call one, I have both ready before I open the case.

Tools I actually reach for

For Cisco switch fleet: How to generate a compliance report on Deployment Automation the cheapest signal I can land usually comes from a known order of operations, not a kitchen-sink approach. I start with traceroute vrf <vrf> <target> because it is the lowest-friction way to confirm the failure is real and reproducible. If that returns ambiguous data, I escalate to show tech-support (capture for TAC), show logging last 200, packet capture on the ingress interface (TAC will ask for it), show interfaces counters errors, and finally to ping vrf <vrf> <target> only when the cheaper tools cannot reach the layer the failure lives in. That ordering matches the failure surfaces I have actually seen on Deployment Automation units over the last few years, not an abstract taxonomy. The cheap signals gate the expensive ones so the investigation does not balloon into a multi-hour exercise.

Verification I run before I close the ticket

Before I mark Cisco switch fleet: How to generate a compliance report resolved on a Deployment Automation unit, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheap checks gate the more expensive ones so I never burn an hour on a deep test that a shallow one would have failed in seconds.

show spanning-tree summary  # confirm topology stability

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

show ip route <prefix>  # confirm best path post-change

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

show interfaces <int> | include errors|drops|CRC

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

show logging | include %LINK|%LINEPROTO|%BGP|%OSPF

Only when every line above runs clean do I close the ticket and update the runbook with the timestamps. A green verification that nobody can reproduce is not a fix, it is luck waiting to regress.

Where I check first when the docs disagree

When two sources contradict each other on a Deployment Automation detail, the disambiguation order I lean on is stable across products and across years. Cisco TAC case knowledge base is where I start for the ground-truth view. cisco.com/c/en/us/td/docs/ios-xml for IOS XR is where I start for the ground-truth view. cisco.com/c/en/us/support. official command references is where I start for the ground-truth view. Random blog posts and reseller wikis are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim. The cost of trusting an unauthoritative source on Cisco switch fleet: How to generate a compliance report is rarely worth the time it saved.

Pitfalls I have walked into on this exact path

The shortcuts that look smart on Cisco switch fleet: How to generate a compliance report have a habit of biting back. The pitfalls below are the ones I have personally walked into on a Deployment Automation unit, not things I read about. Most catalyst stack issues I have triaged were power-budget related, not software, the show power detail output answers it in 5 seconds. Cisco bug search tool is the cheapest sanity check before a config change: search the symptom, sort by affected releases, decide. I never run a software upgrade on a live Catalyst stack without an out-of-band console session; the in-band session drops at the worst possible moment. When in doubt I revert to the slower path that the manual prescribes - the time I save by skipping it is always smaller than the time I spend cleaning up afterwards.

What I tell the next on-call

When I hand Cisco switch fleet: How to generate a compliance report off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature on Deployment Automation - not a paraphrase, the exact string that surfaces in logs or on the screen. Second, the diagnostic that gave the highest signal in the least time. Third, the exact verification command whose green output justified closing the ticket. That trio is what turns a one-off fix into a runbook entry the next engineer can use without paging me at three in the morning.

I also add a one-line note on the cost of getting this wrong. For Cisco switch fleet: How to generate a compliance report on a Deployment Automation unit, the cost is rarely the replacement part or the patch itself. It is the downtime, the second site visit, and the trust deficit you spend with whoever owns the asset when the fix does not hold. That framing keeps the next on-call from choosing the cheap-looking shortcut that ends up costing the most in elapsed hours and goodwill.

Related fixes

Related guides worth a look while you sort this one out:

• Cisco AP fleet: How to generate a compliance report
• Cisco router fleet: How to generate a compliance report
• Cisco switch fleet: How to back up configs nightly to a Git repo
• Cisco switch fleet: How to deploy with Ansible (cisco.ios collection)
• Cisco switch fleet: How to deploy with Cisco DNA Center / Catalyst Center
• Cisco switch fleet: How to deploy with NETCONF + YANG