OEM vs third-party optics comes down to three separate questions: will the module physically and optically work, will the switch software accept it, and what does the switch vendor say about support when it is installed. This guide separates what the vendors publish from what you should ask before buying.
The short answer
- A standards-compliant transceiver in the right form factor can interoperate optically with another compliant module. That does not guarantee the switch will accept it.
- Acceptance is decided by the host: its hardware, software release and any vendor checks it applies to the module's stored identity.
- Support positions are set by each switch vendor. Read them in the vendor's own documents, and ask the seller in writing what you are getting.
- Check compatibility against the exact switch model, uplink module and software release, not against the form factor.
What "coded for" means
A transceiver stores identification data that the host reads when it is inserted. A "coded" module is one whose stored data has been set to be recognised by a particular vendor's host. Cisco's 10-Gigabit Ethernet transceiver data sheet says its quality ID feature "enables a Cisco platform to identify whether the module is certified and tested by Cisco". That is the vendor describing the check; the data sheet does not describe the mechanism or what happens to a module that fails it.
Because the check is the host's, the same physical module can be accepted on one switch family and refused on another. Ask whoever supplies a coded module which host, which software release and which vendor it was coded for.
What the standards do and do not give you
| Layer | Who defines it | What it gives you |
|---|---|---|
| Form factor and electrical interface | Multi-source agreements (MSAs) such as SFF-8472 | A module that fits the cage and presents a common management interface |
| Optical specification | IEEE 802.3 (for example 10GBASE-SR, 100GBASE-LR4) | Two compliant modules of the same type can talk to each other |
| Host acceptance | The switch vendor's software | Whether the port comes up, is disabled, or shows a warning |
Arista's 100G optics FAQ states that Arista 100G transceivers are fully interoperable with other 100G transceivers "as long as the non-Arista 100G transceivers meet the associated industry standard specifications". That is an optical interoperability statement. Non-standard types, such as 100G BiDi and SWDM4 variants, are called out in the same FAQ as not interoperating with each other, so match the type at both ends.
What each vendor publishes about third-party optics
Cisco. Cisco's Optics-to-Device Compatibility Matrix is the tool for checking which Cisco optics are supported on which devices; it is an interactive page and we have not reproduced its contents here. Two Cisco documents we read state positions for specific products: the Cisco MDS 9700 hardware guide says "Cisco TAC does not support switch ports populated with non-Cisco SFP+ transceivers", and the Embedded Service 9300 configuration guide says to replace a non-Cisco SFP with a Cisco module when troubleshooting. Neither is a statement about every Cisco product. We did not find a Cisco document describing the service unsupported-transceiver command, so we do not describe it here; check the configuration guide for your platform and release.
Juniper. Juniper's transceiver compatibility documentation says JTAC "provides complete support for Juniper-supplied optical modules and cables" and "does not provide support for third-party optical modules and cables". It adds that JTAC may still help diagnose host issues and may ask you to replace the third-party module, and that damage to the host from third-party modules is the user's responsibility. Its Hardware Compatibility Tool lists the transceivers a device supports.
Arista. The FAQ above states optical interoperability with standards-compliant modules, and says Arista does not restrict third-party passive copper cables provided they meet the IEEE and SFF-8636 specifications; unrecognised cables leave the interface disabled. We did not find a published Arista support policy for third-party optics in the documents we read, so put that question to Arista.
DOM and monitoring
Digital optical monitoring (DOM) reports optical power, temperature, bias current and supply voltage. Cisco's Gigabit Ethernet SFP data sheet says DOM follows the SFF-8472 MSA and marks some part numbers with DOM and others without, for example GLC-SX-MMD and GLC-LH-SMD. Juniper's page points to show interfaces diagnostics optics to see whether a transceiver supports monitoring. Do not assume a lower-cost module has DOM; ask.
How to check an exact switch and release
- Record the switch model, any uplink or network module, and the running software release.
- Look up each optic in the vendor matrix or tool (Cisco's matrix, Juniper's Hardware Compatibility Tool, Arista's transceiver guide) for that device and release.
- Match the speed, fibre type, reach and wavelength, then the connector. See single-mode vs multimode fibre and SFP vs SFP+ vs SFP28.
- For a coded third-party module, get the coding target in writing.
- Keep a vendor-branded spare for fault isolation.
Examples of common Cisco 10G and 25G parts: SFP-10G-SR, SFP-10G-LR, SFP-25G-SR-S, QSFP-100G-SR4-S. For Juniper: JNP-QSFP-100G-SR4.
Common mistakes
- Treating "MSA compliant" as "accepted by the switch".
- Checking the part number but not the software release.
- Assuming a Cisco-branded optic is supported on every Cisco platform; Cisco's matrix is per device.
- Mixing 100G BiDi, SWDM4 and SR4 at the two ends of a link.
- Not asking whether a module has DOM.
- Assuming a support contract covers a third-party module without reading the vendor's own terms.
FAQ
Will a third-party SFP+ work in my switch?
It depends on the host's acceptance check and release. Check the vendor matrix and ask the seller what the module is coded for.
Is third-party optics use supported by the switch vendor?
Read the vendor's documents. Juniper publishes that JTAC does not support third-party optics; Cisco publishes product-specific statements such as the MDS 9700 one above. For anything else, ask the vendor.
Do your optics come with vendor support?
We do not promise warranty or support entitlement on optics. Confirm terms with the vendor and in your quote.
What to include in your quote request
- Switch or router model, uplink module, software release
- Speed and standard (for example 10GBASE-SR, 25GBASE-SR, 100GBASE-LR4)
- Fibre type, distance and connector at both ends
- Whether DOM is required
- OEM or third-party, and for third-party, the host it must be coded for
- Quantity, and whether spares are needed
Send the details through our quote request form.
Tool: check a switch model in the optics compatibility lookup to see which optics we sell for it, and the evidence behind each verdict.