sjat/MakerFLOSS_Troubleshooting
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

network-map: srv07 uplink recorded (pp02:8 -> sw06:4), close open question

Browse source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
sjat 2026-07-17 17:29:16 +02:00
parent 2194a26970
commit 1fc6a66195
2 changed files with 2 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
incidents/2026-07-17-srv07-access.md
View file

@ -51,7 +51,8 @@ Two physical-layer facts, no software fault:
## Follow-ups ## 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`. - Identify the rack-LAN Debian trio `.10/.11/.12` and `.158/.165/.209`.
- Find/verify makerfloss1 (LAN and wg1 both dark). - Find/verify makerfloss1 (LAN and wg1 both dark).
- Ansible play against srv07 not yet re-run — first run after the rename - Ansible play against srv07 not yet re-run — first run after the rename

3
network-map.md
View file

@ -18,9 +18,6 @@ live probing (mamba wired on the rack LAN + the wg1 hub + mf01).
## Open questions (check when on-site) ## 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 - **makerfloss1:** where is it, and is it still alive? Neither its LAN IP nor
its wg1 peer answered. its wg1 peer answered.
- **The `.10/.11/.12` trio and `.158/.165/.209`:** identify and label - **The `.10/.11/.12` trio and `.158/.165/.209`:** identify and label