CodingBox Q&A Ask question

All questions

Latest questions from the community.

355 questions
15 30 50 per page
3votes
1 answer
155views

Where to set hw.ix.unsupported_sfp=1 on a Netgate XG-7100 with third-party optics (loader.conf.local vs GUI tunables)

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…

5votes
5comments
223views

ConnectX-7 400G OSFP to a QSFP-DD switch port: is a passive DAC enough, or do the lane rates get in the way

Bringing up a pair of GPU boxes against our existing 400G fabric, and I have already managed to buy the wrong cable once, so I would rather get the theory straight before ordering again. NIC: ConnectX-7 MCX715105AS-WEAT, single 400G port, OSFP cage Switch: 400G QSFP-DD ports In hand: a passive 400G…

Indonesia sfpeng49 ID asked
1vote
1 answer
172views

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…

5votes
1 answer
211views

Brocade 200e between Proxmox and FreeNAS: Buffer I/O error and isp0: Receive Error while all ports show online

Running a small virtualization setup: two Proxmox 6 nodes and a target on FreeNAS 11.2. While the HBAs were connected to the target directly, everything ran for months without a single error. Put a used Brocade 200e between them to avoid crossing cables, and that's when it started. two Proxmox 6…

2votes
1 answer
106views

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

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…

6votes
6comments
141views

Turris Omnia pins a Luleey LL-XS2510 XPON stick to 1000baseX and ethtool never offers 2.5G

My fibre WAN runs into a Turris Omnia and I moved from the ISP box to an XPON stick to drop one hop. The stick is a 2.5G part, the Omnia cage does 2.5G, and everything still lands at 1G. Turris Omnia, Turris OS 7.0.2 HBS, kernel 5.15.148 Luleey LL-XS2510 XPON SFP, RTL960x based, DFP-34X-2C2 family…

1vote
1 answer
143views

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…

2votes
1 answer
319views

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…