CodingBox Q&A Ask question

Top questions

Popular discussions about programming, compatibility and testing of optical transceivers.

111 questions
15 30 50 per page
2votes
1 answer
254views

Does 'service unsupported-transceiver' still work for third-party optics on Catalyst 9300 with IOS XE Everest?

The poster asked whether anyone had used third-party optics in a Cisco Catalyst 9300 series switch running IOS XE Everest (16.x), and specifically whether the hidden global command 'service unsupported-transceiver', long used on older Catalyst platforms to accept non-Cisco SFPs, still functions on…

2votes
1 answer
154views

CBS350 SFP-10G-LR link only comes up when the TX fiber is inserted before RX; faulty transceiver pair

While rolling out single-mode fiber between Cisco CBS350-8MGP-2X switches (firmware 3.4.0.17) with SFP-10G-LR modules, the poster hit strange behaviour: the link only comes up if the duplex LC connector is split and the TX fiber is inserted first, then the RX fiber. Inserting the joined LC…

0votes
2 answers
47views

Eight new J9150D transceivers fail with Unsupported Transceiver (SelftTest Err#098000) on a 5406R zl2: all counterfeit

The poster bought eight J9150D 10G SR SFP+ transceivers for an Aruba 5406R zl2 chassis with a J9993A module. Every module lit the orange LED and logged Unsupported Transceiver. (SelftTest Err#098000), even though the compatibility documents list this combination and the chassis had already been…

6votes
4comments
164views

1G SFP in a Catalyst 3850 uplink module reported unsupported and err-disabled

The poster has a stack of two Cisco Catalyst 3850-48T switches, each fitted with a 2x1G/2x10G fiber uplink network module. Two 10G fiber links already run in slots 2/1/3 and 2/1/4. When a single-mode 1G SFP is inserted into 1G slot 2/1/1, the switch reports the module as unsupported and places the…

3votes
3comments
93views

ethtool -m fails on FS.com XXV710 NIC: "Module EEPROM memory read not supported" and NVM not updatable

On Ubuntu 18.04 (kernel 5.4.0, ethtool 5.3, i40e 2.8.20-k) the poster used 25G XXV710-based NICs bought from FS.com (FS part XXV710AM2-F2, Intel XXV710 chipset). Link and error-free wire-speed traffic worked, but reading a transceiver's DMI data with sudo ethtool -m enp4s0f0 failed with "Cannot get…

6votes
3comments
60views

Finisar FCLF8521P2BTL 1000BASE-T SFP rejected by Intel X710-DA2 despite feature matrix listing

The poster wanted to use a Finisar FCLF8521P2BTL 1000BASE-T copper SFP in an Intel X710-DA2 running NVM 7.1. Intel's X710/XXV710/XL710 Feature Support Matrix (rev. 3.4, Nov 2019, doc 332191-024) lists single-speed SFP 1GBASE-T transceivers with support limited to Finisar FCLF-8521-3, Kinnex A…

1vote
1 answer
55views

Real incidents caused by third-party optics: slow I2C crashing a linecard and a DDM uptime overflow bug

In a NANOG discussion about vendor lock-in, an operator described two concrete failures. First, a third-party optic answered I2C reads too slowly; the switch vendor's polling code did not handle the timeout and crashed the linecard control plane, and the vendor refused to treat it as a bug because…

1vote
1 answer
63views

Non-Juniper SFP+/SFP modules not detected in any port of an EX2300-24P but fine in an EX2300-48P

While staging an EX2300-48P and an EX2300-24P (both Junos 18.2R3-S5.3) with non-Juniper SFP+/SFP modules, the 48-port switch recognised the transceivers and created interfaces, but the 24-port switch showed nothing in any of its four uplink ports; show chassis hardware listed PIC 1 as 4x10G…

4votes
1 answer
40views

CSCwo18785: 'ERROR: The transceiver doesn't support this speed' with a third-party 200G DAC on Nexus 9332D-GX2B

The poster, validating their product against Cisco Nexus 9000 switches (a Nexus C9332D-GX2B chassis), is blocked by bug CSCwo18785: configuring 200G on a QSFP-200G DAC fails with 'ERROR: The transceiver doesn't support this speed'. The cable is a Mellanox MCP1650-H002E26 200GbE DAC; connected…