Fibre Patching — Cores to Pass to New Colo Room¶
Version: 0.1 (framework — needs optic-type walk) — 2026-07-06 Every fibre terminating on CR-LEVEL-01 and CR-LEVEL-02 today, so we can size the fibre (core count) to run into the new colo room before patching. All plant is single-mode (SM). Core count depends on optic type per run:
- BiDi (WDM, one wavelength each way) = 1 core per link.
- Duplex (separate TX/RX) = 2 cores per link.
Source: live port comments + /ip address per port (DISCOVERY.md data). The Type column is the field walk you need to confirm — I can't read optic type remotely; fill BiDi/Duplex and the totals compute.
1. CR-LEVEL-01 (CCR1016, 12×SFP + 1×SFP+)¶
| Port | Terminates | Subnet(s) | Category | Passes to new room? | Type (confirm) | Cores |
|---|---|---|---|---|---|---|
| sfp1 | Yankees venue (1G) | 10.254.4.4/30 | Venue fibre | Yes | ? | 1–2 |
| sfp2 | Mathew St (VLAN 601) + peppers temp | 10.254.254.0/30, 10.254.4.8/30 | Provider L2 / temp | Yes (until 601-swap) | ? | 1–2 |
| sfp3 | SOHO venue (1G) | 10.254.4.0/30 | Venue fibre | Yes | ? | 1–2 |
| sfp4 | Electrik venue (1G) | 10.254.4.12/30 | Venue fibre | Yes | ? | 1–2 |
| sfp5 | Boston Pool core (1G) | 10.254.8.4/30 | Building/core fibre | Yes | ? | 1–2 |
| sfp6 | Starlink dish | — | Dish feed | Dish relocates separately | n/a | 0 |
| sfp7 | CR-LEVEL-02 (rack) | 10.254.5.4/30 | Local rack | No (both ends move) | DAC/short | 0 |
| sfp8 | SERVER-ROUTER | 10.199.199.0/30 | Local rack | No (server fabric rebuilt) | short | 0 |
| sfp9 | LEVEL venue (RTR-LVL) | 10.254.0.20/30, 10.123.67.0/30 | Venue fibre | Yes | ? | 1–2 |
| sfp10 | Server rack uplink (VLAN trunk: 10.1.5/6/7/30/90) | multiple | Local rack | No (rebuilt) | short | 0 |
| sfp11 | Old Bank roof — nRAY 60 GHz (port comment says "5 GHz" — wrong) | 10.254.5.28/30 | Roof radio feed | Roof feed (see §3) | ? | 0–1 |
| sfp12 | Backup internet | 10.254.5.36/30 | WAN | Yes (or re-terminate on OPNsense) | ? | 1–2 |
| sfpplus1 | Vive upstream 10G — trunk carrying provider L2 VLANs (Lago .5, Cheers .6, .7, 10.254.0.64, 10.254.5.60, 10.254.6.8/12). NB: .4 is NOT provider L2 — it's a Wireless Wire 60 GHz radio to Lord St (see WIRELESS-60G §4b) |
many | Upstream WAN + provider L2 | Yes — critical | ? | 1–2 |
⚠ sfpplus1 is the big one: a single 10G fibre to the provider (Vive) that also backhauls multiple sites as tagged VLANs (Lord St, Lago, Cheers, BNG). It is both your WAN and a chunk of your metro-over-provider L2. It must land in the new room; the 601-swap (MOVE-PLAN §4) is what eventually lets the metro traffic come off this provider path onto your own fibre, but the WAN handoff stays.
2. CR-LEVEL-02 (CCR2004, 12×SFP+ / sfp28)¶
| Port | Terminates | Subnet | Category | Passes to new room? | Type (confirm) | Cores |
|---|---|---|---|---|---|---|
| ether1 | CR-LEVEL-01 (copper?) | 10.254.5.4/30 | Local rack | No | copper/short | 0 |
| sfp-sfpplus1 | Boston core (2nd link) | 10.254.8.12/30 | Building/core fibre | Yes | ? | 1–2 |
| sfp-sfpplus2 | (spare / Boston?) | — | — | confirm | ? | 0 |
| sfp-sfpplus3 | Kells of Eden venue | 10.254.5.64/30 | Venue fibre | Yes | ? | 1–2 |
| sfp-sfpplus4 | Wood Street (WDS) venue | 10.254.7.0/30 | Venue fibre | Yes | ? | 1–2 |
| sfp-sfpplus5 | SOHO venue (2nd?) | 10.254.4.8/30 | Venue fibre | Yes (reconcile vs LEVEL-01 sfp3) | ? | 1–2 |
| sfp-sfpplus6 | CR-LEVEL-03 (roof) | 10.254.8.16/30 | Roof/rack | If roof stays: Yes | ? | 0–2 |
| sfp-sfpplus7 | CR-LEVEL-04 | 10.254.9.4/30 | Local rack | No (LEVEL-04 → bdr-2; link dies) | short | 0 |
| sfp-sfpplus8 | Seel St core | 10.254.70.0/30 | Building/core fibre | Yes | ? | 1–2 |
| sfp-sfpplus9 | Charlotte St core | 10.254.70.4/30 | Building/core fibre | Yes | ? | 1–2 |
3. Things to resolve on the walk¶
- Optic type per run — the whole point: mark each
?as BiDi (1 core) or Duplex (2 cores). BiDi is common on longer single-fibre venue runs; duplex on older/shorter. Don't assume — check the SFP part or the patch panel. - Roof radios (sfp11 Old Bank nRAY 60 GHz, plus other 60 GHz links): is the rack-to-roof segment fibre or Cat6? If fibre, it needs a core in the count (and the radios themselves eventually re-home to the colo roof RB5009 per MOVE-PLAN D1). If Cat6, it's out of the fibre core count but still needs a roof cable path.
- SOHO appears on both LEVEL-01 sfp3 (10.254.4.0/30) and LEVEL-02 sfp-sfpplus5 (10.254.4.8/30) — dual-homed, or a stale comment? Confirm; affects whether it's 1 or 2 physical fibres.
- sfpplus1 provider trunk: confirm with Vive whether the handoff to the new room is a re-terminate of the same fibre or a new cross-connect in the new room's meet-me. This drives your WAN cutover logistics (MOVE-PLAN Stage C) more than core count.
- Diversity: for the building-to-building core links (Boston, Seel, Charlotte) and the WAN, run diverse-path cores where the new-room build allows — the design wants two independent paths to key hubs (DESIGN §2.4).
4. Two-room model & inter-room core counts¶
Confirmed layout: fibres don't all land in one place. Two source rooms feed the new colo room (new CCRs + OPNsense):
- Old server room — where the colo venue fibres terminate. Assume all duplex (2 cores/link).
- Meet-me room — where the metro cross-connects and transit (Vive) come in. Assume all duplex (2 cores/link).
Vive WAN handoff is in-room, not an inter-room trunk: transit lands in the meet-me room → patches to the new core routers → those routers connect to OPNsense over SFP+ (DAC/short patch in-rack). That adds 0 cores to the inter-room trunks — the WAN→OPNsense hop never leaves the colo room.
4a. Old server room → new colo room (venue fibres)¶
Direct venue fibres discovered on the colo routers (excludes LOR/LAG/CHR, which ride the Vive L2 trunk = meet-me/transit, and Boston's venues, which land at the Holmes building not here):
| Venue router | Colo port | Notes |
|---|---|---|
| RTR-FUS (Fusion) | LEVEL-01 sfp1 | |
| RTR-YNK (Yankees) | LEVEL-01 sfp3 | |
| RTR-EIN (Einstein) | LEVEL-01 sfp4 | |
| RTR-LVL (LEVEL) | LEVEL-01 sfp9 | |
| RTR-KEL (Kells) | LEVEL-02 sfp-sfpplus3 | |
| RTR-WDS (Wood Street) | LEVEL-02 sfp-sfpplus4 | |
| RTR-SOH (SOHO) | LEVEL-02 sfp-sfpplus5 |
7 venue fibres today × 2 (duplex) = 14 cores. Target design adds colo-fed venues (Diego Demise, Playbox, Cheers, Electrik…) → plan for ~12 venues = 24 cores.
4b. Meet-me room → new colo room (metro + transit)¶
| Link | Type | Cores (duplex) |
|---|---|---|
| Mathew St (own fibre, post 601-swap) | Metro | 2 |
| Charlotte St | Metro | 2 |
| Seel St | Metro | 2 |
| Holmes (Boston) link A | Metro | 2 |
| Holmes (Boston) link B (diverse) | Metro | 2 |
| Old Bank (fibre when built; 60 GHz today) | Metro | 2 |
| Vive WAN primary (transit) | Transit | 2 |
| Backup internet (diverse transit) | Transit | 2 |
| Total | 16 cores |
4c. Recommended trunk sizes (both rooms are in-building → over-provision cheaply)¶
| Trunk | Used now | Target | Pull |
|---|---|---|---|
| Old server room → colo room | 14 | ~24 | 24-core (or 48 for long-term venue growth) |
| Meet-me room → colo room | 16 | ~20 | 24-core |
Total to order: 2× 24-core SM (48 cores) if patching each fibre through individually — the simple, no-active-kit option.
Alternative — collapse with in-room aggregation: drop a small switch/router in each source room and trunk over 2× fibre (BiDi or a pair) per room instead of 24 individual cores. Turns 48 cores into ~8, at the cost of active kit + power in each room. Worth it only if core-pulling is expensive here; since these are short in-building runs, direct patch-through is usually simpler — but note the option.
5. Next actions¶
- Confirm the venue list in §4a against the four ambiguities in §3 (esp. SOHO dual-homing, and whether LOR/LAG/CHR get their own fibre or stay on the Vive L2 path — if they get fibre they move into §4a and add 6 cores).
- Order 2× 24-core SM (old-server-room and meet-me-room trunks to the colo room) unless you adopt in-room aggregation.
- The BiDi/Duplex
Typecolumn in §1–2 is now moot for sizing (assumed all-duplex) but still worth recording per run for optic ordering.