From 8aa89c5062ca32ca4ebbb99337f37554ae3c310c Mon Sep 17 00:00:00 2001 From: Joshua Gilman Date: Fri, 14 Aug 2026 17:35:40 -0700 Subject: [PATCH] docs: add physical connection map --- .../designs/drafts/lab-v2-core-network.md | 2 + docs/docs/index.md | 6 ++- docs/docs/reference/hardware.md | 17 +++---- docs/docs/reference/physical-connections.md | 45 +++++++++++++++++++ docs/mkdocs.yml | 1 + 5 files changed, 57 insertions(+), 14 deletions(-) create mode 100644 docs/docs/reference/physical-connections.md diff --git a/docs/docs/designs/drafts/lab-v2-core-network.md b/docs/docs/designs/drafts/lab-v2-core-network.md index 0d1fac0..6622b3b 100644 --- a/docs/docs/designs/drafts/lab-v2-core-network.md +++ b/docs/docs/designs/drafts/lab-v2-core-network.md @@ -64,6 +64,8 @@ interface. VyOS routes lab prefixes, applies firewall policy, and performs source NAT for internet egress. The CRS309-1G-8S+IN carries lab VLANs between VyOS and connected lab devices. The TEG-3102WS connects directly to the VP6630 and carries management/OOB traffic for both non-SFP NICs on each MS-02. +The [physical connection map](../../reference/physical-connections.md) is the +authoritative port-to-port cabling record. ## Device Responsibilities diff --git a/docs/docs/index.md b/docs/docs/index.md index cb590f1..33ba2db 100644 --- a/docs/docs/index.md +++ b/docs/docs/index.md @@ -17,8 +17,10 @@ VLAN transport. A TRENDnet TEG-3102WS handles MS-02 management/OOB switching. verification criteria. - [ADR-0001: Use VyOS for Layer 3 and Dedicated Switches for Layer 2](decisions/0001-use-vyos-for-layer-3-and-switches-for-layer-2.md) assigns routing and switching responsibilities. -- [Hardware](reference/hardware.md) identifies the core network devices, - connections, and roles. +- [Hardware](reference/hardware.md) identifies the core network devices and + their roles. +- [Physical connections](reference/physical-connections.md) records every + installed cable and its endpoint ports. Compute platforms, workload networking, and application delivery are outside the core network documentation. diff --git a/docs/docs/reference/hardware.md b/docs/docs/reference/hardware.md index f2b6dab..87a096b 100644 --- a/docs/docs/reference/hardware.md +++ b/docs/docs/reference/hardware.md @@ -1,6 +1,6 @@ --- title: Hardware -description: Core network devices, connections, and assigned roles. +description: Core network devices and their assigned roles. --- # Hardware @@ -19,14 +19,7 @@ description: Core network devices, connections, and assigned roles. | --- | --- | --- | | Home router | MikroTik CCR2004 | Routes the home network, provides internet access, and terminates the upstream side of the routed lab transit | -## Connections - -| Endpoints | Connection | -| --- | --- | -| CCR2004 to VP6630 | Routed lab transit | -| VP6630 to CRS309-1G-8S+IN | 802.1Q trunk for lab VLANs | -| VP6630 to TEG-3102WS | Direct management/OOB uplink | -| TEG-3102WS to each MS-02 | Two non-SFP NICs carrying management/OOB traffic | - -See the [Lab v2 core network design](../designs/drafts/lab-v2-core-network.md) -for the topology and device boundaries. +The [physical connection map](physical-connections.md) records every installed +cable and its endpoint ports. The +[Lab v2 core network design](../designs/drafts/lab-v2-core-network.md) defines +the logical topology and device boundaries. diff --git a/docs/docs/reference/physical-connections.md b/docs/docs/reference/physical-connections.md new file mode 100644 index 0000000..4be458b --- /dev/null +++ b/docs/docs/reference/physical-connections.md @@ -0,0 +1,45 @@ +--- +title: Physical Connections +description: Authoritative port-to-port map of the installed network cabling. +--- + +# Physical Connections + +Each row records one installed cable. Port names match the labels on the device +chassis. `Unlabeled Ethernet port` identifies a physical Ethernet port that has +no printed label. + +## Connected ports + +| Connection | Device A | Port A | Device B | Port B | +| --- | --- | --- | --- | --- | +| `PHY-001` | MikroTik CCR2004 | `SFP+ 1` | Minisforum VP6630 | `SFP+ 1` | +| `PHY-002` | Minisforum VP6630 | `SFP+ 2` | MikroTik CRS309-1G-8S+IN | `Port 8` | +| `PHY-003` | Minisforum VP6630 | `Port 2` | TRENDnet TEG-3102WS | `Port 1` | +| `PHY-004` | Minisforum VP6630 | `Port 3` | PiKVM | `Unlabeled Ethernet port` | +| `PHY-005` | Minisforum VP6630 | `Port 4` | TESmart 8x1 KVM | `Unlabeled Ethernet port` | +| `PHY-006` | TRENDnet TEG-3102WS | `Port 2` | LAB01 | `Top Port` | +| `PHY-007` | TRENDnet TEG-3102WS | `Port 3` | LAB01 | `Bottom Port` | +| `PHY-008` | TRENDnet TEG-3102WS | `Port 4` | LAB02 | `Top Port` | +| `PHY-009` | TRENDnet TEG-3102WS | `Port 5` | LAB02 | `Bottom Port` | +| `PHY-010` | TRENDnet TEG-3102WS | `Port 6` | LAB03 | `Top Port` | +| `PHY-011` | TRENDnet TEG-3102WS | `Port 7` | LAB03 | `Bottom Port` | +| `PHY-012` | MikroTik CRS309-1G-8S+IN | `Port 1` | LAB01 | `Right SFP 25G` | +| `PHY-013` | MikroTik CRS309-1G-8S+IN | `Port 2` | LAB01 | `Left SFP 25G` | +| `PHY-014` | MikroTik CRS309-1G-8S+IN | `Port 3` | LAB02 | `Right SFP 25G` | +| `PHY-015` | MikroTik CRS309-1G-8S+IN | `Port 4` | LAB02 | `Left SFP 25G` | +| `PHY-016` | MikroTik CRS309-1G-8S+IN | `Port 5` | LAB03 | `Right SFP 25G` | +| `PHY-017` | MikroTik CRS309-1G-8S+IN | `Port 6` | LAB03 | `Left SFP 25G` | +| `PHY-018` | MikroTik CRS309-1G-8S+IN | `Port 7` | NAS | `10GB Port` | + +## Unconnected ports + +Only ports explicitly identified as unconnected are listed. + +| Device | Port | +| --- | --- | +| Minisforum VP6630 | `Port 1` | +| TRENDnet TEG-3102WS | `Port 8` | + +IP addresses, VLANs, bonds, interface names, and link settings belong to the +network configuration rather than this physical map. diff --git a/docs/mkdocs.yml b/docs/mkdocs.yml index 2f1f869..ba0f9aa 100644 --- a/docs/mkdocs.yml +++ b/docs/mkdocs.yml @@ -38,6 +38,7 @@ nav: - Lab v2 core network: designs/drafts/lab-v2-core-network.md - Reference: - Hardware: reference/hardware.md + - Physical connections: reference/physical-connections.md plugins: - search