[sles-beta] SLES12 RC1 wicked configuration ETHTOOL_OPTIONS=autoneg on = NIC does not come up

[urs.frey at post.ch]

Hello Pawel

I had a closer look at this issue:

VMWare ESXi = the virtual interface does allow to use ETHTOOL_OPTIONS, wicked will start the NIC here, no problem
============
v03er9:~ # /usr/sbin/dmidecode | awk '/Product Name:/ {print $4$5}'
VirtualPlatform
DesktopReference
v03er9:~ # lspci | grep Ether
02:00.0 Ethernet controller: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 01)
v03er9:~ # ethtool -s eth0 autoneg on
v03er9:~ # cat /etc/sysconfig/network/ifcfg-eth0
BOOTPROTO='static'
STARTMODE='auto'
IPADDR='10.1.100.167'
NETMASK='255.255.254.0'
NAME='82545EM Gigabit Ethernet Controller (Copper)'
ETHTOOL_OPTIONS='autoneg on'
PREFIXLEN='23'
v03er9:~ #

=> Here wicked does start the network interface, no problem.


KVM = the virtual interface does technically not allow to use ETHTOOL_OPTIONS, because it is a virtual interface. No settings possible
==============
h05cnh:~ # /usr/sbin/dmidecode | awk '/Product Name:/ {print $4$5}'
PC(i440FX
h05cnh:~ # lspci | grep Ether
00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
h05cnh:~ # ethtool -s eth0 autoneg on
Cannot get current device settings: Operation not supported
  not setting autoneg
h05cnh:~ #
h05cnh:~ # cat /etc/sysconfig/network/ifcfg-eth0
BOOTPROTO='static'
STARTMODE='auto'
IPADDR='10.226.169.28/24'
BROADCAST='10.226.169.255'
PREFIXLEN='24'
h05cnh:~ #

=> Here Wicked runs into a General Failure, NIC will not be started

==============

HP Proliant Blade Server with Converged Network Adapter = This interface does not allow to set ETHTOOL_OPTIONS, No settings possible.
=======
h05cni:~ # /usr/sbin/dmidecode | awk '/Product Name:/ {print $4$5}'
BL460cGen8
h05cni:~ # lspci | grep Ether
04:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 01)
04:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 01)
h05cni:~ # ethtool -s eth0 autoneg on
Cannot set new settings: Operation not supported
  not setting autoneg
h05cni:~ #
h05cni:~ # cat /etc/sysconfig/network/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=none
ETHTOOL_OPTIONS=''
STARTMODE='hotplug'
MASTER=bond0
SLAVE=yes
h05cni:~ #

=> Here Wicked runs into a General Failure, NIC will not be started


=======
BUT:
HP Proliant DL380-G7, Broadcom Nextreme II BCM5709 Gigabit Ethernet = This interface does allow setting of ETHTOOL_OPTIONS
h063uz:~ # /usr/sbin/dmidecode | awk '/Product Name:/ {print $4$5}'
DL380G7
h063uz:~ # lspci | grep Ether
03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
h063uz:~ # ethtool -s eth1 autoneg on
h063uz:~ #
h063uz:~ # cat /etc/sysconfig/network/ifcfg-eth0
BOOTPROTO='static'
STARTMODE='auto'
IPADDR='10.226.154.19/23'
BROADCAST='10.226.155.255'
ETHTOOL_OPTIONS='autoneg on'
PREFIXLEN='23'
h063uz:~ #

=> Here wicked does start the NIC, no problem


CONCLUSION:
===========
On all server installations, where ETHTOOL causes an error if trying to set autoneg on,  wicked runs into an error.

With the old network configuration, this error got ignored and the network interface got started anyway.
Let us say focus on correct IP configuration.

So I can imagine, that wicked now is more sensible to configuration errors, which somehow is correct and consequent 

Best regards


Urs Frey                                              
Post CH AG
Informationstechnologie
IT Betrieb 
Webergutstrasse 12 
3030 Bern (Zollikofen) 
Telefon : ++41 (0)58 338 58 70 
FAX     : ++41 (0)58 667 30 07 
E-Mail:   urs.frey at post.ch


-----Ursprüngliche Nachricht-----
Von: Pawel Wieczorkiewicz [mailto:pwieczorkiewicz at suse.de] 
Gesendet: Friday, August 08, 2014 4:09 PM
An: Frey Urs, IT222; Karol Mroz
Betreff: Re: [sles-beta] SLES12 RC1 wicked configuration ETHTOOL_OPTIONS=autoneg on = NIC does not come up

On Fri, 8 Aug 2014 14:01:43 +0000
<urs.frey at post.ch> wrote:

> Hello Pawel
> 
> Please find in the attachment a tarball containing config.log,
> status.log, wicked.log and messages
> 
> I booted the KVM client with ETHTOO_OPTION='autoneg on'
> Then I collected the logs
> ‒ set DEBUG=all in /etc/sysconfig/network/config
> ‒ systemctl restart wickedd
> ‒ wicked ifstatus all > status.log
> ‒ wicked show-config > configs.log
> ‒ journalctl -b -o short-iso > wicked.log
> 


Hello,

Are you testing ETHTOOLs options only in KVM env or also on physical
interfaces? From my experience KVM drivers for ethernet nics do not
support ethtool options very well, and they are pretty unstable with
them (sometimes they work, sometimes they lose the changes).

We will look into the logs. Thank you for sending them.

-- 
Best Regards,
Pawel Wieczorkiewicz <pwieczorkiewicz at suse.de>, Linux System Developer
SUSE LINUX Products GmbH
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG
Nürnberg) Maxfeldstr. 5 / D-90409 Nürnberg / Phone: +49-911-740 53 - 613