Hi,
I noticed that one of out "Centos 5" servers with an onboard "Marvell 88E8001" was showing some packet overruns.
# ifconfig -a eth0 | grep "RX p" RX packets:1629537 errors:0 dropped:0 overruns:3694 frame:0
So I thought about using a driver from "elrepo" the lspci id's suggest to install the "kmod-sk98lin" driver. I yum installed the kernel module and on reboot found the server was still using the old "skge" driver.
ethtool -i eth0 driver: skge version: 1.6
Looking at modprobe.conf shows
# cat /etc/modprobe.conf | grep eth0 alias eth0 skge
[1] Should I just change the "skge" in the above line to "sk98lin" and reboot?
[2] This motherboard has a "Marvell 88E8052" as a second NIC, currently disbled in the BIOS. Problem is that the "88E8001" NIC has to be "eth0" as it is the one used in a "flexlm" license server file. In Centos five how can you *force* a given NIC controller to always post at "eth0" ?
Cheers, Steve
On 02.Sep.2013, at 22:14, Steve Brooks wrote:
[2] This motherboard has a "Marvell 88E8052" as a second NIC, currently disbled in the BIOS. Problem is that the "88E8001" NIC has to be "eth0" as it is the one used in a "flexlm" license server file. In Centos five how can you *force* a given NIC controller to always post at "eth0" ?
I think that setting HWADDR in ifcfg-eth0 should do the trick.
On Tue, 3 Sep 2013, Markus Falb wrote:
On 02.Sep.2013, at 22:14, Steve Brooks wrote:
[2] This motherboard has a "Marvell 88E8052" as a second NIC, currently disbled in the BIOS. Problem is that the "88E8001" NIC has to be "eth0" as it is the one used in a "flexlm" license server file. In Centos five how can you *force* a given NIC controller to always post at "eth0" ?
I think that setting HWADDR in ifcfg-eth0 should do the trick.
Thanks for the replay Markus, I thought that too but on reboot of the server it stayed at "eth1". That is why I disabled the other NIC in the bios and deleted all NIC configurations and reconfigured when it did come up as eth0.
It looks now like I need to keep the current NIC ("88E8001" with rx overruns) as device "eth0" so flexlm works and enable the "Marvell 88E8052" in the bios to take over the ethernet traffic.
Cheers,
Steve
On Tue, Sep 03, 2013 at 10:20:49AM +0100, Steve Brooks wrote:
On Tue, 3 Sep 2013, Markus Falb wrote:
On 02.Sep.2013, at 22:14, Steve Brooks wrote:
[2] This motherboard has a "Marvell 88E8052" as a second NIC, currently disbled in the BIOS. Problem is that the "88E8001" NIC has to be "eth0" as it is the one used in a "flexlm" license server file. In Centos five how can you *force* a given NIC controller to always post at "eth0" ?
I think that setting HWADDR in ifcfg-eth0 should do the trick.
You also have to look at /etc/udev/rules.d/70-persistent-net.rules
(Learned that after cloning some VMs, where the hardware address was wrong.)
On Tue, Sep 3, 2013 at 7:36 AM, Scott Robbins scottro@nyc.rr.com wrote:
On Tue, Sep 03, 2013 at 10:20:49AM +0100, Steve Brooks wrote:
On Tue, 3 Sep 2013, Markus Falb wrote:
On 02.Sep.2013, at 22:14, Steve Brooks wrote:
[2] This motherboard has a "Marvell 88E8052" as a second NIC,
currently
disbled in the BIOS. Problem is that the "88E8001" NIC has to be
"eth0" as
it is the one used in a "flexlm" license server file. In Centos five
how
can you *force* a given NIC controller to always post at "eth0" ?
I think that setting HWADDR in ifcfg-eth0 should do the trick.
You don't actually need hwaddr in your ifcfg-* files -- though it's probably not a bad thing to have the MAC in there. [As Scott pointed out, it's all about what udev has in its rules.]
You also have to look at /etc/udev/rules.d/70-persistent-net.rules
+1 Yes, udev rules for network devices needs modified.
(Learned that after cloning some VMs, where the hardware address was wrong.)
And I did too after cloning a physical machine to newer hardware. ;-)
-- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
You don't actually need hwaddr in your ifcfg-* files -- though it's probably not a bad thing to have the MAC in there. [As Scott pointed out, it's all about what udev has in its rules.]
You also have to look at /etc/udev/rules.d/70-persistent-net.rules
+1 Yes, udev rules for network devices needs modified.
(Learned that after cloning some VMs, where the hardware address was wrong.)
And I did too after cloning a physical machine to newer hardware. ;-)
I am using "centos 5" and it seems the "udev" cam in with e16 ... So can't go that way..
Something else to bother me is that lspci reports the ethernet device correctly. "Marvell Technology Group Ltd. 88E8001" but the "ifcfg-eth0"
# head -3 /etc/sysconfig/network-scripts/ifcfg-eth0
# D-Link System Inc DGE-528T Gigabit Ethernet Adapter DEVICE=eth0 ONBOOT=yes
# ethtool -i eth0
driver: skge version: 1.6
So it seems it is using the correct driver for "88E8001"
Steve
On Tue, Sep 03, 2013 at 02:02:08PM +0100, Steve Brooks wrote:
You don't actually need hwaddr in your ifcfg-* files -- though it's probably not a bad thing to have the MAC in there. [As Scott pointed out, it's all about what udev has in its rules.]
You also have to look at /etc/udev/rules.d/70-persistent-net.rules
I am using "centos 5" and it seems the "udev" cam in with e16 ... So can't go that way..
Cursory googling indicates that you can create the file (and directories if needed). The line in there would read something like
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="XX:XX:XX:XX:XX:XX", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
with XX:XX etc being the hardware address. It's all on one line and quotation marks are used as shown.
All this is untested by me on CentOS 5.x
On Tue, 3 Sep 2013, Scott Robbins wrote:
On Tue, Sep 03, 2013 at 02:02:08PM +0100, Steve Brooks wrote:
You don't actually need hwaddr in your ifcfg-* files -- though it's probably not a bad thing to have the MAC in there. [As Scott pointed out, it's all about what udev has in its rules.]
You also have to look at /etc/udev/rules.d/70-persistent-net.rules
I am using "centos 5" and it seems the "udev" cam in with e16 ... So can't go that way..
Cursory googling indicates that you can create the file (and directories if needed). The line in there would read something like
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="XX:XX:XX:XX:XX:XX", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
with XX:XX etc being the hardware address. It's all on one line and quotation marks are used as shown.
All this is untested by me on CentOS 5.x
Thanks Scott, I do have a test machine I can try it on, so I will see what happens with your suggestion.. Thanks, Steve
-
Markus Falb -
Scott Robbins -
SilverTip257 -
Steve Brooks