The network as actually built and verified: management lives on VLAN 100 · 192.168.100.0/24. Solid green lines are untagged access ports on SW-CORE-01; dashed blue lines are 802.1Q trunks — including the two new Phase 7 guest trunks (Gi1/0/4 and Gi1/0/5) down to each Proxmox host's second NIC. Device pictograms follow Cisco's standard network topology icon style. No VM has moved off the flat management network yet — see the proposed migration table below, which is a plan, not a completed change.
Hover any device to peek at its details — click to pin the card in place, click empty space or the ✕ to dismiss it.
Legend: gold = core switches · blue = access switches · green = hosts · grey dashed = not yet integrated. Trunks carry VLANs 100, 110, 120, 130, 210, 220.
| From | Port | To | Type |
|---|---|---|---|
| SW-CORE-01 | Gi1/0/1 | Rocky OptiPlex (.30) | Access · VLAN 100 |
| SW-CORE-01 | Gi1/0/2 | PVE01 (.10) | Access · VLAN 100 |
| SW-CORE-01 | Gi1/0/3 | PVE02 (.13) | Access · VLAN 100 |
| SW-CORE-01 | Gi1/0/4 | PVE02 nic1 → vmbr1 | Trunk · VLANs 120, 130 only · guest only, no VLAN 100 |
| SW-CORE-01 | Gi1/0/5 | PVE01 nic1 → vmbr1 | Trunk · VLANs 110, 130 only · guest only, no VLAN 100 |
| SW-CORE-01 | Gi1/0/47 ↔ Gi1/0/24 | SW-ACCESS-01 (.4) | Trunk |
| SW-CORE-01 | Gi1/0/48 ↔ Gi2/0/48 | SW-CORE-02 (.3) | Trunk · VLANs 100,110,120,130,210,220 |
| SW-CORE-02 | Gi2/0/47 ↔ Gi0/2 | SW-ACCESS-02 (.5) | Trunk |
Inter-switch port pairs are shown as documented in the Phase 5 topology file; if you re-cable anything, tell Muse and this page gets updated.
switchport nonegotiate, STP forwarding verified for both VLANsswitchport nonegotiate, STP forwarding verifiedcopy running-config startup-config on CORE-01, and both Proxmox hosts now show a VLAN-aware vmbr1 on nic1 (Active, no host IP, no gateway) alongside the untouched nic0 / vmbr0 management linkvmbr1 shows Proxmox's broad default bridge-vids 2-4094 — that is not the switch allowlist. The switch is what actually limits each trunk to its two VLANsshow interfaces status shows a PVE02 description on both Gi1/0/2 and Gi1/0/3. The physical map (Gi1/0/2 = PVE01, Gi1/0/3 = PVE02) is authoritative until the descriptions are auditedip routing is not enabled on CORE-01 — only Vlan100 (.2) is up. Nothing routes between VLANs todayvmbr0 — no VM has been migratedshow running-config | include ^ip default-gateway — before any routing change, so the management impact can be assessed| Host | VM | Current IP (.100) | Proposed VLAN | Proposed IP |
|---|---|---|---|---|
| PVE01 (Student 1) | 100 rocky-server01 | .11 | 110 | 192.168.110.11 |
| PVE01 (Student 1) | 101 rocky-server02 | .12 | 110 | 192.168.110.12 |
| PVE01 (Student 1) | 102 ubuntu-server01 | .20 | 130 | 192.168.130.20 |
| PVE02 (Student 2) | 200 rocky-server02 | .21 | 120 | 192.168.120.21 |
| PVE02 (Student 2) | 201 rocky-serverb02 | .22 | 120 | 192.168.120.22 |
| PVE02 (Student 2) | 202 ubuntu-services02 | .23 | 130 | 192.168.130.23 |
Ownership follows the host: PVE01 belongs to Student 1, PVE02 to Student 2, and both Ubuntu VMs are slated for shared VLAN 130. Migration happens one VM at a time, only after the gateway, VLAN, ACL, and rollback plan are sound — never all at once.