We’ve been using vyatta/vyos for 6 or 7 years now. Until today we’ve been very happy with it. Many gigabit units and the last 3 or 4 years all vmware vmxnet 10GB virtual servers. Things have worked great.
Until today. First we had to disable the XHCI and USB 3.0 to get it to install whatsover from USB.
Then none of the 10GB interfaces are coming up.
Tried the latest 1.1.7 and the build of today with the 1.2.999.
Vyos seems to not been picking up on them online at all. Just ONCE we saw the internal ones ‘up’ with the 1.2 beta code. It appears the broadcom ones have never even been detected.
Is Vyos dying out? The underlying OS seems to be very outdated and there is no effort to keep it up.
Any ideas? We had high hopes of these in datacenters. Not sure what to do now.
Hello,
we don’ t have supermicro servers nor spare time for them,
so until someone with device start fixing issues, it will be like that.
For us VyOS is not dying We just focused on things we need
Interesting approach and timelines. The devices in them are not supermicro, they are intel and broadcom NICs The two top NICs used by enterprise which are not only moving to 10G but also 40G and 100G. 1G Nics are not used anywhere in data centers now. For VyOS to progress beyond the “Home Lab” these are the type of things that need fixed. As Enterprise admins we are willing to try opensource things, but if there is no support from the native community it is time to move on. Very sad as we have been exclusive vyatta, vyos for 8 to 10 years.
Small quite form factor.
Xeon CPU
6 onboard 1GB Nics,
2 onboard 10GB Nics
Added a second 10GB PCIe card for 2 more 10GB.
NVMe on motherboard.
This should be a workhorse. 2 of these for bare metal with failover is the plan. Both for under $2000 total.
Really not sure why you would not want to support this.
Known issues:
Cannot support USB install without modifying bios. (Turn off XHCI and USB 3.0 Compatibility as a work around) This issue has been open for a couple years.
Broadcom 5700 NICs not being detected.
Intel X552/X557 NICs not “up” when connected.
We have already figured our next step. Just posting this for the next guys.
Well,
i not told that we don’t want support that,
just that don’t have possibility spend time for that.
Still everybody have access to sources and build script and welcome to submit pull requests.
Hi
What did you figure out? I was thinking about purchasing a couple of these myself.
But if the internal nics are a problem, I’ll rather find something that allows me to use a pci-e dual nic.
I know this is an old thread but the SFP ports not coming up have nothing to do with VyOS. I am running the same server on CentOS 7 and it doesn’t come up because the linux drivers don’t support auto negotiation.
If you want to use the SFP+ ports you have to configure the speed/duplex settings because the controller cannot auto negotiate. In CentOS 7 if you try “ethtool -s eno8 speed 1000 duplex full” the link will come up.
I had a 1Gbit SFP on the switch connected to the server thats why the speed was set to 1000. I am not familiar with VyOS yet but I am planning to run it on these servers.
You have to edit the interface config to make the speed/duplex config permanent.