MakerFLOSS/docs/hardware/pp02.md
sjat f047332e94
All checks were successful
Build docs site / build (push) Successful in 53s
Build slides / build (push) Successful in 1m11s
docs(hardware): record srv07 real specs and identity, correct mf04 mapping
srv07 verified on-site 2026-07-17: it is the Ansible/OS host mf04
(i3-4360T 2c/4t, 16 GB, 500 GB HDD, Debian 13), renamed to srv07 to match
the sticker. The naming-scheme migration row said mf04 -> srv05 — corrected
with a dated note. pp02: srv07's LAN path was restored 2026-07-17; the new
rear patch of port 8 is ad hoc and still needs recording.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-17 17:20:41 +02:00

1.1 KiB
Raw Blame History

hostname kind status rack rack_u u_height rack_face ports links
pp02 patch-panel in-use rack01 25 1 front 24
local peer peer_port
1 pp01 1
local peer peer_port
2 sw01 1
local peer peer_port
3 sw01 2
local peer peer_port
4 sw01 3
local peer peer_port
5 sw01 4
local peer peer_port
6 sw01 5
local peer peer_port
7 sw01 6

Notes

  • 24-port patch panel; ports 1–7 are the live LAN feeds.
  • Port 1 → pp01:1 → wan01 (srv01 eth0, WAN).
  • Ports 2–7 → sw01:1–6 (LAN): srv01 eth1 (p2), srv02 (p3), srv03 (p4), srv04 (p5), srv05 (p6), srv06 (p7).
  • Port 8 carries srv07 eth0. Its rear patch to sw01:7 was removed when sw01:7 was repurposed as the uplink to sw06, leaving srv07 with no LAN path for a while. Connectivity was restored on 2026-07-17 (srv07 is back on the LAN at 10.0.0.x and its wg1 tunnel is up) — but the new rear patching was done ad hoc and is not yet recorded: confirm on-site which switch/port port 8 now lands on and update this list.