From 1fc6a661957f75a69ba9e5a1774835d74a24558b Mon Sep 17 00:00:00 2001 From: sjat Date: Fri, 17 Jul 2026 17:29:16 +0200 Subject: [PATCH] network-map: srv07 uplink recorded (pp02:8 -> sw06:4), close open question Co-Authored-By: Claude Fable 5 --- incidents/2026-07-17-srv07-access.md | 3 ++- network-map.md | 3 --- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/incidents/2026-07-17-srv07-access.md b/incidents/2026-07-17-srv07-access.md index 07bae93..4aa87bd 100644 --- a/incidents/2026-07-17-srv07-access.md +++ b/incidents/2026-07-17-srv07-access.md @@ -51,7 +51,8 @@ Two physical-layer facts, no software fault: ## Follow-ups -- Record srv07's actual rear patch / switch port (pp02.md + sw01.md). +- ~~Record srv07's actual rear patch / switch port~~ — done same day: + pp02:8 → sw06:4 (srv07's single NIC; MakerFLOSS docs `cfaf065`). - Identify the rack-LAN Debian trio `.10/.11/.12` and `.158/.165/.209`. - Find/verify makerfloss1 (LAN and wg1 both dark). - Ansible play against srv07 not yet re-run — first run after the rename diff --git a/network-map.md b/network-map.md index aedff8c..f34e003 100644 --- a/network-map.md +++ b/network-map.md @@ -18,9 +18,6 @@ live probing (mamba wired on the rack LAN + the wg1 hub + mf01). ## Open questions (check when on-site) -- **srv07's physical uplink:** connectivity restored 2026-07-17, but the new - rear patch of pp02:8 (or a direct cable?) is unrecorded — see the note in - `MakerFLOSS/docs/hardware/pp02.md`. Record switch + port. - **makerfloss1:** where is it, and is it still alive? Neither its LAN IP nor its wg1 peer answered. - **The `.10/.11/.12` trio and `.158/.165/.209`:** identify and label