Latest questions from the community.
A Linux server with an Intel 82599ES 10-Gigabit SFI/SFP+ controller showed no 10G interface and dmesg contained failed to load because an unsupported SFP+ or QSFP module type was detected after an untested SFP+ module was inserted. The article explains that the ixgbe driver only enables modules it…
All 10G ports on a Netgear M5300-28G3 were used, so the poster asked whether a Cisco 3 m SFP+ DAC (H10GB-CU3M) or Finisar FTLX8571D3BCL 10G SR modules could be used in the switch's 1G SFP ports to add another 10G-capable device at reduced speed. Hardware involved: Netgear M5300-28G3, Cisco…
A Dell-branded Intel X520-DA2 with Flypro 10GBASE-T SFP+ modules showed no carrier (or no interface at all) on Debian and on FreeBSD-based OPNsense because the card rejects unapproved modules. The post collects the per-OS fixes and the permanent EEPROM approach. Hardware involved: Dell-branded…
The poster bought a Cisco SFP-10G-SR on eBay (markings suggesting 2007 manufacture) and, warned about counterfeit Cisco optics with longevity and safety risks, asked how to tell whether it was genuine before deploying it. Hardware involved: Cisco SFP-10G-SR. Reported symptoms/messages: authenticity…
The two SFP ports (F1/F2) of a Brocade ICX6450-C12-PD, licensed for 10G, would not come up with either a Brocade 1000BASE-LR SFP (33211-100) or 10GBASE-SR modules over a 5 m single-mode patch to an ICX6450-24P. show media saw the transceivers but the interface reported GigabitEthernet1/3/1 is down…
On an Intel S2600WFT board the X722 10GbE SFP+ controller (rev 09, NVM 3.31 0x80000d31 1.1767.0) refused ethtool -m with Cannot get module EEPROM information: Invalid argument, and the kernel logged Module EEPROM memory read not supported. Please update the NVM image. The behaviour was identical…
Intel X710/XL710 adapters refuse third-party optics at the firmware level with the message Rx/Tx is disabled on this device because an unsupported SFP module type was detected, and the i40e driver offers no override. The repository documents a procedure to remove the check: update to a known…
The thread starter documented that 82599-based X520 cards carry an undocumented EEPROM bit (IXGBEDEVICECAPSALLOWANYSFP, lowest bit of the capability word at byte offset 0x58, typically 0xFC locked / 0xFD unlocked) that decides whether non-Intel active SFP+ modules are accepted on ESXi and Windows…
A FreeNAS build on a Supermicro X11SPM-TPF board would not recognise a Ubiquiti UF-RJ45-10G SFP+ copper module in the on-board SFP+ cage, although the switch side showed link. The poster asked for BIOS settings or a compatible 10G RJ45 transceiver. Hardware involved: Supermicro X11SPM-TPF, Intel…
A FreeNAS box with on-board Intel X552 SFP+ ports (Xeon D) and an ESXi 6.7 host with a Mellanox ConnectX-3 (MT27500, Dell Y3KKR) were cabled with two Mellanox MCP2104-X003B passive DACs from 2014. Looping each device to itself brought the ports up, but between the two systems ESXi showed…
Intel X520 (82599) cards enforce a list of approved SFP+ modules; under Linux the ixgbe parameter helps, but on Windows or ESXi there is no such option. The gist provides a Python script that reads the card EEPROM with ethtool -e and sets bit 0 of the byte at offset 0x58 (0 = Intel modules only, 1…
The poster had third-party SFP+ optics for both the on-board Intel X553 ports of a Netgate XG-7100 and an add-in X520-DA2 and had found that hw.ixgbe.unsupportedsfp=1 in /boot/loader.conf enables them. Questions: does it apply to both on-board and PCIe Intel ports, what is the difference between…
The poster tried a Mellanox MFA2P10-Axxx 25G SFP28 AOC between a MikroTik switch and a Supermicro server with an Intel X722 (ixl driver) under pfSense. The cable linked fine switch-to-switch but on the X722 ifconfig -vvvm showed the module recognised (10GBase-SFI, 1000Base-KX listed) yet no carrier…
A QSFPTEK 10GBASE-T SFP+ module installed in port ix1 of a passively cooled Netgate 6100 reported 73 C through DDM although the room was at 20 C; the module is specified for 0-70 C and up to 2.5 W. The poster asked for known-good RJ45 SFP+ modules that stay within spec. Hardware involved: Netgate…
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…
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!…
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…
After upgrading to Proxmox VE 8 with the 6.x kernel, on-board Intel X553 SFP+ ports that worked on kernel 5.15.108 showed NO-CARRIER even with the cable and module connected. The regression was traced to an upstream ixgbe commit (565736048bd5) that broke auto-negotiation handling for X550/X553…
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…
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…
On an HP 5820-24XG-SFP+ (JC102A) the ports cabled with genuine HP X240 10G SFP+ 3 m DACs (JD097C) came up but logged OPTMOD/4/FIBERSFPMODULENOWINVALID: This is not a supported transceiver for this platform, and broadcast/multicast counters on those ports grew faster than normal. The cable is listed…
On a Minisforum MS-01 running Proxmox (i40e, kernel 6.8.12-10-pve) the X710 SFP+ port enp2s0f0np0 recognised a Ubiquiti SFP+-to-RJ45 module (ethtool listed 10G Base-SR capability) but the link never came up: Link detected: no, interface DOWN, no dmesg errors, ip link set up made no difference…
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…
Several pairs of 3COM 2928 switches (JE007A-like, HP 1910-24G family) were linked over J9281B SFP+ DACs. After upgrading from 5.20 1108P01 to 5.20 1519P03 the links no longer came up. Before the update display transceiver interface showed STACKSFP / Tyco Electronics and simple LINK UPDOWN events…
The poster configured new HP 2530-48G switches (J9281B) with J9775A SFP+ direct-attach cables bought as accessories. The ports stayed down and the log said FFI: port 49 Transceiver type not supported in this port; show tech transceivers first showed nothing and, after upgrading from YA.15.12.0007…
A 2920-48G-PoE+ (J9729A) rejected a J9283B 3 m SFP+ DAC with 00536 FFI: port 45 Transceiver type not supported in this port even though HP lists the cable as compatible; the same cable worked in a 2530 with SFP+ slots. Firmware had been updated without effect. A later reader noticed an old J9283B…
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…
On an HPE 5510 24G SFP 4SFP+ HI (JH149A, Comware 7.1.045 R1111P01) genuine JD119B and JD118B 1G SFPs were accepted at first (OPTMOD/4/MODULEIN: The transceiver is 1000BASESXSFP), but after a cold power reboot the same modules were reported as UNKNOWNSFPPLUS with OPTMOD/5/CHKSUMERR: Transceiver…
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…
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…