The value of third-party optics is direct: for the same link, compatible modules cost far less than OEM, and in most cases the feature is enough. But they are also the component in the network easiest to buy on a wrong glance — form factor right, speed right, still unable to link, because of coding and the setup at both ends.
“100% compatible” is not a spec; it is a result to verify
Many market pages write phrases like “100% OEM Compatible” or “Triple-Tested”; we do not. The reason is simple: compatibility is not a property of the module alone, but the combined result of module + your device + your firmware version + both-end setup.
What we can commit to is the method: pair coding to your model and version, test the link before dispatch, and state up front what is not guaranteed. What we cannot do — for example, a firmware release that simply raises a warning — we say directly that we cannot do it.
Choosing a module comes down to four variables
Form factor
- SFP: 1G, the most common access and copper-cable alternative.
- SFP+／SFP28: 10G／25G, switch uplinks and server access.
- QSFP+／QSFP28: 40G／100G, four lanes in parallel.
- QSFP-DD／OSFP: 200G／400G and above, eight lanes, used in rooms and AI clusters.
- Legacy form factors: GBIC, XENPAK, X2, XFP still appear on older gear; these models are mostly end-of-life, supply depends on the specific case.
Form factor decides whether it “fits in”, not whether it “passes through”.
Speed and lane structure
40G is 4×10G, 100G is 4×25G, 400G is 8×50G. On the same QSFP28 link, both ends must match speed and lane allocation; a 40G module into a 100G port usually does not auto-downspeed on most platforms — it simply will not link.
Reach and fibre type
- Multimode (OM3／OM4): short reach, SR class, nominally 100–150 m class.
- Single-mode (OS2): LR／ER／ZR class, 10 km to 80 km class.
- Connectors: LC mainly; 40G／100G often use MPO／MTP multi-fibre.
Reach is a “nominal upper limit”; in practice it depends on your fibre grade, connector loss and cleanliness. Older OM1／OM2 are often a bottleneck at multimode high speed; swapping the module does not fix that case.
Coding
OEM switches read the vendor identity and model fields in the module EEPROM; that is coding. The same hardware, written with different vendor identity, becomes a “Cisco version” or “Juniper version”. Different platforms read slightly different fields, so one module type usually needs several coding versions on hand.
This also explains a common misunderstanding: “this module links in room A but not room B” is not a dead module; the coding or port setup is wrong.
Five problems you actually run into
Link will not come up
Most common; usually four causes: wrong coding, speed／lane mismatch at both ends, wrong fibre type or connector, or the port set to a fixed speed. Troubleshooting should start from setup, not by swapping modules first.
Flagged non-OEM after a firmware update
Some platforms warn on non-OEM modules, restrict features, or even refuse to enable them after a firmware update. We do not commit to compatibility with every firmware combination; if your environment upgrades on a schedule, tell us the version first — this is one of the most important inputs to selection.
DDM readings are off
DDM／DOM is the mechanism by which the module reports temperature, voltage and Tx／Rx optical power. Low-price modules sometimes skip calibration; readings are reference only. If you rely on DDM for monitoring or alert thresholds, say so when requesting the quote; we explain that model’s actual capability.
FEC and speed negotiation
For 100G DR4／FR4／LR4 class, RS-FEC usually must be enabled at both ends to be stable; SR4 mostly does not need it. FEC is not the module’s own decision — the two devices must agree; one side on and the other off gives the hardest-to-trace state of “linked but unstable”.
BiDi and wavelength pairing
Single-fibre bidirectional (BiDi) needs paired wavelengths: for example one side transmits 1270／receives 1330, the other end must be the reverse. CWDM／DWDM must match wavelength and mux／OADM channel. This class of error usually shows as “one fibre works, one does not”, not a total failure.
How we deliver a compatible module (six steps)
- Confirm the port: read your device’s interface type, speed and existing setup, not only the model on the procurement list.
- Pair coding: write the matching identity by brand and platform; if one batch spans devices of different brands, mark them separately.
- Bench power-on: insert into a same-type or same-platform test port and confirm it is identified correctly.
- Live link test: connect to a same-speed port, check link state, errors and FEC counters, not just the light.
- DDM check: temperature, voltage and Tx／Rx power within reasonable range; pick out the abnormal ones.
- Pre-dispatch recheck and packing: per-module label, anti-static bag, batch recorded by serial, so you can reconcile later.
Step 4 is the key. A lit light does not mean a stable link, especially at 100G and long-reach single-mode.
Warranty: one year, not Lifetime
- Compatible optics carry a one-year warranty; the start date is written on the quote.
- We do not offer Lifetime warranty. For third-party modules, “lifetime” refers to the decade after the module goes out of production, not today’s batch; writing it down does not mean delivering it.
- The warranty covers functional failure of the module itself; unavailability caused by firmware policy change, coding mismatch or setup error is a compatibility issue, not a warranty case. We state this up front to avoid later dispute.
- Host gear (switches, routers) warranty is separate: new gear under OEM warranty; used and refurbished gear generally 3–6 months. Detail in the terms of service.
OEM vs compatible: how to choose
| Comparison | OEM module | Compatible module |
|---|---|---|
| Compatibility certainty | Same brand and model, highest | Decided by coding and live test; confirmed batch by batch |
| Cost | High | Relatively lower |
| Warranty | Per OEM terms | One year |
| Management and alerts | Complete, usually no non-OEM notice | Depends on platform; notice or restriction may appear |
| Special features | Complete | Some features (specific encryption, timing, management traits) not guaranteed |
| Best fit | Core links, zero-tolerance alerts | Expansion, lab, branches, budget-sensitive bulk ports |
A common practice in practice is a mix: OEM on core and external links, compatible elsewhere, and marked in monitoring. It is not a choice between “save money” and “stable”; it is allocated by link importance.
DAC and AOC: short reach does not always need optics
For 10G／25G／100G interconnect within the same rack, DAC (copper cable) or AOC (active optical cable) is usually simpler than optics plus fibre: no pairing, no cleaning, plug and use. Reach is generally a few to a dozen-plus metres, depending on the chosen model. Optics come back in for cross-rack, cross-floor or long reach.
If your procurement list has both in-rack and cross-room links, list them separately and it saves many rounds.
Information to provide for a quote
- Device model and firmware version (most important; it directly affects coding and compatibility judgement).
- Port type and speed (1G／10G／25G／40G／100G／400G).
- Reach and fibre type (OM3／OM4／OS2), and connector (LC／MPO).
- Single-mode or multimode; whether BiDi or CWDM／DWDM wavelength is needed.
- Whether DDM／DOM monitoring is required, and reading accuracy needs.
- Whether FEC must be enabled at both ends, and the existing setup.
- Quantity, lead time and delivery location (Hong Kong／Greater Bay Area).
The more accurate the information, the fewer rounds. Writing only “need 10G SFP” means we ask one round before we can quote.
Packing, labels and batch management
What goes wrong most in bulk procurement is not the modules but mismatch: one box mixes different coding and wavelengths, discovered only at racking. Our dispatch labels each module (model, speed, reach, coding brand) and records batches by serial, so you can check on receipt and swap／repair later. Skip this step and the time saved is paid back in the room.
Next step
How to write selection and procurement terms is in the compatible optics selection guide. For a quote, email the seven items above to [email protected]. If you only want to confirm whether one model works, write in directly — we reply “this combination we have verified” or “this combination is not recommended”.
Warranty and compatibility: compatible optics carry a one-year warranty; no Lifetime warranty. Warranty covers module functional failure; unavailability caused by firmware policy, coding mismatch or setup error is a compatibility issue, not a warranty case. Host gear warranty is separate: new gear under OEM warranty; used and refurbished gear generally 3–6 months.