I am not sure why you think changing kernels is a bad idea. The kernel you are running mist be a 7.3 kernel. It will be vulnerable to the Spectre and Meltdown exploits and you really need to upgrade. If you have automatic updates enabled, you should just be able to reboot to install 3.10.0-957.10.1.v7. You can check what is on your system with a:

rpm -qa | grep ^kernel-3 | sort

The 393.x.y.v7 series are from 7.4, 862 from 7.5 and 957 from 7.6.

Clearcenter are keeping the last three devel packages available in the repos. It could be possible to jump through a few hoops and make 3.10.0-514.21.2.v7 available but with the Spectre and Meltdown issues overhanging, that would not be a good idea.

You may even find the later kernels support your NIC natively. What is the output of:

lspci -knn | grep Eth

[root@testsvr AQtion]# rpm -qa | grep ^kernel-3 | sort

kernel-3.10.0-514.21.2.v7.x86_64

so I did

yum install kernel-devel-3.10.0-514.21.2.v7.x86_64

and got

No package kernel-devel-3.10.0-514.21.2.v7.x86_64 available.

So

[root@testsvr AQtion]# lspci -knn | grep Eth

01:00.0 Ethernet controller [0200]: Device [1d6a:07b1] (rev 02)

03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)

	Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet [1458:e000]

Not sure if that helps.
The same PC runs the card fine in Mint 19.

If that is the only kernel you show, you are massively behind on your updates. Do you know how it got that way? Please do a:

yum update app-base

yum clean all

yum update

Then reboot.

If you do that then:

[root@server ~]# modinfo atlantic

filename:       /lib/modules/3.10.0-957.10.1.v7.x86_64/kernel/drivers/net/ethernet/aquantia/atlantic/atlantic.ko.xz

description:    aQuantia Corporation(R) Network Driver

author:         aQuantia

version:        2.0.2.1-kern

license:        GPL v2

retpoline:      Y

rhelversion:    7.6

srcversion:     7CE86B5B3014030C6277338

alias:          pci:v00001D6Ad000052B1sv*sd*bc*sc*i*

alias:          pci:v00001D6Ad000051B1sv*sd*bc*sc*i*

alias:          pci:v00001D6Ad000092B1sv*sd*bc*sc*i*

alias:          pci:v00001D6Ad000091B1sv*sd*bc*sc*i*

alias:          pci:v00001D6Ad000089B1sv*sd*bc*sc*i*

alias:          pci:v00001D6Ad000088B1sv*sd*bc*sc*i*

alias:          pci:v00001D6Ad000087B1sv*sd*bc*sc*i*

alias:          pci:v00001D6Ad000080B1sv*sd*bc*sc*i*

alias:          pci:v00001D6Ad000012B1sv*sd*bc*sc*i*

alias:          pci:v00001D6Ad000011B1sv*sd*bc*sc*i*

alias:          pci:v00001D6Ad000009B1sv*sd*bc*sc*i*

alias:          pci:v00001D6Ad000008B1sv*sd*bc*sc*i*

alias:          pci:v00001D6Ad000007B1sv*sd*bc*sc*i*

alias:          pci:v00001D6Ad000000B1sv*sd*bc*sc*i*

alias:          pci:v00001D6Ad0000D109sv*sd*bc*sc*i*

alias:          pci:v00001D6Ad0000D108sv*sd*bc*sc*i*

alias:          pci:v00001D6Ad0000D107sv*sd*bc*sc*i*

alias:          pci:v00001D6Ad0000D100sv*sd*bc*sc*i*

alias:          pci:v00001D6Ad00000001sv*sd*bc*sc*i*

depends:

intree:         Y

vermagic:       3.10.0-957.10.1.v7.x86_64 SMP mod_unload modversions

signer:         CentOS Linux kernel signing key

sig_key:        74:81:EC:3D:6B:C8:629:A3:6F:E0:3B:6B:5C:1A:B8:5D:8B:25:AE

sig_hashalgo:   sha256

parm:           aq_itr:Interrupt throttling mode (uint)

parm:           aq_itr_tx:TX interrupt throttle rate (uint)

parm:           aq_itr_rx:RX interrupt throttle rate (uint)

So it looks like it supports your card ([1d6a:07b1])

I am concerned if you want to use Clearglass if your partitions are XFS. Can you give the output of:

xfs_info /

If it says something with ftype=0, you won't be able to run ClearGLASS unless you create a new partition and mount /var/lib/docker into it. The default for ftype changed from 0 to 1 at either 7.3 or 7.4.

Good but your config won't work as you have both NIC's on the same subnet so ClearOS won't route. Also it is strongly recommended to avoid the 192.168.0.0/24 and 192.168.1.0/24 subnets. They are too common and can give you grief if you use OpenVPN or any other VPN where the normal requirement is to have each end of the VPN on different subnets.

Nick Howitt wrote:

Good but your config won't work as you have both NIC's on the same subnet so ClearOS won't route. Also it is strongly recommended to avoid the 192.168.0.0/24 and 192.168.1.0/24 subnets. They are too common and can give you grief if you use OpenVPN or any other VPN where the normal requirement is to have each end of the VPN on different subnets.

The mission was to get the 10gig card working and I managed that. It's a test server, I've now got to do it for the real one. The reason it's got two NICs is because only one worked.

What I'd like to do is connect one NIC to the Internet router and have the 10gig one connected to the Ethernet hub on it's SFP port and use ClearOS as the DHCP and gateway.
At this stage I'd be OK with 192.168.0.x as my Internet and 192.168.10.1 as my ClearOS. I can kick the Virgin router into Modem mode when I'm ready.

BTW, I did notice you other NIC was an "RTL8111/8168/8411". This does not work reliably well with the stock driver giving all sorts of exotic problems. It works much better with the r8168 driver. If you do a:

yum install kmod-r816*

It will install 2 drivers. The kmod-r8169 driver removes compatibility of the r8169 driver with the RTL8111/8168/8411 NIC and the kmod-8168 package provides the r8168 driver. You will need to reboot for the change to take effect.

Nick Howitt wrote:

BTW, I did notice you other NIC was an "RTL8111/8168/8411". This does not work reliably well with the stock driver giving all sorts of exotic problems. It works much better with the r8168 driver. If you do a:

yum install kmod-r816*

It will install 2 drivers. The kmod-r8169 driver removes compatibility of the r8169 driver with the RTL8111/8168/8411 NIC and the kmod-8168 package provides the r8168 driver. You will need to reboot for the change to take effect.

Those RealTek NICs are everywhere. It seems to be the standard integrated network on most motherboards. A bit worrying if Linux comes with a broken driver for that. However I've been using a ClearOS server with this card for years and it seems OK. I do get problems with it losing DNS until a reboot or network restart. I've run your command on both machines which took a while but don't notice anything working any differently.

End result is I have a Mint 19 desktop directly cabled to a ClearOS 7.6 server acting as DHCP using two of the ASUS 10gig network cards.

Speed tests over SAMBA using tmpfs drives show about 360MB/s transfer speeds. Not quite the 900MB/s I was expecting but loads better than the 90MB/s that a standard network does. 4 times faster is worth having. I'll probably have to say that's good enough because I am installing the server next week. It's going to be connected to a 1gig hub using a 10gig copper SFP adaptor. No one will see more than 90MB/s but 4 people could have that speed at the same time with no slowing.