Skip to content

Topology & Sites

The network follows a layered Edge → Core → Metro → Venue model, plus the server room and a Starlink backup WAN. Today the shape is largely a star on the colo with tactical 60 GHz backups; the target adds two links to form two protected rings so every hub has at least two independent paths to the colo.

graph TB
    INET((Internet)) --- FW[OPNsense edge pair]
    STAR([Starlink]) --- COLO
    FW --- COLO{{Colo core<br/>CR-COLO-01/02}}
    COLO --- MAT[Mathew St]
    COLO --- CHA[Charlotte St]
    COLO --- SEE[Seel St]
    COLO --- HOL[Holmes]
    COLO -. roof .- CROOF[Colo roof]
    CROOF -. 60GHz .- OLD[Old Bank]
    MAT --- TEM[Temple Court]
    MAT --- FEN[Fenwick St]
    SEE -. 60GHz new .- HOL
    OLD -. fibre planned .- FEN
    MAT -.-> V1[venues]
    CHA -.-> V2[venues]
    SEE -.-> V3[venues]

Solid = fibre, dashed = 60 GHz or planned. Diagrams in the source live as inline Mermaid in DESIGN.md §2.2 (target) and DISCOVERY.md (as-built).

The eight hub sites

# Site Role Core router(s)
1 Colocation — 18-20 Fleet St Core, WAN hand-off, server room CR-COLO-01, CR-COLO-02
2 Mathew St Metro rack CR-MATHEWST-01
3 Charlotte St Metro rack + roof RB5009 CR-CHARLOTTE-01
4 Seel St Metro rack CR-SEELST-01
5 Temple Court Metro rack + roof RB5009 CR-TEMPLECT-01
6 Old Bank Metro roof (RB5009 only) CR-OLDBANK-01
7 Fenwick St Metro rack CR-FENWICK-01
8 Holmes Building Metro rack CR-HOLMES-01

Per-hub redundancy

Hub Primary path Backup path
Mathew St 10G fibre → Colo Venues fail over individually via 60 GHz → Temple Court
Charlotte St 10G fibre → Colo 60 GHz roof → Temple Court; venue CAT6 → roof RB5009
Seel St 10G fibre → Colo New 60 GHz → Holmes (currently single-homed)
Temple Court 10G fibre → Mathew St 60 GHz → Charlotte roof
Old Bank 2× 60 GHz → Colo roof (ECMP) 10G fibre → Fenwick (planned)
Fenwick St 10G fibre → Mathew St 60 GHz → via Old Bank roof
Holmes 2× 10G diverse → Colo (ECMP, one per colo CCR) — (already dual, diverse)

Ring closure (planned)

Two new links turn the star into two protected rings:

  1. Seel St ↔ Holmes, 60 GHz — closes the southern loop (Colo → Seel → Holmes → Colo). !!! warning "Revive, don't rebuild" A Holmes ↔ Seel 60 GHz dish pair already exists but is offline. Investigate why it is dormant before ordering hardware. See 60 GHz wireless.
  2. Old Bank ↔ Fenwick, 10G fibre — closes the western loop (Colo → Old Bank → Fenwick → Mathew St → Colo) and gives Mathew St a second fully-diverse exit.

As-built vs target

The estate is mid-migration, so as-built device names differ from the target naming (e.g. CR-LEVEL-01/02/03/04, CR-BOSTON-01). The move plan tracks each device's fate. A read-only discovery sweep on 2026-07-06 captured the current state; several routers were not reachable from the management source (RTR-CHR, RTR-EIN, RTR-FUS, RTR-IRH, RTR-NFL, RTR-SOH, RTR-TAV, RTR-WDS) and a few have unknown passwords (RTR-CAS, RTR-LOR, RTR-MCC, RTR-BPL).

Migration

The move follows: interconnect old + new racks → move WAN → re-home links backups-first → decommission. Golden rule: a new core port adopts the old core-side /30, so the far end needs zero config in the cutover window.

Key device fates:

Device Fate
CR-LEVEL-01 (CCR1016, ROS6) Decommission (holds public IPs until last)
CR-LEVEL-02 (CCR2004) Wipe → netinstall ROS 7.19 → re-use as CR-HOLMES-01
CR-LEVEL-03 (RB5009) Re-role → CR-COLOROOF-01 (needs a loopback assigned)
CR-LEVEL-04 (CCR2004) Re-role as retail-ISP bdr-2 (after WireGuard peers migrate off it)
CR-BOSTON-01 (CCR1009) Replaced in place by re-used LEVEL-02 → spares
CR-CELTICROOF-02, CR-LORDSTREETROOF-01 Remove
SERVER-ROUTER (RB4011) Decommission after server-room re-org (Phase 7)

Window discipline: venue-impacting moves Mon–Thu mornings; WAN cutover Sunday early AM; never Fri/Sat (trade nights).