Network and IP Planning · #09
Online Static Route Inventory Diff
Compares two route lists from before and after a change using VRF + prefix as the key; keeps each ECMP path.
- Data is processed in your browser and not sent to a server
- Export: CSV
Tool
What does this tool do?
Comparing route lists taken before and after a router or firewall change line by line is misleading because of ordering and ECMP: the same two next hops in a different order look 'changed'. The tool compares the next-hop set per VRF + prefix, ignores order and separates new, removed and changed routes.
How to use it
- Paste both lists as CSV with a header row. Required columns:
prefixandnext_hop; optionalvrfandmetric. Comma, semicolon or tab separators work. - Common column names such as
network,destination,gateway,nexthopare recognised. - Press Calculate and download the differences as CSV.
Fields
- List A (before)
- CSV with header: vrf,prefix,next_hop,metric
- List B (after)
- Second list in the same format
Worked example
| Input | Value |
|---|---|
| List A (before) | |
| List B (after) | |
Expected result: 1 changed (10.50.0.0/16 next hop 10.0.0.2 → 10.0.0.6), 1 ECMP change (10.0.0.4 removed from 10.60.0.0/16), 1 added (172.16.0.0/12), 2 unchanged.
10.60.0.0/16 had two equal-cost paths in A and only one in B: a change that halves capacity and is easy to miss in a line-by-line comparison. The mgmt VRF route is unchanged.
Method and assumptions
Each prefix is reduced to its network address; the key is VRF | prefix ('default' if no VRF). The value of a key is the set of next_hop [metric] pairs, so each ECMP path is kept and order does not matter.
Keys only in A are removed, only in B are added, and different sets are changed. Changes involving more than one path are flagged as 'ECMP change'.
Using the result and troubleshooting
After capturing list B in the change window, review unexpected 'removed' or 'changed' rows against your rollback plan.
If interface names are used as next hops (e.g. Null0), write them the same way in both lists; comparison is case-insensitive.
Limits and common mistakes
- Administrative distance, tags and tracking are not compared.
- It does not distinguish routes learned from dynamic protocols; it compares the lists you enter.
- Up to 20,000 lines.
Frequently asked questions
Is the metric column required?
No. If present it is compared together with the next hop; a route whose metric alone changed appears as 'changed'.
Related tools and service
- Subnet Overlap CheckerLists overlaps within the same VRF and deliberate reuse across VRFs separately.
Related service: Network Performance Analysis and Troubleshooting