Rack, row and building links
Application decision brief
Data Centre Optics & DCI
Choose the link architecture before choosing the optic. MingApex coordinates the named host, fibre, reach, connector, sample and lot evidence for leaf–spine, top-of-rack and DCI projects.
Selected by distance and serviceability
Result tied to platform and revision
A data-centre bill of materials should begin with port speed, topology, physical distance and the installed fibre plant. Part numbers come after these constraints, because an SR4, LR4, CWDM4 or DAC decision changes connector type, patching, loss budget and maintenance procedures.
Migration planning matters as much as day-one reach. A 25G server edge feeding 100G spine links may later move to 400G uplinks, so breakout capability, FEC behaviour, host firmware and spare strategy should be recorded before the first sample.
MingApex operates as a China-based sourcing, OEM-coordination and independent quality-control partner. The approval record is therefore linked to the exact quoted configuration rather than a generic compatibility claim.
01 / Architecture
Translate the network requirement into an optical path
Use distance, fibre and operational access to decide the media. Then validate the exact host and software combination.
| Network requirement | Recommended design path | Confirm before approval |
|---|---|---|
| Inside the rack | Passive DAC or short AOC where power, bend radius and service access permit. | Cable length, EEPROM/coding, port cage and airflow. |
| Across the row or hall | SR optics or AOC matched to MMF type and connector topology. | OM3/OM4 reach, MPO polarity, insertion loss and cleaning. |
| Between halls or buildings | LR4/CWDM4/FR4 over SMF when duplex LC and longer reach are required. | Loss budget, patch count, chromatic path and host FEC. |
| DCI wavelength expansion | CWDM/DWDM path where fibre scarcity justifies passive wavelength multiplexing. | Channel plan, optical budget, mux loss and protection route. |
02 / Real catalogue anchors
Product examples for a controlled starting point
These live catalogue pages are concrete BOM anchors; the final choice still depends on the named switch/NIC and fibre route.
Verified live product page25G SFP28 1310nm LR 10km LC TransceiverServer edge and longer-reach 25G uplinksVerified live product page100G QSFP28 SR4 100m MPO TransceiverHigh-density multimode fabric linksVerified live product page100G QSFP28 LR4 10km LC TransceiverSingle-mode inter-building or DCI pathVerified live product page100G QSFP28 Passive DAC CableShort in-rack or adjacent-rack connectionsVerified live product page100G QSFP28 CWDM4 2km LC TransceiverDuplex-LC campus and data-centre reach
Catalogue examples define a starting configuration, not automatic proof for a different host, revision, reach or fibre plant.
03 / Deployment patterns
Where this application architecture is used
The same speed can serve very different physical and operational patterns. Document the use case before freezing the SKU.
Leaf–spine fabric
Server-facing 25G/100G ports aggregate toward 100G/400G spine capacity with defined oversubscription and breakout rules.
Top-of-rack refresh
Existing rack cabling, cage density and airflow determine whether DAC, AOC or pluggable optics are maintainable.
Data-centre interconnect
Building separation, route loss, patch panels and protection paths define LR/FR/WDM selection.
Migration staging
Old and new speeds coexist with approved breakouts, firmware baselines and labelled spare pools.
04 / Validation
Sample, compatibility and release workflow
Approval should move from paper specification to named-host sample, then from sample identity to production-lot release.
- 1
Freeze the link definition
Record host, software, port role, speed, reach, fibre, connector and patch topology.
- 2
Map the BOM boundary
Separate cable, optic, mux, patch lead and spare requirements by link zone.
- 3
Validate the named sample
Check recognition, DOM, link stability, error counters, FEC and temperature behaviour on the named host.
- 4
Lock identity and change control
Keep coding profile, label, serial format, firmware and component-change approval linked to the sample.
- 5
Release the production lot
Use quantity, identity, optical checks, packaging and shipment records tied to the order line.
05 / Commercial control
MOQ, lead time and pricing factors
Commercial terms should follow the frozen link map. Mixed speeds and many coding profiles can change MOQ and lead time more than total unit count.
| Commercial item | What changes the outcome | Buyer action |
|---|---|---|
| MOQ | Mixed SKUs, coding profiles and custom labels split the effective quantity. | Share quantities by exact host and part-number line. |
| Lead time | Sample approval, coding, optics availability and lot inspection add separate stages. | Provide target delivery and identify which links are critical-path. |
| Pricing | Reach, wavelength, temperature, connector, coding and warranty affect cost. | Request line-item pricing instead of a blended unit price. |
| Spares | Rare reaches and legacy hosts may require a controlled spare pool. | Define spare ratio and identity-matching rule before order. |
06 / Evidence
Downloadable buyer evidence pack
Use the redacted templates to define what must be recorded for the exact quoted configuration.
07 / Risk control
Failure modes to remove before shipment
Host recognition without link stability
A coded module can be recognized yet fail under load; test counters and FEC over a defined period.
Connector and fibre mismatch
SR4 MPO, duplex LC and different fibre grades are not interchangeable; audit the physical path.
Sample-to-lot drift
An approved sample does not control later coding or component changes unless identity is locked.
Unplanned migration boundary
Breakout and mixed-speed support can differ by line card and software release; record both.
08 / Buyer questions
Application-specific questions
Should we choose DAC, AOC or pluggable optics inside the rack?
Use actual length, airflow, bend radius, service access, port compatibility and replacement method. DAC is not automatically best merely because the distance is short.
Does a compatible code guarantee the link?
No. Coding supports recognition, while link success also depends on host software, FEC, fibre, connector, optical budget and traffic stability.
Can one approved 100G sample cover every switch?
No. The result belongs to the named host model, software, port and sample identity unless the validation scope explicitly proves otherwise.
What should be sent with the RFQ?
Share the link map, host list, software versions, line rate, reach, fibre, connector, quantity by SKU, spare ratio and target delivery.
Controlled next step
Send the rack, row and DCI link map—not only a part-number list.
MingApex will return a structured optical path, validation boundary, sample plan and commercial line-item review for the named data-centre project.