42U rack elevation
One rack with ToR switches, a firewall, a management switch, DB and app servers, storage and a UPS — each placed at its U position.
Open this example in the editor →
A rack is a group with a height (42U), and every device inside can carry the U slots it occupies. Select the rack and the side panel shows a front view with free and overlapping slots; new devices are dropped into the lowest free U automatically.
Server cards pin their IP attribute underneath, so the rack elevation and the IP list stay in one place. Turn on "Hide IPs" when exporting and only the addresses are masked in the picture you send out. If your asset register lives in Excel, save it as CSV and bring it in with File ▾ › Import CSV.
What's on each layer
- L1 · Rack equipment — Rack B-03 · 42U, ToR switch A (25G · 48 ports), ToR switch B (25G · 48 ports), Firewall (1U), Management switch (iDRAC·IPMI), DB-01 (2U), DB-02 (2U), APP-01 (1U), APP-02 (1U), Storage (4U · 60TB), Rack UPS (3U · 3kVA), Core switch (end of row B)
- L0 · Server room — Server room, row B, Cold aisle
Flow scenario
App → DB request path
- APP-01 → ToR switch A — APP-01 sends a DB query
- ToR switch A → DB-01 — ToR in the same rack forwards to DB-01
- DB-01 → Storage — Reads data blocks
Good for
- Documenting a server room walk-through
- Checking free U and power before new hardware arrives
- Reconciling the asset register (CSV) with what's actually racked
Open this example in the editor →
More examples
- Three-tier web service diagramThe classic split — web servers in the DMZ, application and database servers inside — drawn as an equipment layer with the services stacked on top.
- Disaster recovery (DR) pair diagramA primary site and a DR site side by side, with storage replication, database log shipping and the GSLB failover on one canvas.
- Network separation diagramA business network and an internet network kept apart: the internet only through VDI, files only through a cross-domain transfer server.