Network Documentation with Dia: A Sysadmin Guide
Dia Diagram Editor is a free, open-source project by the GNOME community. This site is an independent community resource — we are not affiliated with the GNOME Dia project.
Every sysadmin inherits a network held together by tribal knowledge. Dia — free, offline, tiny files — is an excellent tool for turning that knowledge into real documentation. This guide gives you a complete method: topology + rack + subnet records + versioning, using our network diagram tutorial and rack diagram tutorial as building blocks.
The three-document system
1. Topology map (topology.dia)
One page per site. Routers, switches, firewalls, servers, WAN links — with every link labeled (interface names, VLANs, speeds). Use the Cisco-style shapes. Label everything; an unlabeled line on a network map is technical debt.
2. Rack elevations (rack-row-a.dia)
One diagram per rack, built with the server-rack shape pack. Each unit labeled: hostname, role, and both power feeds. Include the patch panels — future-you tracing a cable will be grateful.
3. Subnet/IP register
Dia isn’t a spreadsheet — keep the IP register as a table inside the topology diagram (a simple table object on an annotations layer): subnet, gateway, VLAN, purpose, one row per network. One glance, whole addressing scheme.
Conventions that save you later
- Naming:
sitecode-role-numberhostnames everywhere (e.g.nyc-sw-02), identical in Dia, DNS, and monitoring. - Colors: one color per VLAN/security zone, with a legend box on every diagram. Never rely on color alone — label too.
- Dates: put “Last verified: YYYY-MM-DD” in a corner of every diagram. A map without a date is a rumor.
- Change log: a text box listing the last few changes (“2026-09: added nyc-sw-03”). Five lines, enormous value.
Versioning .dia files
.dia files are gzipped XML — small and git-friendly. Keep the docs in a git repo: every change gets a commit message (“add uplink to nyc-rtr-02”). You get history, blame, and backups for free. Rule: update the diagram in the same change window as the network change. Documentation updated “later” is documentation never updated.
Sharing with non-Dia users
Export PDF for the team wiki and printed binder copies; keep the .dia as the source of truth. See our export guide for print-ready settings.
FAQ
Is Dia enough for professional network documentation?
For small-to-medium networks, absolutely — topology + rack + IP register covers what most teams need. Enterprises with automated discovery (NetBox, etc.) outgrow it, but Dia remains great for the human-readable layer.
How do I keep diagrams from going stale?
The “last verified” date plus updating in the change window (above). Assign one owner per site’s docs.
Can I link diagrams together?
Keep one index diagram (site map) with the filenames of the detailed diagrams noted on it. Dia has no hyperlinking between files worth relying on — the index convention works fine.
What about wireless/AP layouts?
Same method: floor-plan outline on a locked background layer, APs placed to scale, channels labeled. See the layers guide for the technique.