Infrastructure and network
Infrastructure diagrams are used under pressure, usually by someone who did not draw them. That single fact should drive every choice: real names, real addresses, a date, and a link to the runbook.
Where the layout can be generated from text, generate it. It is the only way these stay current.
#In this section
Network diagram
From one office to many sites.
Network topology diagram
Star, mesh, bus, ring, and hybrids.
Subnet and VLAN diagram
Addresses that stay readable as they multiply.
Rack diagram
Elevations that match what is in the room.
Data center diagram
Floor, rows, racks, and power.
Packet and protocol headers
Bit offsets, drawn properly.
P&ID diagram
Piping and instrumentation, with the right symbols.
#Everything under here
Network diagramDraw a network diagram in Confluence, from a small office LAN to a multi site topology.Network topology diagramDiagram star, mesh, bus, ring and hybrid topologies and pick the notation that suits each one.Subnet and VLAN diagramDocument subnets, VLANs and IP allocation with a network diagram that stays readable as it grows.Rack diagramDraw a server rack elevation with units, depth and equipment labels, next to the runbook.Data center diagramLay out a data center floor, rows, racks and power, and link each rack to its own elevation.Packet and protocol headersDraw a protocol header with bit offsets and field widths for TCP, custom protocols or binary formats.P&ID diagramDraw a piping and instrumentation diagram in Confluence with the shipped valve and instrument shapes.
Somebody will read this at 3am. Be kind.
