Technical sources reviewed: September 3, 2026
Quick answer: Spine-leaf cabling design starts with fabric math and the transceiver media-dependent interface (MDI). The topology defines which switches connect; it does not select the cable. The MDI, fiber allocation, route and channel map determine whether the link uses duplex LC, MPO-12, MPO-16, dual MPO, AOC, DAC or another interface.
Engineering notice: The module examples and calculations are for design reference only, not a compatibility or performance guarantee. Use current data sheets for the exact endpoint SKUs and an approved project channel plan.
In this guide, leaf spine fiber cabling means the physical channels between the two switch tiers. The phrase does not assume one fiber category, connector or assembly type.
Contents
- Spine-leaf cabling in five decisions
- What the topology fixes and leaves open
- Calculate the fabric before choosing a cable
- Map each link class to the exact transceiver MDI
- Choose the physical cabling architecture
- Specify fiber, cable construction and pathway conditions
- Add international procurement requirements to the schedule
- Build the channel map before the BOM
- Treat 400G-to-800G migration as a compatibility review
- Turn the design into a trunk and patching schedule
- Label, inspect and commission against the approved plan
- Common specification failures
- FAQ
- Request a BOM review
Spine-leaf cabling in five decisions
Complete these five checks before releasing a cable schedule:
- Record the leaf count, spine count, links per leaf-spine pair, link speed and ports reserved for other roles.
- Record the manufacturer and part number at both ends of every link class, including port mode and breakout mode.
- Choose direct equipment cords, a structured trunk route, cassettes or a mapped optical mesh to suit the pathway and change model.
- Document every connector, adapter, splice, lane mapping and Tx-to-Rx path. Calculate channel loss from the module specifications and project margin.
- Issue a trunk and patching schedule with its revision, labels, approver and acceptance records.
Buyer summary: Before requesting a spine-leaf cabling quotation, freeze the fabric counts, exact endpoint switch and transceiver part numbers, port modes, rack-to-rack routes, required link distances and project acceptance method. Calculate each link class, then map its MDI, active fiber positions, connector presentation, polarity path, mated pairs and loss allowance. Add the project country, pathway and document requirements, quantity, named delivery point and target schedule. Keep unresolved fields on hold. A supplier response should identify the proposed configuration, applicable documents, deviations, commercial assumptions and acceptance deliverables against the same schedule revision.
Hold the RFQ if one of these inputs is still an assumption. A correct port count paired with the wrong MDI can produce a complete-looking BOM that cannot be connected.
Use the sequence Count → MDI → Route → Map → Release on every revision. If the exact endpoint SKUs and rack route are already known, send BWNFiber the link matrix for a pre-quotation input review. The purpose is to expose unresolved fields before pricing, not to certify an assumed interface or promise compatibility.
What the topology fixes and leaves open
In a conventional two-tier Clos fabric, every leaf connects to every spine. This full-mesh relationship gives predictable link counts and multiple equal-cost paths; Cisco describes this same leaf-to-every-spine model in its two-tier fabric design guide.
The topology fixes:
- which switch pairs need inter-switch connectivity;
- how many physical links are needed when the link multiplier is known;
- the leaf-facing fabric-port demand on each spine;
- the aggregate uplink bandwidth available to each leaf.
The topology does not fix:
- the connector, polish, keying or pinning at a transceiver;
- single-mode versus multimode fiber;
- native versus breakout operation;
- direct cords versus structured trunks and patch fields;
- end-to-end polarity, channel loss or acceptance limits.
The equipment and physical-layer design control the remaining choices. MPO suits parallel lanes and high-fiber-count routes, but the topology does not require it. Review the BWNFiber MPO cabling overview after the required interface and channel are defined.
A useful spine leaf cabling diagram should therefore show both the logical switch relationships and the physical link classes. Likewise, spine leaf MPO cabling describes one possible implementation, not a rule that every link has an MPO interface.
When is spine-leaf the right fit?
Spine-leaf is a candidate, not a default answer for every network. Juniper treats workload demand, oversubscription and the intended scale step as design inputs in its spine-and-leaf fabric paper. Use the topology only after those inputs justify its extra cross-tier links.
| Decision dimension | Conventional two-tier leaf-spine block | Core-distribution-access hierarchy |
|---|---|---|
| Interconnection pattern | Every leaf connects to every spine in the block | Access devices connect through one or more aggregation/distribution layers according to the design |
| Path model | Same-tier endpoint traffic normally crosses a leaf, one spine and another leaf unless both endpoints share a leaf | Path and hop count depend on endpoint placement, layer boundaries and the specific hierarchy |
| Growth model | Add leaves for edge ports and use available leaf/spine radix for fabric scale steps | Expansion may use additional access blocks or larger aggregation/core platforms |
| Cabling effect | Link quantity grows with the leaf-to-spine matrix, increasing the need for repeatable routes and labels | Fewer full cross-tier relationships may be required, but routes are design-specific |
Neither column guarantees latency, nonblocking behavior, availability or lower cost. Those outcomes depend on capacity, traffic, protocols, failure state and implementation.
| Project condition | Design response | Physical-layer consequence |
|---|---|---|
| Repeated east-west traffic across many racks, with a need for multiple equal-cost paths | Evaluate a symmetric two-tier leaf-spine fabric | Every leaf-to-spine relationship must be represented in the link matrix and pathway plan |
| Small, stable environment with limited inter-rack traffic | Compare a collapsed core, a smaller routed design or the existing hierarchy before adding a fabric | Avoid buying and managing cross-tier links that do not solve a measured requirement |
| Scale requires pods, a super-spine or another stage | Define each fabric block and the links between blocks separately | The L × S × k formula in this guide applies to one symmetric leaf-spine block, not the entire multi-stage network |
| Service targets must be maintained after a spine or link failure | Size both the normal and degraded states; validate routing, convergence and traffic distribution separately | Reserve the required ports and pathways, but do not treat installed cable count as proof of application performance |
This guide controls the link count and physical channel. It does not replace the logical design for routing, ECMP, failure domains, congestion control, security or overlays.
Calculate the fabric before choosing a cable
How do you calculate spine-leaf cable count?
For a symmetric full mesh, define:
- L = number of leaf switches;
- S = number of spine switches;
- k = physical links between each leaf-spine pair;
- V = usable bandwidth of each link;
- D = aggregate downlink bandwidth on one leaf;
- P = fabric ports available on one spine after reservations;
- R = target downlink-to-uplink ratio.
Calculate these values:
| Design result | Formula | Meaning |
|---|---|---|
| Uplink bandwidth per leaf | U = S × k × V | Sum of all leaf-to-spine links |
| Achieved oversubscription | D ÷ U | Downlink bandwidth divided by uplink bandwidth |
| Inter-switch link count | L × S × k | Excludes management, border, inter-pod and spare links |
| Leaf-facing ports per spine | L × k | The port demand on each individual spine |
| Maximum leaves per spine | floor(P ÷ k) | Use available ports after reservations |
| Minimum symmetric link multiplier | k = max(1, ceil(D ÷ (R × S × V))) | Use only when the chosen switch design supports that many links per pair |
Every spine connects to every leaf. Its leaf-facing demand is L × k, not its port count divided by the number of spines.
Treat the leaf spine oversubscription calculation as a capacity input. It does not select the transceiver, cable or acceptance limit.
Check normal and degraded-state capacity
The normal-state ratio is incomplete when the service requirement includes a spine or link outage. If f equal-capacity spines are unavailable and every surviving leaf-to-spine link remains usable, the remaining uplink bandwidth per leaf is:
Udegraded = (S − f) × k × V
The degraded downlink-to-uplink ratio is D ÷ Udegraded. If individual links rather than complete spines are unavailable, count the actual surviving links on each leaf; do not average the loss across the fabric.
In the example below, one unavailable spine leaves 300 Gb/s of uplink capacity per leaf, so the arithmetic ratio changes from 3:1 to 4:1. The installed inter-switch link count remains 64, but only 48 of those links are available in that failure state. Juniper illustrates the same capacity principle: losing one of four spines reduces aggregate fabric bandwidth by one quarter, while losing one of two halves it.
This calculation is a capacity screen, not a performance guarantee. ECMP hashing, flow size, traffic concentration, queueing, routing convergence and the actual failure mode can produce a different application result. Validate those factors in the network design and test plan.
Worked example
Assume 16 leaves, 4 spines, one 100G link per leaf-spine pair, and 48 × 25G server-facing ports on each leaf. Each leaf has 1.2 Tb/s of downlink bandwidth, 400 Gb/s of uplink bandwidth and a 3:1 downlink-to-uplink ratio. The fabric requires 64 inter-switch links and 16 leaf-facing ports on each spine. Cisco uses the same aggregate-bandwidth method in its oversubscription example.
If each spine has 64 ports available for the fabric and k = 1, the port formula permits up to 64 leaves before reserved ports, platform limits and other design constraints are applied. Whether a 3:1 ratio is acceptable is a traffic-design decision; it is not a universal cabling target.
Create a link matrix with one row per link class before any trunk is selected. At minimum, record the two endpoint groups, quantity, speed, k, expected port mode, route and change domain. This matrix is the controlled data behind a spine-leaf cabling diagram and the final BOM.
The worked example proves only a small set of design facts:
| Proven by the inputs | Still unresolved before procurement |
|---|---|
| 64 leaf-to-spine links in the symmetric block | Exact transceiver part numbers and MDIs at both ends |
| 16 leaf-facing fabric ports on each spine | Direct cords, structured trunks, cassettes or mapped modules |
| 3:1 normal-state arithmetic ratio | Fiber category, active positions, connector presentation and polarity |
| 4:1 arithmetic ratio with one of four equal-capacity spines unavailable | Route lengths, mated pairs, loss limits, labels and acceptance records |
It is therefore incorrect to turn 64 links into 64 MPO trunks without the missing interface, route and channel decisions.
Map each link class to the exact transceiver MDI
Which connector does a spine-leaf link need?
A speed label cannot select a connector. Different PMDs at the same nominal speed can use different MDIs, fiber types, lane counts and reaches.
These Cisco modules show the problem. They are examples, not a universal compatibility list:
| Link example | Documented equipment-side MDI | Fiber implication | Design lesson |
|---|---|---|---|
| QSFP-100G-SR4-S | MPO-12 over multimode fiber | Parallel MMF; the cited sheet lists up to 70 m on OM3 and 100 m on OM4 | A 100G SR4 example can require MPO-12. Cisco 100G data sheet |
| QSFP-100G-DR-S | LC over single-mode fiber | Duplex SMF | A 100G DR example can use LC, so 100G does not imply MPO. Cisco 100G data sheet |
| QSFP-400G-DR4 | MPO-12 APC over parallel SMF | Four parallel optical lanes | This 400G DR4 example is not interchangeable with an LC channel. Cisco 400G data sheet |
| QSFP-400G-FR4 | Duplex LC UPC over SMF | Wavelength-multiplexed duplex path | This 400G FR4 example disproves a universal 400G-MPO rule. Cisco 400G data sheet |
| OSFP-800G-DR8 | Two MPO-12 APC interfaces over SMF | Two parallel connector groups | The connector layout must be read from the exact SKU. Cisco 800G data sheet |
| OSFP-800G-DR8P | One MPO-16 APC interface over SMF | One 16-fiber parallel interface | Even within an 800G DR8 family, the MDI can differ. Cisco 800G data sheet |
For each endpoint, capture the exact part number, current data-sheet revision, host port mode, native or breakout state, fiber category, connector geometry, polish, reach and supported channel loss. Repeat the check at both ends; similar marketing names do not prove interoperability.
IEC 61754-7-1 covers one-row MPO interface dimensions, while IEC 61754-7-2 covers two-row MPO interface dimensions. These standards define interface geometry; they do not select a project assembly or prove channel performance. See the public scopes for IEC 61754-7-1 and IEC 61754-7-2.
MDI review checkpoint: Have the optics but not the cable mapping? Send both endpoint part numbers, data-sheet revisions, port modes and the intended native or breakout state. BWNFiber can review whether the input set is complete enough for a project-specific assembly discussion; the current manufacturer documents and approved channel plan remain the technical authority.
Choose the physical cabling architecture
Direct links or structured MPO trunks?
Within a broader data center fiber connectivity plan, choose the physical path only after each link class has a known MDI. The route must fit the room, rack and operating model.
| Architecture | Best fit | Advantages | Design checks |
|---|---|---|---|
| Direct equipment cord | Short, stable, point-to-point route | Few mated pairs and simple initial BOM | Pathway congestion, service loops, reach, bend control and moves/adds/changes |
| MPO trunk with pass-through patch fields | Repeated rack-to-row or row-to-row routes | Separates permanent pathway from equipment cords | Fiber count, connector presentation, polarity, mate count, loss and spare allocation |
| MPO-to-LC cassette | High-count backbone feeding duplex-LC equipment | Concentrates backbone fibers while presenting duplex ports | Cassette mapping, port labels, module loss, polarity and upgrade restrictions |
| Mapped mesh or shuffle module | Repeated many-to-many mapping that the module is designed to implement | Can reduce field patching for a defined pattern | Exact mapping, failure domain, replacement strategy, vendor drawing and migration effect |
There is no evidence-based rule that a main distribution area becomes mandatory after a particular rack count. Corning compares patch-cord and optical-mesh approaches in its spine-and-leaf cabling discussion, while CommScope provides a broader fabric-network design guide. Use such architectures as design references, then test them against the actual pathway, operations plan and equipment interfaces.
ISO/IEC 11801-5 defines generic cabling within and to data-centre computer-room spaces, and TIA identifies TIA-942-C as its current data-center infrastructure revision. ANSI/TIA-568.3-E addresses premises optical-fiber cabling and components. Their public scopes help frame the facility design, but they do not choose a connector or route for a specific switch pair. Review the ISO/IEC 11801-5 scope, TIA-942-C overview and TIA-568.3-E announcement alongside the project's contractual and local requirements.
For MPO route details such as fiber count, panel presentation, cassette choice and loss allocation, continue to the MPO trunk cable design guide. When the design calls for a direct duplex equipment cord, use the fiber optic patch cord selection page to define both interfaces, fiber grade, polish, jacket and length.
Specify fiber, cable construction and pathway conditions
How should OS2, OM3, OM4 and OM5 be specified?
Record the transceiver-supported medium, cabled-fiber category and assembly construction as separate fields. The exact PMD data sheet governs the acceptable medium and reach. On the cited Cisco sheet, QSFP-100G-SR4-S is listed for up to 70 m on OM3 and 100 m on OM4; the same cabling table lists OM5 at 100 m. This example does not establish that OM5 extends every short-reach application. IEC 60793-2-10 defines OM3, OM4 and OM5 as standardized 50/125-micrometre multimode categories, while the equipment specification sets the application-specific reach and channel conditions.
For single-mode links, do not treat OS2, G.652.D and G.657.A1/A2 as interchangeable labels. OS2 is a cabled-fiber category, while the ITU-T designations describe single-mode fiber characteristics. The cited Cisco 100G DR example specifies standard G.652 single-mode fiber. ITU-T G.652 covers conventional single-mode fiber and cable, while ITU-T G.657 covers bending-loss-insensitive single-mode fiber and states that its Category A fibers are compatible with G.652.D. If a supplier proposes G.657.A1 or G.657.A2, record the exact category and confirm it against the cable and optics requirements. Bend-insensitive fiber does not waive the assembly manufacturer's minimum bend-radius limits.
Which physical cable parameters belong in the schedule?
| Specification input | What to record | Decision boundary |
|---|---|---|
| Fiber count | Active transmit/receive positions, unused positions, allocated spares and breakout allocation | Connector position count is not the same as active fiber count; derive both from the lane map |
| Cable construction | Approved assembly design, termination method and any ribbon, loose-tube, tight-buffered or breakout elements named in the product data sheet | Construction terms do not select the transceiver MDI or prove installation suitability |
| Bend radius | Minimum installation and long-term bend radii for the exact assembly | Do not copy a generic multiple of cable diameter or infer the limit from G.657 alone |
| Tensile and crush limits | Rated installation load, long-term load where applicable, crush limit and approved pulling method | Use the exact cable data sheet and route plan; a standards test method does not supply the product rating |
| Jacket and fire requirements | Jacket material, required fire classification, indoor/outdoor transition and contractual or local-code reference | LSZH, flame performance, plenum/riser classification, PE jacket, UV resistance, water blocking and rodent protection are separate claims |
| Length and handling | Approved route length, measurement method, service-loop rule, pulling path, reel or packaging limits and connector protection | A floor-plan estimate is not an installed-route measurement |
IEC 60794-1-1:2023 establishes generic property families for optical fiber cables. Separate documents define methods such as IEC 60794-1-101:2024 tensile testing and IEC 60794-1-111:2023 cable bending. These are test methods, not proof of the ratings for a proposed assembly. Require its current data sheet or approved drawing.
Do not reuse jacket or fire-language from a project in another country without review. Record the site country, room or pathway classification, route boundary, applicable authority and contract requirements. If a route leaves controlled data-center space, treat aerial, duct, direct-burial, armored, water, UV and rodent requirements as a separate outside-plant design scope. ADSS and FTTH drop cable choices do not follow from the spine-leaf topology.
At receipt, match the part number, length, connector presentation, labels and packaging condition to the approved schedule before installation. During installation, protect connector end faces and stay within the documented pulling, crush and bend limits. After changes, update the channel map and as-built record instead of treating the original drawing as current.
Add international procurement requirements to the schedule
Country name alone does not select the jacket, fire classification, certification set or shipping term. Add a regional compliance and logistics annex to the same controlled cable schedule, and have the buyer, designer, local authority or consultant identify the applicable requirements before quotation.
| Project region | Confirm before quotation | Do not assume |
|---|---|---|
| North America | Project jurisdiction and authority having jurisdiction, room and pathway classification, contractually required TIA or other standards, delivery point and importer responsibilities | That every indoor route needs the same plenum or riser listing |
| Europe | Destination country, applicable construction-product and fire-performance requirements, required Declaration of Performance or CE documentation where the product and application fall within scope, document language and delivery point | That LSZH by itself proves a required fire classification or regulatory status |
| Middle East | Country and city authority, consultant specification, indoor/outdoor boundary, storage and handling conditions, import documents and delivery responsibility | That one Gulf-country requirement applies across the region |
| Southeast Asia | National building, telecom and fire requirements, humidity and storage controls, site labeling language, multi-site packing and customs responsibility | That a specification accepted in one country is accepted in another |
| Latin America | Destination-country rules, Spanish or Portuguese document needs, importer-of-record responsibilities, customs data, site spares and delivery point | That a regional label replaces country-specific approval |
| Africa | Country and local authority, route environment, storage and last-mile handling, document language, site-spares plan and customs responsibility | That climate or logistics conditions are uniform across countries or sites |
For an EU project, request the applicable product documentation rather than adding CE or CPR compliant to an RFQ as a generic checkbox. The European Commission explains that a Declaration of Performance and CE marking apply when a construction product is covered by a harmonised European standard or has a European Technical Assessment. The exact product, intended use and current legal transition therefore need review. See the Commission's construction-product declaration and marking guidance.
Keep the commercial delivery basis separate from production lead time. State the selected Incoterms® 2020 rule and named place, who handles export and import clearance, the shipping method, the point at which delivery and risk transfer, and which taxes, duties, insurance or destination charges are included. ICC's Incoterms® 2020 buyer checklist shows why the rule and the delivery point must be selected together; it is not evidence of a BWNFiber delivery offer.
Define export packing by the assembly and route risk: connector protection, bend control, moisture protection where required, carton or reel identification, package-level route IDs and a packing list that reconciles to the cable schedule. If raw-wood pallets, cases, cable drums or spools are used in an international shipment, confirm applicable ISPM 15 treatment and marking with the logistics parties; the IPPC standard expressly includes those forms of wood packaging. Processed-wood exemptions and destination-country controls must be checked rather than inferred.
For schedule planning, separate engineering and drawing approval, sample or first-article approval if required, production, export handling, transit, customs and site receipt. Ask the supplier to quote each applicable stage and dependency in writing; do not convert a general website statement into a delivery commitment.
This regional annex is for data-center switch-fabric channels. If the requirement is an ISP access network, FTTH drop, ADSS aerial route, duct route or direct-burial plant, use the relevant access or outside-plant design page and a separate environmental specification. Those cable choices do not follow from a spine-leaf topology.
Build the channel map before the BOM
Set polarity from the end-to-end channel map. A cable type alone cannot describe the complete path. The map should show:
- the exact transmitter and receiver lane assignments at both modules;
- every equipment cord, adapter, cassette, trunk, splice or mapping module;
- connector row count, pinning, key orientation and polish at every interface;
- fiber positions through each passive component;
- final Tx-to-Rx continuity for native and breakout modes;
- the insertion-loss budget and approved engineering margin;
- the owner, revision and approval state of the drawing.
Approve the trunk method and component mapping after the complete path has been checked. A site-wide instruction such as "use Type B everywhere" is insufficient because equipment cords, cassettes, transition modules and breakout mappings can change the result.
Use the MPO polarity checklist to record the full route. If any component drawing or endpoint lane map is missing, keep that link class on engineering hold.
Treat 400G-to-800G migration as a compatibility review
An "OS2" or "MPO-16-ready" label does not guarantee that an installed route can move from 400G to 800G unchanged. Reuse requires compatibility in each area below:
- equipment-side MDI and connector presentation;
- fiber category, fiber count and lane allocation;
- end-to-end mapping and polarity;
- route length, mated pairs, loss budget and engineering margin;
- native versus breakout behavior;
- patch-panel, cassette and adapter interfaces;
- operational rules for spares, maintenance and fault isolation.
| Migration case | Reuse decision |
|---|---|
| 100G SR4 multimode route to a 100G DR single-mode module | Not direct reuse: the example MDIs and fiber media differ. Compare the exact module data sheets and redesign the channel. |
| Direct 400G DR4 parallel route to an 800G DR8 interface | Do not assume reuse: the lane and interface requirement changes. A higher-count backbone may be reusable only if its allocated fibers, connector presentation, mapping, reach and loss all pass review. |
| 400G FR4 duplex-LC route to a future 800G link | Reuse is possible only if the selected future modules explicitly support a compatible duplex interface and the existing channel meets their optical requirements. |
| MPO-16-capable panel installed in advance | The panel is one component, not a migration guarantee. Trunks, modules, cassettes, adapters, patch cords and lane mapping must also be compatible. |
Record the current-state and future-state MDIs side by side. Mark each passive component as reusable, replaceable or unresolved, and record the source for that decision. Treat "future-ready" as unproven until every required component passes this review.
Turn the design into a trunk and patching schedule
What should a spine-leaf cabling RFQ include?
Build the cable schedule from the approved design inputs. Use one row for each repeatable link class or unique route and include:
| Field group | Required fields |
|---|---|
| Control | Project, schedule ID, revision, status, author, approver and issue date |
| Endpoints | Leaf/spine IDs, rack/U positions, source/destination ports and equipment roles |
| Optics | Manufacturer, exact part numbers, data-sheet revisions, port modes and breakout state |
| Channel | Fiber category, allocated fibers, endpoint MDI, connector/polish/key/pin details and lane-map drawing ID |
| Route | Origin/destination panels, pathway segments, measured or approved design length, service-loop rule and fire-rating requirement |
| Components | Equipment cords, trunks, cassettes/modules, adapters, splices and quantities |
| Performance | Module channel limit, component loss assumptions, calculated total, margin and acceptance method |
| Operations | Label format, color conventions, spare-fiber rule, test-record ID and change-control owner |
Aggregate routes into a trunk after the schedule confirms compatible fiber positions, connector presentation and change domains. A label such as "400G trunk" cannot describe mixed MDIs.
Issue the link matrix, route drawing, channel map, trunk/patch schedule and evidence references with the RFQ. State the transceiver interface and polarity method instead of asking a supplier to infer them from a cable description.
What documents should buyers request?
Request documents for the exact proposed configuration, not a generic company pack. The supplier should also state which records are included in the quotation, which are available only after approval or production, and which do not apply.
| Document or record | What it should establish | Hold condition |
|---|---|---|
| Current model data sheet | Exact fiber, interface, construction and applicable ratings for the proposed item | Only a family page, expired sheet or unversioned summary is supplied |
| Controlled drawing or part-number definition | End A/end B, connector presentation, polish, pinning, length, breakout, labels and channel map | The quoted part cannot be traced to the cable schedule |
| Quotation and deviation schedule | Schedule revision, quantity basis, commercial assumptions, exclusions and substitutions | A price is returned without identifying what changed or was excluded |
| Sample or first-article plan | Configuration, checks, approval record and the production scope it controls | A sample is offered without defined acceptance criteria or revision linkage |
| Inspection and test-deliverable plan | Applicable methods, limits, wavelengths, report format and link or assembly traceability | The quotation says only tested or presents a generic certificate as product evidence |
| Packing, labeling and as-built plan | Route IDs, package contents, label format and final record handoff | Receiving and installation teams cannot relate shipped items to the approved schedule |
Specification-document checkpoint: Once a proposed item is identified, request its current data sheet and controlled drawing before approval. A family brochure or generic downloadable checklist is not approval evidence for the quoted configuration.
Use the fiber cable assemblies selection and RFQ page to identify an applicable assembly family; keep this spine-leaf guide as the owner of the fabric-to-schedule calculation.
Compare price, MOQ and lead time on the same revision
Two quotations are not comparable when they use different connector presentations, route lengths, accessory scope or test records. Ask each bidder to identify the schedule revision used, exclusions, substitutions, quantity basis and proposed deliverables. Resolve those differences before comparing price, MOQ or lead time.
Treat price, minimum order, sample timing, production lead time and delivery date as project quotation fields, not facts that can be copied from a general web page. Give every bidder the same requested quantity and delivery point, then ask for:
- currency, tax basis, delivery term and quotation-validity date;
- unit and extended price at the stated quantity, plus any quantity break or MOQ for that exact configuration;
- separate engineering, tooling, sample, testing, packing or expedite charges where applicable;
- the event that starts the production clock, such as drawing, sample or commercial approval;
- production lead time, shipping method, estimated transit scope and the requested delivery date;
- component-availability assumptions, approved alternatives and the process for schedule changes.
An unsupported delivery-speed claim is not a project schedule. Commercial review passes only when the technical baseline, approval events, destination and inclusions are explicit in the quotation.
Compare installed cost, not a bare cable price
Use the same approved design basis to compare total installed cost. Do not award the project from an assembly unit price while other scope is hidden.
| Cost or risk bucket | Put the same scope in every bid |
|---|---|
| Active and passive connectivity | Optics or AOC/DAC scope, equipment cords, trunks, cassettes or mapping modules, adapters and spares |
| Space and pathway | Panel and enclosure capacity, rack units, pathway fill, service loops and route segregation |
| Installation | Pulling and placement method, connector protection, labeling, inspection and patching |
| Acceptance | Required test methods, reference cords, directions, wavelengths, records and retest responsibility |
| Change and recovery | Approved substitutions, spare strategy, replacement mapping, as-built updates and disposition of failures |
A design with fewer components can reduce mate count but may be harder to reconfigure. A structured route can add interfaces and rack space but may simplify controlled changes. Price those tradeoffs against the approved operating model and loss budget.
Score supplier evidence before commercial comparison
Use a pass/hold review before scoring price. A low quotation is not comparable if it omits the information needed to prove the same channel.
| Review item | Pass evidence | Hold condition |
|---|---|---|
| Schedule conformity | Bid identifies the exact schedule ID and revision and answers every required field | Supplier quoted from a generic description or an obsolete revision |
| Interface and mapping | Controlled drawing shows connectors, polish, keying/pinning, fiber positions and end-to-end mapping | Mapping is described only as a cable type or marketing name |
| Substitution control | Each proposed substitution is identified and approved before production | Supplier reserves the right to substitute an unspecified component |
| First-article control | Custom configuration is tied to a sample or first article and its approved records | A sample is offered without revision traceability or defined checks |
| Test and inspection records | Deliverables, methods and channel IDs match the acceptance plan | Tested is stated without method, limit, record format or traceability |
| Labels and as-built data | Label format and final schedule update are included | Labels, route IDs or final records are excluded |
| Deviations and retest | Nonconformance, disposition and retest ownership are stated | Failures can be accepted or reworked without a controlled record |
This scorecard evaluates quotation completeness, not a supplier's unverified factory capability. Validate any claimed certification, product rating, test capability, minimum order, lead time or compatibility with current first-party evidence before it enters the approved bid comparison.
When should buyers ask for a customized cable design?
Ask for a custom review when the approved link cannot be represented by a current catalog configuration: for example, when the channel needs a controlled breakout, non-standard end presentation, project length and tolerance, pulling protection, route-specific labels, a defined panel map or project-specific packing. Customization should resolve a documented requirement, not hide an incomplete MDI or route decision.
If OEM/ODM, private-label marking or packaging is part of the commercial program, put those items on a separate controlled schedule. Confirm feasibility, ownership of drawings or artwork, sample requirements, cost and timing in the quotation. None of those commercial options changes the need to validate the optical channel.
Approve non-standard assemblies before volume production
For a custom mapping, connector presentation, label scheme or unusual length, require a sample or first article tied to the approved schedule revision. Verify the connector, pinning, polish, length, labels, lane map and agreed inspection or optical records before authorizing the production quantity. A passed sample approves that configuration only; it does not prove compatibility with other modules or channels.
If a sample is required, say so in the inquiry and define the configuration, quantity, checks and approval owner. Ask the supplier to confirm sample feasibility, cost, timing and its effect on the production schedule in writing. Do not describe a sample as free, available or fast unless the current quotation says so.
Move from inquiry to purchase release
A technically complete inquiry is the start of controlled project communication, not permission to manufacture. Use this sequence:
- Submit the controlled link matrix, route drawing, optics evidence, schedule and acceptance requirements.
- Require the supplier to return the proposed part definition, applicable documents, commercial scope and a deviation list.
- Close every technical hold with the responsible network, facilities or cabling owner; do not let a sales email silently replace the schedule.
- Align price, quantity, MOQ if applicable, sample plan, production lead time, delivery basis and quotation validity against that same revision.
- Approve the sample or first article when the configuration risk warrants it, and record exactly what the approval covers.
- Reference the approved schedule, drawing and deviations in the purchase order; prohibit unapproved substitutions.
- At receipt and commissioning, reconcile labels, quantities, records and nonconformances to the approved purchase package.
Only then should the project move from inquiry to production release. Any later interface, route, quantity or acceptance change needs a new revision and a documented commercial impact review.
Label, inspect and commission against the approved plan
Give every permanent link and equipment cord a unique channel ID that traces back to the schedule revision. Record both ends, panel/port positions, route, component serial or lot identifiers when required, and the approved test record.
Inspection, insertion-loss measurement, return-loss measurement, polarity verification and OTDR analysis provide different evidence. IEC 61300-3-35:2022 covers visual inspection of fiber-optic connector end faces and states that inspection does not replace attenuation or return-loss measurement; see the IEC 61300-3-35 scope. IEC 61280-4-1:2019 covers attenuation measurement for installed multimode cabling, while IEC 61280-4-2:2024 covers attenuation and optical return loss for installed single-mode cabling. IEC 61280-4-5:2020 covers attenuation measurement and determination of polarity and length for installed cabling terminated with MPO and tested through MPO interfaces; its public scope is limited to MPO-to-MPO cabling, so do not apply it blindly to mixed-interface routes. See the IEC 61280-4-5 scope.
An OTDR trace can support event location, length and loss analysis when the approved method permits it. Do not treat that trace as interchangeable with a light-source-and-power-meter result, end-face inspection or polarity record. The acceptance plan must state the test method, directions, wavelengths, reference-cord method, instrument settings and limits for each link class.
The commissioning pack should contain:
- approved as-built link matrix and channel maps;
- visual-inspection records tied to channel IDs;
- polarity/mapping results for the applicable route;
- attenuation and other optical results required by the project;
- instrument, method and reference-cord details;
- deviations, dispositions and retest records;
- final BOM and installed schedule revision.
Acceptance limits must come from the optics, approved channel design, project requirements and applicable standards. A generic internet table cannot set project pass/fail limits. The MPO trunk installation guide provides an installation workflow that can be adapted to the project plan.
Common spine-leaf cabling specification failures
Block the release when the design contains any of these failures:
- treating every spine-leaf link as MPO without an endpoint MDI check;
- dividing spine-port capacity by the number of spines when calculating maximum leaves;
- ordering by speed label while omitting the exact transceiver part number and port mode;
- treating 100G DR like 100G SR4, or 400G FR4 like 400G DR4;
- stating that every 800G DR8 module has one MPO-16 interface;
- choosing Type B, a cassette or a mesh module before proving Tx-to-Rx continuity;
- promising trunk reuse from "OS2" or a "future-ready panel" alone;
- applying an MPO-to-MPO test method to a mixed-interface channel without checking scope;
- copying a generic bend radius, pull limit, jacket claim or fire rating into the schedule without exact assembly evidence;
- treating an OTDR trace, connector inspection or sample approval as proof of every other acceptance requirement;
- quoting unsupported product fiber counts, test deliverables, lead times or compatibility;
- releasing a BOM without a controlled channel map and acceptance plan.
Spine-leaf cabling FAQ
Does every spine-leaf link require MPO?
No. A spine-leaf topology defines the switch relationships. The exact transceiver MDI and physical route determine whether a link uses MPO, duplex LC, an AOC, a DAC or another interface.
How many cables are needed between leaf and spine switches?
For a symmetric full mesh, the inter-switch link count is L × S × k, where k is the number of physical links per leaf-spine pair. Add border, inter-pod, management, spare and out-of-band links separately.
How many leaf-facing ports does each spine need?
Each spine needs L × k leaf-facing ports. Use only ports actually available for the fabric after reservations.
How do you calculate leaf-spine oversubscription?
For one leaf, divide its aggregate downlink bandwidth by its aggregate uplink bandwidth. Keep the units and scope consistent, then validate the chosen ratio against the traffic model.
Is 100G DR normally an MPO link?
Not universally. The cited Cisco QSFP-100G-DR-S example uses LC over single-mode fiber, while its 100G SR4 example uses MPO-12 over multimode fiber. The exact SKU governs.
Does 400G always use MPO-12?
No. The cited Cisco portfolio includes a 400G DR4 example with MPO-12 APC and a 400G FR4 example with duplex LC UPC.
Does 800G DR8 always use MPO-16?
No. The cited Cisco OSFP examples include both dual-MPO-12 and single-MPO-16 DR8 interfaces. Confirm the exact module and operating mode.
Is Type B the right polarity for every spine-leaf trunk?
No universal type label is sufficient. Prove the complete channel, including equipment cords, adapters, cassettes or modules, and breakout mapping, from Tx to Rx.
Can a 400G cable plant be reused for 800G?
Possibly, but OS2 alone does not prove reuse. Check interface presentation, allocated fiber count, mapping, reach, mate count, loss budget and every passive component against the selected future modules.
What should be sent with a spine-leaf cabling RFQ?
Send the fabric/link matrix, exact optics list, rack and route drawing, channel map, schedule, performance assumptions, applicable requirements and acceptance plan. Clearly mark unresolved fields so they are closed before production.
When should direct equipment cords be used instead of MPO trunks?
Use direct cords for short, stable point-to-point routes when the endpoint MDIs match and the pathway can be managed without excessive congestion. Use a structured trunk route when repeated pathways, patch-field access or controlled moves/adds/changes justify the extra interfaces. Compare both options against the route, mate count, loss budget and operating model.
Which records should be delivered after spine-leaf cabling is installed?
Require the approved as-built link matrix, channel maps, endpoint and panel labels, applicable inspection and optical results, instrument/method records, deviations and the final BOM revision. Each record should trace to the same channel ID.
Which documents should be requested before placing an order?
Request the current model data sheet, controlled drawing or part-number definition, quotation and deviation schedule, applicable test-deliverable plan, labeling and packing plan, and any agreed sample record. Each document should identify the same approved configuration and revision.
How should buyers compare MOQ and lead time?
Compare them only after every bidder has the same technical baseline, quantity, approval sequence and delivery point. The quotation should state any configuration-specific MOQ, the event that starts production lead time, shipping scope, validity date, exclusions and component-availability assumptions.
When should a sample or first article be requested?
Use one when a non-standard mapping, connector presentation, length, label, pulling arrangement or packing requirement creates material order risk. Define the checks and approval owner first; the sample approves only the configuration and revision that were evaluated.
Does the destination country determine the cable jacket or fire rating?
No. The destination is only one input. Confirm the exact room and pathway, indoor/outdoor boundary, authority or consultant requirements, intended product use and applicable classification before specifying a jacket or fire claim. LSZH, plenum, riser and a European fire classification are not interchangeable labels.
Is spine-leaf a full mesh?
It is fully connected between the two tiers in the conventional design: every leaf connects to every spine. It is not an all-to-all mesh among every switch; leaf-to-leaf and spine-to-spine links are not part of the basic symmetric block.
Is spine-leaf always better than a three-tier design?
No. Spine-leaf is a strong candidate for scale-out fabrics and repeated east-west traffic, but it adds links and operational requirements. Compare workload, scale, failure targets, routing skills, existing infrastructure and total installed cost before changing the topology.
Request a Spine-Leaf Cabling BOM Review
Use the Count → MDI → Route → Map → Release handoff when contacting BWNFiber. Send your leaf and spine counts, switch and transceiver part numbers, port modes, rack or row plan, route topology, link distances, project country and site requirements, quantity, delivery point, target schedule, required document languages and acceptance plan.
BWNFiber's public project-review process allows buyers to submit a BOM, topology, rack layout or transceiver list for review of key interfaces, fiber counts, polarity and loss requirements before quotation. For this project, the practical next output should be one of three things: a request for missing inputs, a proposed configuration with stated deviations, or an evidence-based quotation. Final compatibility, product ratings, sample availability, test deliverables, MOQ and lead time remain subject to the exact approved configuration and written offer.
Request a spine-leaf cabling BOM review, ask for the current applicable data sheet or drawing, or review the BWNFiber MPO cabling options after the link classes are defined. If a sample is part of your approval plan, include its configuration and acceptance checks in the same inquiry.
