CodingBox Q&A Ask question

Suppliers and vendors

Experience with suppliers, third-party modules, warranty and pricing

10 questions
15 30 50 per page
1vote
2 answers
146views

VyOS on Supermicro SYS-1019D with Intel X722: i40e has no allow_unsupported_sfp, third-party SFP+ rejected

On a Supermicro SYS-1019D-FRN8TP running VyOS 1.4 rolling the on-board Intel X722 (i40e) did not recognise an ISP-supplied 1310/1270 nm single-fibre SFP nor other spare optics; ethtool -m returned Cannot get module EEPROM information: Invalid argument. The poster asked how to apply the well-known…

1vote
1comment
156views

Aruba Instant On 1930 shows SFP+ ports DOWN in the dashboard with third-party D-NET LX modules that pass traffic

On an Aruba 1930 (JL685A, software 2.6.0) two D-NET DN-SFP-LX modules in SFP+ ports 49 and 50 actually carried traffic, yet the web dashboard showed both ports as DOWN and, without a CLI, the poster could not check whether the modules were identified. The question was whether this was a bug, an…

0votes
1 answer
182views

Third-party optics on HPE FlexFabric 5700: no allow command, only transceiver phony-alarm-disable

The poster asked whether third-party optics can be used in an HPE FlexFabric 5700 40XG 2QSFP+ (JG896A) and whether the ProVision command allow-unsupported-transceiver exists on it. The answer clarified how Comware differs from ProVision: there is no allow-list of supported transceivers, so unlisted…

1vote
3comments
125views

Enabling a third-party transceiver on HPE FlexFabric 5900AF: no CLI switch, ask the supplier to code it for HP 5900

A FlexFabric 5900AF running Comware 7.1.035 R2208P01 reported a third-party transceiver as not supported when inserted, while the same class of modules worked in a FlexFabric 7904 on 7.1.045. The poster asked whether support could be enabled by command and whether the Comware version mattered…

3votes
2 answers
132views

Enabling third-party SFPs on an Aruba 2530-48G-2SFP+: allow-unsupported-transceiver from 16.02.0013

An Aruba/HPE 2530-48G-2SFP+ on firmware 16.01.0012 logged Port contains a transceiver not made by Hewlett Packard Enterprise with the advice to use only genuine transceivers, and refused the modules; ironically one of the rejected transceivers was HP-branded. The poster asked whether a command…

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…

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…