Subnet Plan Diff

The Subnet Plan Diff tool compares two versions of an IP address plan and identifies exactly what changed: subnets added, subnets removed, and subnets modified. Paste your old plan and new plan side by side -- for example, last month's IPAM export versus this month's -- and get a color-coded diff report with summary statistics showing additions, deletions, and attribute modifications across every entry.

Understanding Network Address Plan Versioning

Network address plans are living documents. They change every time a new VLAN is provisioned, a branch office is deployed, a subnet is resized, or an old allocation is decommissioned. In small networks, these changes might happen once a month. In large enterprises with hundreds of sites, the plan can change multiple times per week. Without a reliable way to track those changes, you lose visibility into what your network looks like today versus what it looked like last quarter, and you cannot answer basic audit questions like "what changed, when, and who approved it."

Most organizations keep their address plans in spreadsheets or IPAM systems, but neither of those tools makes it easy to see a clean diff between two points in time. Spreadsheets have no built-in version comparison. IPAM systems often have change logs, but they track individual field edits rather than presenting a holistic before-and-after view. This tool fills that gap. You take two snapshots of your plan -- at any two points in time, from any source -- and get a clear report showing every difference between them.

The practical value is enormous for regulated environments. PCI-DSS, SOX, HIPAA, and similar frameworks require documentation of network changes as part of their compliance controls. A diff report attached to a change ticket shows the auditor exactly what was proposed, what was implemented, and whether they match. It also catches unauthorized changes: if someone added a subnet outside the change management process, the next periodic diff will surface it immediately.

How to Compare Two Subnet Plans

1. Paste the old version of your subnet plan into the first input (CSV, table, or structured text)
2. Paste the new version into the second input
3. Click Compare to generate the diff report
4. Review the color-coded results showing additions, deletions, and modifications between the two versions

Subnet Plan Diff Output Examples

Added and Removed Subnets

+ 10.1.5.0/24    New York Office Wi-Fi     VLAN 50
+ 10.1.6.0/24    New York Office Servers    VLAN 60
- 192.168.5.0/24  Legacy Lab Network        VLAN 105
- 192.168.6.0/24  Old Dev Environment       VLAN 106

Modified Subnets

Summary Statistics

Plan A: 48 subnets
Plan B: 50 subnets
──────────────────
Added:    4 subnets
Removed:  2 subnets
Modified: 3 subnets
Unchanged: 44 subnets

When to Use the Subnet Plan Diff Tool

• Change advisory board presentations -- clearly show stakeholders exactly what is being proposed, with a line-by-line breakdown of additions, removals, and modifications
• Compliance and audit documentation -- generate reports that demonstrate what changed in the network addressing plan, when, and by whom, satisfying SOX, PCI-DSS, or HIPAA change documentation requirements
• Post-implementation validation -- compare the approved plan against the actually-implemented configuration to confirm they match
• Network migration tracking -- during multi-phase migrations, track which subnets have been moved, resized, or decommissioned at each stage
• IPAM version control -- compare periodic exports from your IPAM system to detect unauthorized or undocumented changes to the address plan
• Rollback planning -- before implementing a large change, save the current plan as a baseline so you can generate a diff to verify what needs to be reversed if a rollback is required

How Subnet Plan Comparison Works

The diff algorithm normalizes both inputs before comparison to ensure accurate matching:

Normalization Steps

1. CIDR canonicalization -- 10.1.1.5/24 is normalized to 10.1.1.0/24 so the same logical subnet matches regardless of which host address was used
2. Whitespace and formatting cleanup -- extra spaces, inconsistent delimiters, and blank lines are stripped
3. Column alignment -- the tool maps columns from both inputs to identify which fields correspond to network, mask, description, VLAN, and other attributes

Change Classification

• Added -- subnets present in the new plan but absent from the old plan
• Removed -- subnets present in the old plan but absent from the new plan
• Modified -- subnets present in both plans but with changed attributes (description, VLAN, prefix length, or other metadata)
• Unchanged -- identical entries in both plans, included in the report for completeness

Practical Advice for Address Plan Version Control

The most effective approach to address plan management is to treat it like source code. Export your IPAM data on a regular schedule -- weekly or monthly, depending on how frequently your network changes -- and store each export with a date stamp. When you need to understand what changed over a specific period, pull the two exports from the relevant dates and run them through this tool. Over time, you build a complete change history that no audit can question.

When reviewing a diff report, pay extra attention to modifications that change the prefix length of an existing subnet. A description update is low-risk metadata. A VLAN reassignment affects switch configurations. But a prefix length change -- say, expanding a /24 to a /23 -- doubles the subnet's address range and may overlap with the adjacent block. Always run a prefix-length modification through the Change Impact Report to verify that the expansion does not create conflicts with neighboring allocations.

Be wary of diffs that show a large number of simultaneous removals and additions. This pattern sometimes indicates a bulk re-addressing project, which is expected and fine. But it can also indicate that someone reimported or overwrote the address plan with stale data, wiping out recent changes. If the diff looks unexpectedly dramatic, compare the new plan against a third snapshot from a different date to determine whether the changes are legitimate or the result of a data handling error.

Frequently Asked Questions

What input formats does the diff tool accept?

The tool accepts CSV, tab-separated values, and structured text with consistent delimiters. Common sources include IPAM exports (NetBox, phpIPAM, Infoblox), spreadsheet pastes, and router configuration extracts. Both inputs must use a compatible format so columns can be mapped.

Can I compare plans with different column layouts?

Yes. The tool identifies network address columns automatically and lets you map additional columns between the two inputs. If one plan has a VLAN column that the other lacks, that column is treated as added or removed metadata rather than causing a mismatch error.

How does the tool handle subnet resizing?

When a subnet changes prefix length (e.g., /24 to /23), it appears as a modification to the existing entry showing the old and new prefix values. If the network address also changes, it may appear as a removal of the old subnet and addition of the new one, since the tool cannot automatically determine that they represent the same logical network.

Can I use this tool to compare router configurations?

The tool is designed for structured address plan data, not raw router configurations. However, if you extract the subnet information from your router configs into a CSV or table format, you can compare those extracts. Tools like show ip route output can be reformatted for comparison.

What should I do if the diff shows unexpected changes?

Investigate whether the changes were authorized through your change management process. Check change tickets for the relevant period to see if the modifications were planned. If no ticket exists, the change may be unauthorized -- escalate to your network security team and consider reverting to the previous version of the plan.

Related Tools

• Change Impact Report - See what overlaps if a new subnet is added
• Duplicate Subnet Detector - Find duplicate subnets in an IP plan
• IPAM Import Formatter - Format data for IPAM system imports
• VLSM Report Generator - Generate printable VLSM allocation reports
• Address Plan Generator - Generate an IP address plan CSV template
• Overallocated Subnet Detector - Detect when required hosts exceed usable capacity