CodingBox Q&A Ask question

rxadmin25

Spain joined 4 months ago 8 questions 14 comments

Datacenter technician from Valencia. Mostly ISP backbone.

Questions

0votes
0comments
99views

OPNsense 22.7: interface is disabled due to unsupported sfp on a 10G port, and the Linux ixgbe tunable does not apply

After upgrading OPNsense from the 21.x series to 22.7 a 10G SFP+ port stopped working with interface is disabled due to unsupported sfp; the newer Intel driver actively disables unrecognised modules. The poster tried to set ixgbe.allowunsupportedsfp=1 as a system tunable, which was not accepted…

0votes
1comment
46views

Genuine versus third-party SFP/SFP+ on Extreme switches: DDMI not readable on an X620, no vendor support

The poster had free thrid-party SFP/SFP+ samples that worked on Extreme switches and asked whether to buy genuine or third-party modules. A respondent reported that on a new X620 a third-party SFP+ linked but its DDMI data could not be read, and that Extreme provides no help for problems involving…

2votes
2 answers
16views

Connecting a UDM SE 10G SFP+ port to an Enterprise XG 24 SFP28 port: which DAC, and the mixed-speed limitation

The poster wanted to connect a UDM SE (10G SFP+) to an Enterprise XG 24 switch (25G SFP28) and asked whether an SFP+ DAC would work with the SFP28 port falling back to 10G, or whether an SFP28 DAC was preferable. The concern was whether the SFP28 cage would fall back to 10G with an ordinary SFP+…

1vote
1 answer
78views

Proxmox VE 6: X520-DA2 fails to load because an unsupported SFP+ or QSFP module type was detected

On Proxmox VE 6.0 (kernel 5.0.18-1-pve, ixgbe 5.1.0-k) an Intel X520-DA2 exposed ens1f0/ens1f1 but any inserted thirrd-party SFP+ module produced failed to load because an unsupported SFP+ or QSFP module type was detected, and the driver had to be reloaded to detect module changes at all. Hardware…

3votes
2 answers
135views

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 onlly genuine transceivers, and refused the modules; ironically one of the rejected transceivers was HP-branded. The poster asked whether a command…

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…