CodingBox Q&A Ask question

All questions

Latest questions from the community.

111 questions
15 30 50 per page
1vote
3comments
127views

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
133views

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
155views

Why third-party SFP+ still fail on Aruba 3810M/2930M with allow-unsupported-transceiver: the HPIDv2 flag at byte 0x7B

Even with allow-unsupported-transceiver enabled, HPE Aruba 3810M and 2930M switches showed an amber fault for generic SFP+ modules, including ones recoded to masquerade as a J9151A. The author traced the behaviour to HPE's HPIDv2 challenge-response authentication: the module EEPROM carries a flag…

net_wizard14 asked
3votes
2comments
90views

Genuine Aruba J9151E SFP+ shows Unsupported Transceiver (SelfTest Err#128000) on 2930F switches

On Aruba 2930F switches (JL255A) the poster installed new J9151E 10G SFP+ transceivers (part 1990-4727) that the transceiver guide lists as supported, but every unit was reported as Unsupported Transceiver (SelfTest Err#128000) and show tech transceivers showed ?? for type and serial. J9281D DACs…

0votes
2 answers
48views

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…

2votes
2comments
160views

Arista 7050QX puts ports with unqualified third-party QSFP+ DACs into errdisable

On an Arista 7050QX running EOS 4.14 the poster tried to use third-party QSFP+ DAC cables; the ports went to errdisable as unqualified transceivers. They patched the XcvrAgent.py agent under /usr/lib/python2.7/site-packages to skip the manufacturer check, which cleared the errdisable state but left…

1vote
1 answer
57views

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
65views

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…