sjat/MakerFLOSS
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
MakerFLOSS/docs/hardware/srv07.md
sjat cfaf06510b
All checks were successful
Build docs site / build (push) Successful in 49s
Details
Build slides / build (push) Successful in 1m8s
Details
docs(hardware): record srv07 rear patch pp02:8 -> sw06:4 
Confirmed on-site 2026-07-17: srv07's single NIC runs eth0 -> pp02:8,
rear-patched to sw06:4 — the patch that restored its LAN path.

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

1.3 KiB
Raw Blame History

hostname kind status cluster location cpu cpu_cores cpu_threads ram_gb storage_gb storage_type nic_gbps rack mounted_on shelf_face shelf_slot chassis_u power links
srv07 server staging tappaas The pile Intel Core i3-4360T @ 3.20GHz 2 4 16 500 hdd 1 rack01 shf02 front 1 6
pdu outlet
pdu01 1
pdu outlet
pdu02 1
local peer peer_port speed_gbps
eth0 pp02 8 1

Notes

  • Specs read live 2026-07-17 (lscpu/free/lsblk): i3-4360T (2c/4t), 16 GB RAM, 500 GB HDD (Seagate ST3500418AS). Runs Debian 13 (trixie).
  • This is the machine Ansible (AnsibleBaobabV4) managed as mf04; the OS hostname was renamed mf04 → srv07 on 2026-07-17 to match the sticker. The naming-scheme guide's migration row originally said mf04 → srv05; that was a mis-mapping (srv05's page describes an i5-3570K box).
  • SSH on :7576 (project standard), user sjat. WireGuard split-tunnel to the makerfloss VPS (wg1 peer 10.13.0.3, unit wg-quick@mf-srv07) dials out automatically on boot.
  • Single NIC (eth0 → pp02:8). LAN path restored 2026-07-17 via a rear patch pp02:8 → sw06:4 (DHCP lease 10.0.0.183); the original pp02:8 → sw01:7 patch had been removed when sw01:7 became the sw06 uplink, which left the box with no LAN path for a while.