CodingBox Q&A Ask question

All questions

Latest questions from the community.

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

1G SFP on Intel X710 (pfSense, ixl) fails with unqualified module until the optic is recoded as Intel

On a Protectli Vault 6 with Intel X710 SFP+ ports (ixl0/ixl1) a 1G EZConn ETB43315-7S34-FR SFP showed no carrier. Logs contained Invalid advertised speed; valid flags are: 0x06, ixl1setlink: Error getting phy capabilities -37, aq error: 8 and Link failed because an unqualified module was detected!…

1vote
1 answer
234views

XCP-ng with X520-DA2 and Finisar SFP+: allow_unsupported_sfp must be set per port on the kernel command line

An XCP-ng host with an Intel X520-DA2 and Finisar SFP+ transceivers logged failed to load because an unsupported SFP+ or QSFP module type was detected. insmod with allowunsupportedsfp=1 failed with Unknown symbol in module; options ixgbe allowunsupportedsfp=1 in /etc/modprobe.d/ixgbe-options.conf…

1vote
1 answer
76views

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 third-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…

2votes
1 answer
259views

Proxmox on a Dell R720 with X520 rNDC: ixgbe allow_unsupported_sfp=1 does not take effect for Cisco SR modules

A Dell R720 with the integrated i350/X520 daughter card ran Proxmox VE; Cisco-branded 10G multimode LC SFP+ modules that worked elsewhere were rejected as unsupported. Adding options ixgbe allowunsupportedsfp=1 to the module options had no visible effect. Respondents walked through GRUB kernel…

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…

1vote
3comments
221views

HP 5120-EI never brings up an Allied Telesis AT-SPEX SFP: FIBER_SFPMODULE_NOWINVALID, no way to disable the coding check

On an HP 5120-EI the poster inserted an Allied Telesis AT-SPEX 1310 nm SFP and got a PHONY ENTITY trap plus OPTMOD/4/FIBERSFPMODULENOWINVALID: This is not a supported transceiver for this platform; the port never came up. The poster looked for a command to disable enforcement of SFP coding. Later…

1vote
1 answer
45views

HP 5900AF logs OPTMOD/4/PHONY_MODULE for Avago and JDSU 10G SR modules while a Cisco 6500 peer shows input errors

An HP 5900AF-48XG-4QSFP+ (Comware 7.1.045 R2311P01) logged OPTMOD/4/PHONYMODULE: This is not a supported transceiver for this platform for two 10G SR SFP+ modules; display transceiver interface identified them as Avago and JDSU 10GBASESRSFP with DDM. The poster wanted to know which SFP+ to buy and…

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…