Account
Key takeaways
- Per-unit optics price times hundreds of ports is usually the biggest line item buyers underestimate in a buildout.
- Coding on an optic must match what the switch accepts, so the code required belongs in the quote itself.
- Both ends of a link and the fiber type must match, or the link will not come up at the intended reach.
- DACs and AOCs suit in-rack and short runs; optics suit longer, cross-row, and cross-building links.
- The Transceivers category holds 470 parts at 542,629 units; technology slices are counted separately.
Why does volume optics buying blow past the budget people plan for?
A single transceiver looks like a small line item. Multiply it by the port count in a buildout, both ends of every link, plus a spare pool, and optics can become one of the largest single categories in the bill of materials, often larger than the switches they plug into.
The miscalculation is usually counting ports instead of links, and links instead of transceivers. A single link between two switches needs two transceivers (or one DAC or AOC), and a cross-connect fabric multiplies that by every row and every redundant path.
Pricing the buildout by transceiver count, not by switch count, is the difference between a budget that holds and one that runs out halfway through the rollout.
What does "coded" versus MSA-compliant mean, and why must the code go in the quote?
Many switch vendors program their optics with a vendor code that the switch firmware checks before it will bring the port up, or before it will do so without a warning. An optic can be electrically equivalent to the OEM part and still be rejected, or flagged, if it lacks that code.
MSA-compliant means the optic follows the multi-source agreement standard for its form factor and speed, which covers physical and electrical interoperability, but says nothing about whether a specific switch's firmware will accept it without a vendor code.
For a volume order, this means the switch make and model, and whether coding is required, has to be in the quote itself. Ordering hundreds of uncoded optics for a switch that checks for a code is a buildout-stopping mistake to catch after delivery. See the vendor coding and MSA guide.
How do I make sure both ends of a link and the fiber type match?
A link needs the same speed and, on most platforms, a compatible reach class on both ends; a 10G optic on one end and a 25G optic on the other will not link up. The fiber running between them has to match what each optic expects: single-mode fiber for single-mode optics, multi-mode for multi-mode.
Mixing multi-mode and single-mode optics on the same fiber type is a common cause of a link that fails to come up during a bulk rollout, and it is harder to catch across hundreds of runs than on a single test link.
Confirm the fiber plant type before ordering the optics, not after, since re-terminating fiber for a mismatched batch is far more expensive than getting the order right the first time.
SR or LR, single-mode or multi-mode: which reach class do I need?
SR (short reach) optics run on multi-mode fiber and are built for in-building, in-row distances; on most platforms that means up to a few hundred meters depending on the fiber grade. LR (long reach) optics run on single-mode fiber and reach several kilometers, which covers cross-building and cross-campus links.
The reach class you need depends on the physical distance and the fiber already in the ground or the conduit, not on the switch port speed. Buying LR everywhere "to be safe" costs more per unit for reach you are not using; buying SR everywhere fails on any run that exceeds its distance.
If you do not know the fiber type already installed, that is the first thing to confirm, since it determines which reach class of optic you can even use on that run.
DAC and AOC versus optics: which for in-rack and which for cross-row?
A DAC (direct attach copper cable) or AOC (active optical cable) combines the transceiver ends and the cable into one assembly. A DAC suits short in-rack runs, usually a few metres. An AOC carries the same one-part convenience much further, commonly tens of metres, which covers cross-rack and many cross-row links. Both trade flexibility for a lower cost per link and simpler inventory, one part instead of two transceivers plus a patch cable.
Optics plus separate fiber suit longer runs: cross-row, cross-room, or cross-building, where a fixed-length DAC or AOC would not reach, or would be wasteful to stock in every length a rack layout needs.
A buildout usually mixes both: DAC or AOC within and between adjacent racks, optics and fiber for the aggregation and core links that span more distance.
Why does a spare pool matter at scale?
At the scale of hundreds of optics, some will fail during burn-in or early operation, and a link that goes down because of a bad optic with no spare on hand can stall a rollout schedule that has nothing to do with the switch or the fiber.
A spare pool sized as a percentage of the deployed count, held in the same part numbers as the live deployment, means a failed optic is a quick swap instead of a re-quote and a wait. Build the spare quantity into the original volume order rather than as an afterthought.
What do I put in a volume optics quote?
Five things let a quote get answered in one pass: the switch make and model, the port type (form factor and speed), whether vendor coding is required and for which platform, the reach class you need, and the total quantity.
Current depth in the Transceivers category: 470 parts at 25 or more units, totaling 542,629 units. Counted separately by technology slice, 25G and 40G optics and adapters run 378 parts at 108,943 units, and 100G optics and adapters run 60 parts at 32,942 units. The two breakdowns are measured differently, so do not read one as a subset of the other.
Send the same five details through request a volume quote for both ends of the link if the two ends need different optics, and note the spare percentage you want included in the quantity.
Browse current listings: transceivers and network switches.
Frequently asked questions
What happens if I order the wrong code for my switch?
On most platforms, an uncoded or wrong-coded optic either fails to link or brings the port up with a vendor-mismatch warning, and some switch firmware blocks the port entirely. Confirm the switch make, model, and coding requirement before ordering at volume; a single wrong code multiplied by hundreds of units is expensive to unwind.
Can I mix optics from different vendors in the same buildout?
Usually, as long as each optic is coded correctly for the switch it plugs into and matches the fiber type and reach class of its link partner. Behavior varies by switch vendor and firmware version, so confirm compatibility for your specific platform rather than assuming any MSA-compliant optic will be accepted.
Do DACs and AOCs need a vendor code the same way optics do?
Yes, on most platforms a DAC or AOC is checked for a vendor code the same way a separate transceiver is, since the switch firmware reads the same identifying data from the cable's end. State the switch make and model in the quote the same way you would for optics.
What is the difference between single-mode and multi-mode fiber for a bulk order?
Single-mode fiber carries one light path and supports the longer reach classes (LR and beyond); multi-mode fiber supports multiple light paths over shorter distances (SR class). The optic and the fiber type must match, so confirm which fiber is already installed before ordering optics for a bulk rollout.
How many spare optics should I include in a volume order?
There is no fixed ratio that fits every deployment; it depends on your link count and how disruptive a failed optic would be to your schedule. Build a spare percentage into the same quote as the live deployment so the spares are the same part number and condition as what is already installed.