Rebuilding My Server Getting Unsupported Sfp+ Working on Linux

Published on 2024-08-27

Categories: tech
Tags: selfhosting

I'm rebuilding VM my server. This post is about getting SFP+ 10GB "unsupported" devices working on Linux

Context

I have been running VMs on XCP-NG for a while now. XCP-NG does not come with a console by default, but Xen Orchestra (XOA) gets you covered. The only issue with XOA is the complete version requires you to compile and install it manually.

I’ve been lagging on this setup and remembered a time where I ran Proxmox.

So 2 days ago, I installed a HD in one of my kid’s desktop (don’t tell them), and moved my most critical services: plex and miniflux.

Today, I installed Proxmox.

Network Challenges

My server has 7 network ports:

• one IPMI admin port locked on a restricted network
• 4 onboard gigabit ports
• 2 SFP+ 10GB modules installed in a X520 PCIe network card

With that many ports, it could be challenge to find the proper port to setup in the network bridge.

My first issue? I got lost with so many ports and picked the wrong port.

My second issue? I did not notice my X520 card was not being detected properly.

The ixgbe kernel module needed for the X520 card reports the SPF+ modules as “Unsupported”.

There is a trick

You can tell ixgbe module to support the “unsupported” SPF+ modules.

With grub in /etc/default/grub

GRUB_CMDLINE_LINUX=”ixgbe.allow_unsupported_sfp=1″

For two modules:

GRUB_CMDLINE_LINUX=”ixgbe.allow_unsupported_sfp=1,1″

run update-grub and reboot.

When typing dmesg | grep ixgbe I now see the modules being detected.

Note to future self: type sfp instead spf to save some time.

Alternative

The same can be achieved by setting a module configuration:

1

echo "options ixgbe allow_unsupported_sfp=1,1" > /etc/modprobe.d/ixgbe.conf

For comments, use email or Mastodon

Don't forget to subscribe to my RSS feed!