πŸ™οΈ MAN

Metropolitan Area Network β€” Low-Latency Metro Fabric for Sites, Data Centers & Cloud

A MAN (Metropolitan Area Network) links your buildings, campuses, and colocation sites across a metro with low latency, high bandwidth, and strong SLAs.
SolveForce designs MANs that are application-aware, secure-by-default, and evidence-richβ€”using Lit Ethernet (EPL/E-LAN), Wavelength, Dark Fiber rings, and MPLS/VPLS, integrated with SD-WAN and cloud on-ramps.

Where this fits:
πŸ–§ Fabric β†’ Networks & Data Centers β€’ 🌐 Catalog β†’ Connectivity
πŸ”€ Overlay β†’ SD-WAN β€’ πŸ”— On-Ramps β†’ Direct Connect β€’ 🏒 Hubs β†’ Colocation
πŸ”’ Security β†’ Cybersecurity β€’ πŸ“Š Evidence β†’ SIEM / SOAR


🎯 Outcomes (Why SolveForce MAN)

  • Deterministic performance β€” metro-class latency/jitter for DCI, storage replication, voice/video, and AI fabrics.
  • Resilience by design β€” protected rings, diverse laterals/POPs, and documented SLOs.
  • Cloud-ready β€” deterministic paths to AWS/Azure/GCP via carrier-dense colos and private on-ramps.
  • Security built-in β€” L1/MACsec/IPsec, microsegmentation, and identity-aware access.
  • Audit-grade β€” turn-up baselines, OTDR traces, and monthly SLA reports exported to SIEM.

🧭 Scope (What We Build & Operate)

  • Lit Ethernet β€” EPL (point-to-point), E-LAN (any-to-any), EVPL (point-to-multipoint). β†’ Lit Fiber
  • Wavelength (DWDM) β€” 10/100/400G+ Layer-1 lambdas for DCI and HPC/AI. β†’ Wavelength Services
  • Dark Fiber rings β€” you light it for max control/scale. β†’ Dark Fiber
  • MPLS/VPLS β€” managed L3/L2 for QoS or legacy L2 adjacency. β†’ MPLS β€’ VPLS
  • PTP microwave/mmWave β€” fast metro inter-building links where fiber is impractical. β†’ Fixed Wireless

🧱 Building Blocks (Spelled Out)

  • Topologies β€” protected rings, hub-and-spoke to colo hubs, or partial mesh between key sites.
  • Handoffs β€” 1/10/25/40/100/400 GbE (electrical/optical LR/LR4/ER4) with QinQ/MTU planning.
  • QoS/CoS β€” EF for voice/telepresence; AF for interactive; BE for bulk; class-based SLOs.
  • Cloud interconnect β€” MAN terminates in colo β†’ private on-ramp (Direct Connect/ExpressRoute/Interconnect). β†’ Direct Connect

πŸ” Design Patterns (Choose Your Fit)

1) Metro DCI (Data Center Interconnect)

  • Wavelength (L1) or EPL (L2) for low, predictable latency; jumbo frames; optional L1 encryption or MACsec.

2) Campus & Multi-Building

  • E-LAN any-to-any or hub-and-spoke EVPL; segment by function; route near the edge to bound L2 domains.

3) AI/HPC East-West

  • Dense lambdas on Wavelength or Dark Fiber; NCCL-aware leaf/spine; NVMe caches; deterministic microburst headroom.

4) Hybrid WAN (Metro Core)

  • Use the MAN as a regional core; branches attach via SD-WAN; break out to cloud at metro hubs.

5) Regulated / Policy Networks

  • Deterministic CoS, encrypted trunks, segmentation, and immutable logs for HIPAA/PCI/NIST enclaves.

πŸ“ SLO Guardrails (Typical Metro Targets)

Class / MediumOne-Way LatencyJitter TargetSustained LossAvailability*
Wavelength (metro)≀ 1–2 ms≀ 0.5–1 ms< 0.1%99.99% (with protection)
Lit EPL / E-LAN (metro)≀ 1–3 ms≀ 1 ms< 0.1%99.95–99.99%
Dark Fiber (engineered)β‰ˆ ~5 Β΅s/km + gear≀ 0.5–1 ms< 0.1%Design-dependent
PTP Microwave/mmWave≀ 2–5 ms≀ 1–3 ms< 0.1–0.3%99.5–99.95%

*Higher availability with diverse conduits/bridges/POPs and protected rings. SD-WAN can mask brownouts by steering before outages.


