Optical Transceivers · Telecom Synchronization · Network Infrastructure · Custom Solutions
A leaf-spine fabric is a two-layer network: every leaf switch connects to every spine switch, and every server or storage node connects to one or more leaves. The port rate is the same across the fabric, but the roles are not. Server facing ports run short links inside a rack or across a row, while leaf to spine links run longer and carry the oversubscribed aggregate of everything below them.
At 400G the two roles end up on different optics, and the reach classes tell them apart. This guide covers the standard positions in a 400G fabric, what decides the choice at each, and how the cabling carries into 800G. Rate families are listed on the 400G QSFP-DD and OSFP and 800G pages.
Server to leaf links are usually under 100 m and often inside a single row, so multimode parallel optics, direct attach cables or active optical cables cover them at low cost per port. Where a row spans more than a hundred metres, an SMF parallel part at 500 m to 2 km replaces the multimode link.
Leaf to spine links run between rows, halls or down a building riser, and they carry the aggregate of many server ports. A 400G fabric commonly runs these on single-mode parallel or duplex WDM parts, chosen by the measured route, because a spine link that only needs 500 m is a different purchase from one that needs 10 km.
| Position | Module | Media / wavelength | Reach class | Where it usually lands |
|---|---|---|---|---|
| Server to leaf, in row | 400G multimode parallel, DAC or AOC | MMF, 8 or 16 fibre MPO | 50 to 100 m class | Top-of-rack links inside one row |
| Server to leaf, longer | 400G DR4 or DR4+ | SMF, 8-fibre MPO, 1310 nm | 500 m to 2 km class | Single-mode cabled rows and hall to hall |
| Server to leaf, duplex only | 400G FR4 or LR4 | SMF duplex, CWDM or LAN-WDM | 2 to 10 km class | Where no MPO trunk is available |
| Leaf to spine, short | 400G DR4 or DR4+ | SMF, 8-fibre MPO, 1310 nm | 500 m to 2 km class | Spine links within one hall |
| Leaf to spine, campus | 400G FR4 or LR4 | SMF duplex, CWDM or LAN-WDM | 2 to 10 km class | Between buildings or down a riser |
| Leaf to spine, metro or campus backhaul | 400G ZR or ZR+ coherent | SMF, DWDM C-band tunable | Metro DCI class upward | Where fibre is scarce or the span is tens of kilometres |
| Breakout at the leaf | 400G to 4 x 100G | MPO trunk with 100G DR1 or PSM4 parts | Per lane class | One spine port feeding four lower rate ports |
Reach classes are the standard ones for each family, and the working limit is the measured loss through the real patch field. Parallel single-mode positions are covered by parts such as the APX-QSFP-DD-400G-2KM-DR4P, and the coherent end of the fabric by the 400G ZR DCI selection guide.
Single-mode parallel parts need eight-fibre MPO trunks, and the strand count grows four times faster than the port count. A row of forty 400G links needs three hundred and twenty strands on the parallel route, against eighty on the duplex route. The trunk is usually the long lead item, so the cable plan belongs in the planning phase.
Polarity is the other item that fails at turn-up: an MPO trunk wired for one polarity with optics that expect another shows a link that never comes up. Fix the polarity on paper, keep the patch record, and use one trunk type throughout the fabric.
The point of a two-layer fabric is predictable oversubscription: the spine carries the sum of the leaves. A leaf with thirty-two downlinks can be built with eight or sixteen uplinks and left with a two or four to one ratio, and the uplink count sets the spine port count. Compute the uplink count before the optics, because a plan that moves from four to one to two to one doubles the spine ports and the leaf-to-spine modules.
Where the rate changes inside the fabric, breakouts are the usual tool: a 400G spine port feeding four 100G leaf ports. Breakouts keep the trunk count down, but they also share the port between four services, so the failure domain belongs in the decision.
Fabric rooms run warm and the rows fill with high power modules. Confirm the temperature grade per position and the power per cage before the port count is fixed, and check that the module reports diagnostics to the monitoring platform.
The next step is usually 800G on the same trunk: the MPO or duplex pair already in place carries either, and the spine modules change rather than the cable. Builds that will migrate should fix the cabling class now; the worked comparison is on the 400G to 800G migration page, with the AI cluster case on the AI training cluster interconnect page.
Can a 400G fabric run on duplex fibre only?
Yes, with 400G FR4 or LR4 class parts at 2 to 10 km, or coherent parts where the span is longer. It uses fewer strands and costs more per port than a parallel part.
Should server links be multimode or single mode?
Decide by row length and by what is already cabled. Under about a hundred metres multimode is the cheaper position; single mode suits longer rows and a plant that is single mode throughout.
Is a DAC or an AOC an option at 400G?
Yes for short in-row links, and both avoid two optical ports. They are fixed length, so the rack layout has to be settled first.
When does a spine link need coherent optics?
When the span is tens of kilometres, fibre is scarce, or the link crosses sites. Inside a hall the grey and parallel parts cover it at lower cost.
What do you need to quote a 400G fabric?
The position list by role, the measured distances and loss, the cable class in place or planned, the oversubscription ratio, the platform per switch and the temperature at each end.
Send the position list, the measured routes, the cable class and the platform per switch, and we come back with a part per position, the reach class, the connector and polarity per link, and the spare lines for the fabric. Related reading: 800G DR8 against FR4 and ZR+, the 800G AI data centre interconnect guide, and all optics selection guides.
APEX is a communication technology brand focused on optical transceivers, telecom synchronization products, and network infrastructure equipment. We provide products and engineering support for telecom operators, data centers, mobile networks, and enterprise customers worldwide.
APEX GROUP is headquartered in Hong Kong, with our core team and supply chain operations based in China. We ship to customers across Asia, the Middle East, Europe, Africa, and the Americas.
We are a brand owner with deep engineering partnerships. We control product design, specification, quality validation, and supply chain management. Our products are built to our specifications by qualified manufacturing partners, and we handle all testing, coding, and quality assurance before shipment.
Yes. We code transceivers to match the host platform requirements of major switch and router vendors including Cisco, Juniper, Arista, HPE, Huawei, Nokia, and others. Tell us your platform model and required OS version, and we will ship modules that are recognized natively by your equipment.
Datasheets, compatibility matrices, and S-parameter reports are available for all standard products. Contact our sales team or visit the product pages on our website to request documentation.
Provide us with your switch make, model, and OS version. We code the transceiver firmware accordingly before shipment. If you are testing for the first time, we recommend ordering a sample unit to validate compatibility in your specific environment before placing a volume order.
Switch vendors occasionally introduce transceiver whitelisting in new OS releases. We track major platform updates and can provide recoded firmware matching the new OS requirements. Contact technical support if your existing APEX modules stop being recognized after a switch upgrade.
Contact our sales team by email, WhatsApp, or WeChat with your part number and quantity. We will confirm pricing, lead time, and shipping options. For first-time customers, we typically recommend starting with a sample order to validate compatibility before scaling to production volumes.
We ship via DHL, FedEx, and UPS for express delivery, typically 3-7 business days to most destinations. For volume orders, we also offer air freight and sea freight options. We can ship on your courier account or ours, and we handle all export documentation.
Sample orders start from 1-2 units for evaluation. For production orders, MOQ varies by product type, typically 10-50 units for standard transceivers. Contact us for specific product MOQs.
We accept wire transfer (T/T) as our standard payment method. For established customers, we can offer net-term payment arrangements. Contact our sales team to discuss payment terms.
All APEX products come with a 3-year standard warranty against manufacturing defects. We offer advance replacement for defective units, shipping the replacement before you return the failed unit to minimize downtime. For full details, visit our After-Sales Service page.
Contact us by email, WhatsApp, or WeChat. Describe your issue with as much detail as possible, including switch model, OS version, transceiver part number, and the problem you are seeing. Our support engineers will respond within one business day.
Yes, we strongly encourage sample testing. Order 1-2 units of each model you plan to deploy. Test them in your switches with your fiber plant and traffic load. Once validated, we can proceed with production quantities.
Yes. Many of our customers are telecom operators and government networks requiring 5-10 year supply continuity. We offer lifecycle management commitments with advance notification of any changes. See our Global Supply Chain page for details on long-term supply programs.