Operations / configuration planning

Compare illustrative configuration revisions

Explore what changed between two fictional, deliberately simplified network-design snapshots. No controller, device or customer configuration is connected, uploaded, stored or observed. This is a teaching example, not a compliance verdict or change audit.

Before and after are invented examples. There are no device IPs, secrets, command-line configurations or real timestamps. Every field is an illustrative assumption, not a verified observation. “Unknown” is different from zero and never proves a feature is disabled. Any action suggestions require operator verification.

Choose a demo scenario

One fictional site at a time. Start with changes only, or reveal all fields in expert mode.

Illustrative site

Display

5 changed fields · 5 visible · source: synthetic demo · not measured

Download or copy full example comparison

Downloads always include all five allowlisted fields, including unchanged values, with a synthetic/not-measured label. They contain no device configuration, credentials or real network identifiers. No PDF until pdfcn is verified.

Demo Branch A: before vs after

Example revisions, not calendar dates or observed change history

Before

Example revision A

After

Example revision B

WAN arrangement

changed · demo

Before: single
After: failover

Configured VLAN count

changed · demo

Before: 2
After: 3

Guest network enabled

changed · demo

Before: Disabled
After: Enabled

Illustrative PoE headroom (W)

changed · demo

Before: 70 W
After: 45 W

Uplink redundancy

changed · demo

Before: none
After: dual-uplink

Compare the concept with Nautobot structured configuration compliance and Oxidized revision backups. Those tools work with actual authorized configurations; this page intentionally does not. Future real integrations require owner authorization, scoped backend access, TLS validation, secret redaction and independent security review.