Enable third-party optics on Cisco, Nexus, Meraki, Aruba, Juniper and Arista
Switch rejects your optic? The command or setting per platform to allow third-party optics, what it costs you in support, and why the right coding is better.
Your new optics are in and the switch rejects them: "unsupported transceiver", a port in err-disabled, or no link. Most platforms have a command or setting that turns off the check for non-original optics. Below, per platform, is what you type, what the default behaviour is and what it costs you in support. After that we explain why an optic with the right codingCodierung Die Herstellerkennung im EEPROM eines Transceivers. Viele Switches akzeptieren nur Optiken, die für die eigene Marke codiert sind. is usually the better route.
Cisco Catalyst (IOS and IOS XE)
Catalyst checks the coding and puts an unknown optic into err-disabled with cause gbic-invalid. The well-known pair:
conf t
service unsupported-transceiver
no errdisable detect cause gbic-invalid
Then shutdown and no shutdown the port, and pull the optic and reinsert it. That's how a Cisco tech note describes it for the Catalyst 3850.
- Hidden command —
service unsupported-transceiverisn't in any command reference. According to users it's gone on some models and versions, and it doesn't exist at all on Cisco Business switches. - Recovery only — if you want to keep the check but not intervene by hand,
errdisable recovery cause gbic-invalidbrings the port back up after a timer. That doesn't fix the rejection.
Cisco Nexus (NX-OS)
On the Nexus 9000, service unsupported-transceiver is documented, as a global configuration command. According to Cisco it's even the default configuration there. So a Nexus 9000 that rejects an optic probably has no service unsupported-transceiver in its config. Removing that on a first-generation N9K with FEXes? Read the release notes first: Cisco describes a bug where the FEX ports go to "sfp invalid" after a reload. For Nexus 3000 and 5000 we found no official documentation.
Meraki MS
Nothing to do. Meraki states that its MS switches don't lock out optics that aren't Meraki parts, and there's no dashboard setting for it. That documentation covers the MS line; it says nothing about cloud-managed Catalyst switches. Meraki doesn't officially support third-party modules, but support still helps when something breaks. If the problem lies with a link using such a module, support may ask you to test with a certified one.
HPE Aruba (AOS-CX and AOS-S)
Aruba is the most open. On AOS-CX, and on AOS-S 16.02 for a number of series (including 5400R, 3810M, 2930F/M, 2920, 2540 and 2530, up to 40G), you use the same global command:
config
allow-unsupported-transceiver
show allow-unsupported-transceiver
Without confirm, the switch first asks you to accept a warning that use is at your own risk and may void support and warranty. On AOS-CX it's on by default since 10.09 or 10.10, depending on the series, for speeds up to 100G; the first version (10.05) only went up to 10G. On AOS-S you have to turn it on yourself. Aruba calls the support "best effort" and doesn't guarantee that an optic keeps working after a firmware upgrade.
Juniper (Junos)
Junos flags optics from other brands in show chassis hardware as NON-JNPR, sometimes with UNSUPPORTED, but in practice usually lets them work. We found no official switch to allow them, and you usually don't need one. The catch is support: JTAC doesn't support third-party optics. For problems with the switch itself JTAC still helps, but it may ask you to install a Juniper-qualified module first.
Arista (EOS)
According to network operators, Arista puts a port with a non-Arista optic into errdisabled, with reason xcvr-unsupported. According to the same sources you unlock it with a key you request from Arista, tied to your organisation:
service unsupported-transceiver <customer-name> <key>
This isn't in Arista's public documentation. Check the key and the conditions with your Arista contact.
What the command costs you
A command disables the check, not the consequences. Cisco may withhold support under warranty or a support contract if a fault can be traced to third-party components. If the fault lies elsewhere, you get support as usual. Juniper and Meraki don't officially support the optic itself; their support still helps, but may ask you to test with a certified module. On top of that:
- Upgrades — a hidden command can disappear or behave differently after a software upgrade.
- Replaced switches — after an RMA or a replaced supervisor the configuration has to go back on, or your links stay down.
- Handover — the next admin doesn't know why that line is there.
The better route: your platform's coding
An optic coded for your switch needs none of these commands. The switch reads the right vendor data from the EEPROM and accepts it, also after an upgrade or on a replacement switch. How coding works is covered in third-party optics and coding. With our optics, such as the SFP-10G and the 25G SFP28 modules, you choose the coding when you order: Cisco, Juniper, Arista, Aruba (HPE) and around fifteen other brands, or MSA (Generic) for platforms that don't lock out optics, such as Meraki. They come from Solid Optics, a Dutch company that tests them here, including on customers' equipment, with a lifetime warranty. Not sure which coding your platform needs? Send us the switch model and software version, or have a look at our services.

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
What does service unsupported-transceiver do on a Cisco switch?
It's a hidden command that disables the check for non-Cisco optics. On Catalyst you combine it with no errdisable detect cause gbic-invalid. It isn't in the command references, doesn't work on every platform and software version, and Cisco may withhold support if a fault is traced to the optic.
Do I need to enable anything for third-party optics on Meraki or Juniper?
Usually not. Meraki MS switches don't lock out third-party optics, and there's no setting for it either. Junos flags them in show chassis hardware as NON-JNPR, sometimes with UNSUPPORTED, but usually lets them work. Neither vendor officially supports the optic itself. Support still helps, but may ask you to test with a certified module.
Why buy coded optics if a command does the job?
Because an optic coded for your platform needs no configuration, keeps working after an upgrade or a switch RMA, and doesn't start a discussion with the support desk. The command is a workaround; the coding is the fix.