← Back to AI & Optics

Planning framework

Optical connectivity scenarios

Use these physical-link patterns to organize an architecture your team, vendor or integrator has already defined. Each scenario highlights the inputs needed before selecting an NRCube product.

“Addressing this demand will require holistic architectures that connect vast numbers of fast computing nodes over intelligent networking fabrics.”Jensen Huang — Founder and CEO, NVIDIAREAD

AI & Data Center

High-density compute and fabric connectivity

The existing AI scenarios remain focused on server, rack, leaf–spine, breakout and data-hall links.

Scenario 01

Inside-rack connections

Server, accelerator, storage or appliance ports connected to a top-of-rack switch.

Review
Port type, speed, cable routing, airflow and maximum length.
Typical fit
DAC for supported short links; AOC or pluggable optics where fiber handling or reach favors optical media.
Plan this BOM →
Scenario 02

Rack-to-rack links

Connections between adjacent racks or across an aisle within the same data hall.

Review
Measured route, cable management, connector strategy and spare capacity.
Typical fit
AOC or pluggable multimode/single-mode optics, depending on distance and infrastructure.
Plan this BOM →
Scenario 03

Leaf-to-spine fabric

High-density uplinks between leaf and spine tiers in an existing network design.

Review
Native speed, breakout mode, lane mapping, radix and redundancy.
Typical fit
400G or 800G transceivers, AOCs or breakout assemblies selected to match both ends.
Plan this BOM →
Scenario 04

Breakout connectivity

One higher-speed port divided into multiple lower-speed endpoints.

Review
Host breakout support, lane count, endpoint form factor and topology.
Typical fit
Breakout DAC/AOC assemblies or parallel optics with the correct fiber harness.
Plan this BOM →
Scenario 05

Across a data hall

Structured links spanning rows, zones or aggregation points.

Review
End-to-end path length, patching loss, fiber type, panels and polarity.
Typical fit
Pluggable optics plus structured fiber assemblies, selected by reach and link budget.
Plan this BOM →
Scenario 06

Campus or DCI handoff

Longer optical paths handed to a transport or facility design.

Review
Actual link budget, wavelength plan, amplification, FEC and platform constraints.
Typical fit
Long-reach optics only after detailed engineering and equipment-vendor confirmation.
Plan this BOM →

Enterprise & Campus

Reliable access, distribution and campus backbone links

Plan optics around switch hierarchy, building distances, installed fiber and resilient uplinks.

Enterprise 01

Access–distribution–core campus

Access switches connect to redundant distribution switches, which connect to the campus core.

Review
Switch tiers, uplink speed, redundancy, connector and available campus fiber.
Typical fit
1G through 100G SFP or QSFP optics, DAC/AOC for supported equipment-room links.
Plan this BOM →
Enterprise 02

Building-to-building backbone

Core, distribution or aggregation switches connect across campus buildings.

Review
Route distance, single-mode or multimode fiber, patching, loss and diverse paths.
Typical fit
Single-mode LR families for longer campus paths; appropriate SR families within supported multimode reach.
Plan this BOM →

WAN & Router

Router links for sites, providers and regional networks

Capture handoff speed, reach, resiliency and the equipment interfaces at both ends.

WAN 01

Dual-router WAN edge

Redundant enterprise routers connect to one or more service-provider handoffs.

Review
Sites, routers, provider circuits, demarcation interface, speed and failover design.
Typical fit
1G, 10G, 25G or 100G optics selected for the router and provider handoff.
Plan this BOM →
WAN 02

Regional router backbone

Routers connect offices, data centers, POPs or regional sites over longer paths.

Review
Actual distance, fiber ownership, link budget, intermediate transport and diverse routing.
Typical fit
LR, ER or ZR families where platform support and detailed link engineering permit.
Plan this BOM →

Service Provider & Telecom

Access, aggregation, metro and transport-facing connectivity

Organize optics for provider scale without treating the examples as complete transport designs.

“We are continuing to advance the role of pluggables to reach into more parts of the network, replacing functions traditionally delivered from a dedicated chassis.”Bill Gartner — Senior Vice President and General Manager, Optical Systems & Optics, CiscoREAD
Service Provider 01

Access-to-aggregation network

Access devices connect to redundant aggregation switches or edge routers.

Review
Access locations, device count, uplink speed, oversubscription, protection and reach.
Typical fit
10G through 400G pluggable optics selected for access, aggregation and edge interfaces.
Plan this BOM →
Service Provider 02

Metro/core transport handoff

Edge or core routers connect to transport, optical-line or peering equipment.

Review
POP count, transport handoffs, wavelength plan, FEC, link budget and diverse paths.
Typical fit
100G or 400G LR/ER/ZR and wavelength-specific optics subject to engineering confirmation.
Plan this BOM →

Other architectures and verticals

Customer-defined connectivity

Healthcare, education, manufacturing, government, utilities and other environments can provide their equipment, ports, locations, reach, redundancy and operating constraints without being forced into a predefined architecture.

Describe your requirement