Third-party optics and coding: how to order a transceiver your switch accepts
What coding in a transceiver's EEPROM does, why switches check it, what you actually risk with third-party optics and how to order the right coding.
The SFP+ modules you ordered slide into the port perfectly, and the switch rejects them. No link, just a message about an unsupported transceiver. Or you haven't ordered yet and you're wondering whether third-party optics will cause trouble with your switch or your support contract. This article explains what codingCodierung Die Herstellerkennung im EEPROM eines Transceivers. Viele Switches akzeptieren nur Optiken, die für die eigene Marke codiert sind. actually is, why switches check it, which risks are real and which aren't, and exactly what to tell us so the module works first time.
What coding is, down to the byte
Every transceiver carries a small EEPROM with a fixed layout. For SFP and SFP+ that layout is defined in SFF-8472, for QSFP+ and QSFP28 in SFF-8636, and for QSFP-DD and OSFP in CMIS, now maintained by the OIF.
On an SFP+ it holds identity fields such as:
- Vendor name — 16 ASCII characters, bytes 20 to 35.
- Vendor OUI — the manufacturer's IEEE company ID, bytes 37 to 39.
- Vendor PN — the part number, bytes 40 to 55.
- Checksums — CC_BASE (byte 63) and CC_EXT (byte 95), each the low-order 8 bits of the sum of a fixed block of preceding bytes.
- Vendor specific — bytes 96 to 127, whose content the spec deliberately leaves open.
Coding means filling those fields so your platform recognises the module as something it accepts. Change one field without recalculating the checksum and the EEPROM is no longer consistent, and a host that checks will reject the module. That's why coding is a craft, not a matter of overwriting a name somewhere.
Why your switch checks it
A switch reads the EEPROM the moment you insert the module. According to an article in Cisco's community knowledge base, a Cisco switch verifies the serial number, vendor name and vendor ID, recomputes a security code and a CRC, and raises a security error if anything doesn't match. The port may then go err-disabled.
Even a correctly coded module can disappoint: Cisco notes that a newer module may need a newer software release. So coding depends on the platform and the release.
Vendors support what they have qualified themselves. That's a support decision, not a law of physics: the MSA and SFF documents describe the form factor, electrical interface and memory layout, not which brand a host has to accept.
Third-party: same product, different identity
A third-party (or compatible) transceiver is built to the same MSA and SFF specifications as the OEM part. Same form factor, same electrical interface, same memory layout with the same DOM/DDMDOM/DDM Digital Optical Monitoring / Digital Diagnostic Monitoring: Der Transceiver meldet live Temperatur, Versorgungsspannung, Laserstrom sowie Sende- und Empfangsleistung. fields. The difference comes down to two things: who filled in the identity, and whether anyone tested the module on your type of equipment.
A perfectly coded module that has never been in your switch is a gamble. A module tested with full traffic on the target platform isn't.
What's actually at stake
The risks are real, so here they are, straight:
- Support — Cisco states it may withhold support under warranty or a support programme such as Smart Net Total Care if a fault can be traced to third-party components; the wording names GBICs and cables among others. If the cause is something else, support carries on as normal.
- Qualification — Juniper's hardware documentation (the NFX250, for example) states that JTAC does not support third-party optics Juniper hasn't qualified. During troubleshooting, JTAC will likely ask you to check the module and, if needed, swap in a qualified one.
- Power and heat — the same documentation warns that high-power third-party modules, such as coherent ZR or ZR+, can cause thermal damage to the host, and accepts no liability for it.
Our view: for the vast majority of links, third-party is the sensible choice, provided it's tested. For critical ports, keep a spare with the same coding at hand so you can swap quickly during a TAC case. What this means legally is in your support contract, so read it.
How we code
Our optics come from Solid Optics, a Dutch company. They test in the Netherlands, per batch and per item, with full traffic on the equipment the module is meant for, and on the customer's own equipment where needed. Every module carries a lifetime warranty.
Our RMA rate stands at 0.7%, and we count everything in it: wrong choices, degradation and checks. We have never had a DOA.
Watch out with HPE and Aruba: for those we ship a module with licensed HPE/Aruba coding. It can't later be re-coded to another brand and back again. It does work fine in other brands' equipment.
How to order the right coding
- Note the brand and model of the device each module goes into.
- Note the software version it runs.
- Pick your platform's brand under Coding on the product page, or MSA (Generic) if your device doesn't check the vendor.
- Order your spares with the same coding as the modules in production.
- Have the module tested before you roll out if you're in any doubt.
You choose the coding per line in the shop, for example on the SFP-10G or across our full optics range, including SFP28 and QSFP28. Want a module tested on your own equipment first, or a rollout delivered with link tests? Have a look at our services, or call an engineer.

Gründer von FiberNxt und Xyphen IT
Yvan Watchman ist Gründer von FiberNxt und Xyphen IT. Er baut und betreibt seit Jahren Netzwerke und Rechenzentrumsinfrastruktur in und um Amsterdam.
Passende Produkte und Dienstleistungen
Häufig gestellte Fragen
Is a third-party transceiver worse than the OEM part?
Not by definition. Both are built to the same MSA specifications for form factor, electrical interface and memory layout. The difference is the coding and whether the module was tested on your platform. A well-tested third-party module beats an untested one of unknown origin, logo or no logo.
Do I lose vendor support if I use third-party optics?
Not automatically, but read your contract. Cisco states it may withhold support under warranty or Smart Net Total Care if a fault can be traced to third-party components. Juniper JTAC does not support third-party optics that Juniper hasn't qualified and may ask you to fit a Juniper-qualified module.
Which coding do I pick if my device doesn't check the vendor?
Pick MSA (Generic). Not sure whether your platform checks? Send us the brand, model and software version and we'll tell you which coding you need.