πŸ”’ Security & Zero-Trust (Concrete, Enforceable)

  • Encryption β€” L1 AES-256 on transponders, MACsec at L2, or IPsec at L3 by policy. β†’ Encryption
  • Segmentation β€” VRFs/ACLs and microsegmentation for least privilege. β†’ Microsegmentation
  • Identity & access β€” ZTNA/SASE for users/admins; no flat VPNs. β†’ ZTNA β€’ SASE
  • Boundary protection β€” WAF/Bot at the metro edge; DDoS stance and Anycast withdraw options. β†’ WAF / Bot Management β€’ DDoS Protection
  • Evidence β€” keys in Key Mgmt/HSM; logs to SIEM/SOAR with WORM retention. β†’ Key Management / HSM β€’ SIEM / SOAR

πŸ“Š Observability & NOC

  • Optical β€” light levels/OSNR, FEC/BER, OTDR traces;
  • Ethernet β€” latency/jitter/loss, errors, class stats;
  • Microwave β€” RSSI/SNR, fade margins, weather impact.
    Dashboards, alarms, and carrier escalation trees with monthly SLA reports. β†’ Circuit Monitoring β€’ NOC Services

πŸ’΅ Commercials (What Drives Cost)

  • Medium & speed (Wave/Lit/Dark/Microwave), distance, protection & diversity, cross-connects (MMR), and construction of laterals.
  • IRU vs Lease for Dark Fiber; managed optics vs DIY; MACsec/IPsec/L1 encryption options; HA headends.

πŸ§ͺ Turn-Up & Acceptance

1) Provisioning β€” wave/EPL params or fiber span; radio alignment for microwave.
2) Baselines β€” RFC 2544 / ITU-T Y.1564 throughput/latency/jitter/loss; optical OTDR & light levels or RF link budget.
3) Security β€” MACsec/IPsec/L1 encryption validation; key custody evidence.
4) Handover β€” as-builts, diagrams, configs, test artifacts; NOC thresholds & escalation.

Artifacts stored and exported to SIEM for audits. β†’ SIEM / SOAR


πŸ› οΈ Implementation Blueprint (No-Surprise Rollout)

1) Inventory & SLOs β€” sites, DCs/colos, clouds; per-app loss/latency/jitter targets.
2) Topology β€” ring vs hub-and-spoke vs mesh; plan diverse laterals/bridges/POPs (request route letters).
3) Medium β€” Wavelength/Lit/Dark/Microwave by use case; MTU & CoS plan.
4) Cloud on-ramps β€” colo hubs with private interconnects and BGP policy.
5) Security β€” encryption (L1/MACsec/IPsec), ZTNA/SASE for users, microseg for workloads.
6) Turn-up tests β€” archive baselines & OTDR traces; accept against SLOs.
7) Operate β€” NOC thresholds, SLO dashboards, monthly SLA reports; quarterly optimization.


βœ… Pre-Engagement Checklist

  • πŸ“ Endpoints (addresses/colo MMRs) and desired speeds.
  • πŸ”€ Diversity requirements & evidence needs (route letters/maps).
  • πŸ” Encryption policy (L1/MACsec/IPsec), key custody (CMK/HSM), PKI.
  • 🧭 CoS/QoS classes; jumbo MTU alignment.
  • ☁️ Cloud on-ramp plan and DNS/Anycast strategy.
  • πŸ“Š SIEM/NOC destinations; reporting cadence; escalation contacts.
  • πŸ’° Term/budget guardrails; cross-connect logistics; construction constraints.

πŸ”„ Where MAN Fits (Recursive View)

1) Grammar β€” metro rails in Connectivity.
2) Syntax β€” composes the metro fabric in Networks & Data Centers and on-ramps in Cloud.
3) Semantics β€” Cybersecurity preserves integrity (encryption, segmentation, evidence).
4) Pragmatics β€” SolveForce AI predicts congestion, weather risk (microwave), and capacity needs.
5) Foundation β€” consistent terms via Primacy of Language.
6) Map β€” indexed in SolveForce Codex & Knowledge Hub.


πŸ“ž Build a Metro Network That’s Fast, Secure & Auditable

Related pages:
Lit Fiber β€’ Wavelength Services β€’ Dark Fiber β€’ MPLS β€’ VPLS β€’ Fixed Wireless β€’ SD-WAN β€’ Direct Connect β€’ Colocation β€’ Circuit Monitoring β€’ NOC Services β€’ Cybersecurity β€’ Connectivity β€’ Networks & Data Centers β€’ Knowledge Hub