SFP & SFP+ transceiver compatibility: coding, vendor lock, and DOM
Why a 10G optic that fits doesn't always link, how vendor coding works, and how to run third-party SFPs in Cisco, Arista and Juniper.
Will a third-party SFP/SFP+ transceiver work in a Cisco, Arista or Juniper switch? Yes, in nearly all cases. An SFP/SFP+ module is an MSA-standard form factor, so any compliant optic is mechanically and electrically interchangeable. What varies is the vendor ID written into the module's EEPROM: a switch may warn or refuse to bring up an "unapproved" optic until the module is coded for that platform, or the platform is told to allow third-party optics. A correctly coded module links and reports DOM identically to the OEM part.
"It fits, so why won't it link?" is the most common transceiver question — and the answer is almost never the glass. It is the identity string in the module's EEPROM and the platform's policy toward it. Here is what actually governs a link, and how to satisfy each vendor.
What determines whether an SFP links?
Four things must line up. Only the last is vendor politics; the first three are physics:
- Form factor (MSA) — the module and the port cage must match: SFP, SFP+, SFP28, QSFP+, QSFP28 or QSFP-DD. All follow published Multi-Source Agreements, so any compliant module fits any compliant cage of the same type.
- Data rate — the port must support the module's rate. SFP+ ports commonly accept 1G SFPs and step down; a 10G module will not run in a 1G-only port.
- Media, wavelength & reach — both ends of a link must match: same media type (for example 10GBASE-LR), same wavelength (1310 nm), same fiber (OS2 single-mode) within the rated distance.
- Vendor coding — the EEPROM identity the switch reads to decide whether to trust the optic. This is the part people trip over.
SFP form factors & data rates
Pick the cage first — it fixes the maximum rate. This table maps the module families we stock across networking & optics:
| Form factor | Data rate | Connector | Typical media & reach |
|---|---|---|---|
| SFP | 1 Gb/s | LC / RJ45 | 1000BASE-SX 550 m MMF · LX 10 km SMF · T 100 m Cat5e |
| SFP+ | 10 Gb/s | LC / twinax | 10GBASE-SR 300–400 m MMF · LR 10 km SMF · DAC 1–7 m |
| SFP28 | 25 Gb/s | LC / twinax | 25GBASE-SR 100 m · LR 10 km · DAC 1–5 m |
| QSFP+ | 40 Gb/s | MPO / LC | 40GBASE-SR4 100–150 m · LR4 10 km |
| QSFP28 | 100 Gb/s | MPO / LC | 100GBASE-SR4 100 m · LR4 10 km |
| QSFP-DD / OSFP | 400 Gb/s | MPO-16 / LC | 400GBASE-SR8 · DR4 · FR4 / LR4 |
What is transceiver coding / vendor lock?
Every optic carries a small EEPROM programmed per the SFF-8472 specification, holding a vendor name, part number, serial and media parameters. Switch operating systems read this identity and compare it against an internal list of qualified optics. Depending on platform and policy, an unrecognized identity can produce a warning, a syslog message, or an errdisable shutdown of the port. Nothing about the optical or electrical path changes — this is a software trust check on a text field.
Coding is the process of programming that EEPROM to present the identity of a specific OEM optic (for example, a Cisco SFP-10G-LR). A module coded to the target platform is treated as OEM: it links without configuration changes and reports full DOM. Networking Corner codes optics to the requested OEM before shipping and verifies link and DOM on the bench — see how we test.
Running third-party optics by platform
Behavior differs by vendor. Coding to the OEM identity resolves it everywhere; where a module is left generic, these are the platform defaults and the command that permits an unqualified optic:
| Platform | Default behavior | Enable third-party optic | DOM |
|---|---|---|---|
| Cisco IOS / IOS-XE | May error-disable an unqualified optic | service unsupported-transceiver | Yes |
| Cisco NX-OS | Warns; generally links (release-dependent) | no errdisable detect cause gbic-invalid | Yes |
| Arista EOS | Links by default | None required | Yes |
| Juniper Junos | Links; logs "unsupported" message | None required | Yes |
| HPE / Aruba | Accepts HPE-coded or Aruba optics | Use coded optic | Yes |
Note: service unsupported-transceiver is a global, unhidden command that disables Cisco's optic qualification check for the whole switch. Prefer OEM-coded optics in production so no platform-wide override is needed and TAC support cases stay clean.
Digital Optical Monitoring (DOM/DDM)
DOM — also called DDM — is defined by SFF-8472 and lets the switch read live telemetry from the optic. A correctly coded third-party module exposes the same five parameters as the OEM part:
- Module temperature (°C)
- Supply voltage (Vcc)
- Laser TX bias current (mA)
- TX optical power (dBm)
- RX optical power (dBm)
Read it with show interfaces transceiver on Cisco or show interfaces diagnostics optics on Juniper. RX power outside the receiver's rated range is the first thing to check when a link is flapping — usually a reach, connector or attenuation problem rather than the module.
Ordering the right optic
Match the link end-to-end, not the brand: same media type, wavelength and reach at both ends, coded to each platform's OEM identity. Enter your switch model or an OEM optic part number in the Compatibility Tool to see the coded modules we stock for it. On Catalyst 9300 (C9300-48P-A) uplinks, for example, an SFP-10G-LR-coded module links on the SFP+ ports with full DOM and no service unsupported-transceiver override.
Related reading: Which SFP works with a Catalyst 9300 maps optics to each C9300 network module, and Refurbished vs new vs recertified explains the condition tiers and warranty behind coded and house-brand optics.
Frequently asked questions
Will a third-party SFP work in a Cisco switch?
Yes, in nearly all cases. An SFP/SFP+ is an MSA-standard module, so any compliant optic is mechanically and electrically interchangeable. Cisco IOS and IOS-XE may error-disable an unrecognized optic until you enter the global command service unsupported-transceiver (and, if needed, no errdisable detect cause gbic-invalid). A module coded to the Cisco vendor ID links without any configuration change.
Does coding a transceiver affect performance or DOM?
No. Coding only writes the vendor and part identity into the module EEPROM per SFF-8472; it does not change the optics, laser or electrical path. A correctly coded module links at full rate and reports Digital Optical Monitoring — temperature, supply voltage, TX bias, TX power and RX power — identically to the OEM part.
Can I mix OEM and third-party optics on the same switch?
Yes. The switch evaluates each port independently, so OEM and correctly coded third-party optics can coexist across ports on the same switch. Match each link end-to-end on media type, wavelength and reach — for example 10GBASE-LR at both ends — rather than matching the transceiver brand.
What is the difference between SFP and SFP+, and are they backward compatible?
SFP is the 1G form factor and SFP+ is the 10G evolution of the same MSA cage. Most SFP+ ports accept a 1G SFP and negotiate down to 1G, but a 10G SFP+ module will not operate in a 1G-only SFP port. Always confirm the port's supported speeds on the platform datasheet.
Does using a third-party optic void my switch warranty?
Using a third-party optic does not by itself void a switch warranty, but an OEM support contract may ask you to reproduce a suspected fault with a qualified OEM optic before escalating. Third-party optics are widely deployed in production; keep a coded spare on hand for support cases that require OEM reproduction.