[SOLVED] bond interface doesn't work after update kernel

Issues related to configuring your network

[SOLVED] bond interface doesn't work after update kernel

Postby ALex_hha » 2011/12/25 21:43:48

Hello, it seems that new igb drivers including with kernel-2.6.18-274.* doesn't work correctly with bonding.

I have the following system

# uname -r
2.6.18-238.19.1.el5

# cat /etc/redhat-release
CentOS release 5.7 (Final)

# cat /etc/modprobe.conf | grep bond
alias bond0 bonding
options bond0 miimon=80 mode=2
#install bond0 /sbin/modprobe bonding -o bond0 mode=2 miimon=100
alias bond1 bonding
options bond1 miimon=80 mode=2
#install bond1 /sbin/modprobe bonding -o bond1 mode=2 miimon=100

bond0 used internal nic eth0 and eth1 (Intel(R) PRO/1000, e1000e)
bond1 used external nic eth2 and eth3 (Intel Gigabit ET Dual Port E1G42ETBLK, igb)

# modinfo /lib/modules/2.6.18-238.19.1.el5/kernel/drivers/net/igb/igb.ko | grep ^version
version: 2.1.0-k2-1

After I have updated kernel to 2.6.18-274.12.1.el5 and reboot server the network is not up. From console I saw lines something like during the system is booting:
ADDRCONF(NETDEV_UP): bond1: device doesn't exist
ADDRCONF(NETDEV_UP): bond1: link is not ready

After login ethtool show the following information

# ethtool bond1
Settings for bond1:
Link detected: no

# ifconfig bond1
bond1 Link encap:Ethernet HWaddr 00:1B:21:63:55:44
inet6 addr: fe80::21b:21ff:fe63:5544/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:10610766 errors:0 dropped:0 overruns:0 frame:0
TX packets:6304958 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8036660898 (2.9 MiB) TX bytes:1691931933 (2.9 MiB)

As I can see from the following output

# modinfo /lib/modules/2.6.18-274.12.1.el5/kernel/drivers/net/igb/igb.ko | grep ^version
version: 3.0.6-k2-1

The version of igb driver was changed from 2.x to 3.x. Аfter I rebooted the system and chose the 2.6.18-238 kernel all works fine again.

So my question is: is there any problem with igb v3?
ALex_hha
 
Posts: 89
Joined: 2010/04/07 13:02:13

Re: bond interface doesn't work after update kernel

Postby StinGer » 2011/12/26 19:55:14

Have you tried using the ifcfg-xxx config files in /etc/sysconfig/network-scripts/ ? I do personally use bonding on 3 NICs. For my physical NICs, I have the following ifcfg-ethn file :
Code: Select all
DEVICE=eth0
HWADDR=00:XX:XX:XX:XX:XX
ONBOOT=yes
MASTER=bond0
SLAVE=yes


And for ifcg-bond0 :
Code: Select all
DEVICE=bond0
BOOTPROTO=none
IPADDR=192.168.247.253
NETMASK=255.255.255.0
NETWORK=192.168.247.0
GATEWAY=192.168.247.254
ONBOOT=yes
USERCTL=no


I am running fine (but I am in mode 4).
StinGer
 
Posts: 46
Joined: 2008/11/13 01:24:14
Location: Universe > Milky Way > Solar System > Earth > France > Montrouge

Re: bond interface doesn't work after update kernel

Postby ALex_hha » 2011/12/26 22:20:03

Have you tried using the ifcfg-xxx config files in /etc/sysconfig/network-scripts/ ?

Of course I'm using this scripts

# cat /etc/sysconfig/network-scripts/ifcfg-eth2
# Intel Corporation 82576 Gigabit Network Connection
DEVICE=eth2
BOOTPROTO=none
ONBOOT=yes
MASTER=bond1
SLAVE=yes

# cat /etc/sysconfig/network-scripts/ifcfg-eth3
# Intel Corporation 82576 Gigabit Network Connection
DEVICE=eth3
BOOTPROTO=none
ONBOOT=yes
MASTER=bond1
SLAVE=yes

# cat /etc/sysconfig/network-scripts/ifcfg-bond1
DEVICE=bond1
ONBOOT=yes
BOOTPROTO=none

# cat /etc/sysconfig/network-scripts/ifcfg-bond1.210
# Intel Corporation 82576 Gigabit Network Connection
DEVICE=bond1.210
BOOTPROTO=none
IPADDR=192.168.210.1
NETMASK=255.255.255.0
ONBOOT=yes
VLAN=yes
ALex_hha
 
Posts: 89
Joined: 2010/04/07 13:02:13

Re: bond interface doesn't work after update kernel

Postby StinGer » 2011/12/28 19:12:16

OK, then try to stop the network, check the module is still loaded and up your network manually with ip and ifenslave. I would say it would look like this :
Code: Select all
/etc/init.d/network stop
ip l set lo up
ifenslave bond1 eth2
ifenslave bond1 eth3
vconfig add bond1 210
ip a add 192.168.210.1/24 dev bond1.210
ip l set eth2 up
ip l set eth3 up
ip l set bond1 up
ip l set bond1.210 up


So that you'll know where it fails exactly. What have you got about network in your syslog ?
StinGer
 
Posts: 46
Joined: 2008/11/13 01:24:14
Location: Universe > Milky Way > Solar System > Earth > France > Montrouge

Re: bond interface doesn't work after update kernel

Postby TrevorH » 2011/12/28 21:19:24

Could you post the output from

Code: Select all
lspci -nn
modinfo /lib/modules/2.6.18-238.19.1.el5/kernel/drivers/net/igb/igb.ko


I'm interested to know if the pci vendor/device ids are still listed as supported.
User avatar
TrevorH
Forum Moderator
 
Posts: 9147
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: bond interface doesn't work after update kernel

Postby ALex_hha » 2011/12/29 10:48:23

OK, then try to stop the network, check the module is still loaded and up your network manually with ip and ifenslave. I would say it would look like this

thanks, I will try

What have you got about network in your syslog ?

That what I have found in the /var/log/messages is very interesting.
As I told above, in my box I have 4 nic, eth0/eth1 is internal Intel Pro 1000 (e1000e) and eth2/eth3 is external Intel Gigabit ET Dual Port E1G42ETBLK (igb)
Code: Select all
# grep -E "(eth|bond)" /etc/modprobe.conf | grep -v ^#
alias bond0 bonding
options bond0 miimon=80 mode=2
alias bond1 bonding
options bond1 miimon=80 mode=2
alias eth0 e1000e
alias eth1 e1000e
alias eth2 igb
alias eth3 igb


Code: Select all
# dmesg | grep eth
eth0: (PCI Express:2.5GB/s:Width x1) 00:30:48:66:a1:fa
eth0: Intel(R) PRO/1000 Network Connection
eth0: MAC: 2, PHY: 2, PBA No: ffffff-0ff
eth1: (PCI Express:2.5GB/s:Width x1) 00:30:48:66:a1:fb
eth1: Intel(R) PRO/1000 Network Connection
eth1: MAC: 2, PHY: 2, PBA No: ffffff-0ff
igb 0000:03:00.0: eth2: (PCIe:2.5Gb/s:Width x4) 00:1b:21:63:55:44
igb 0000:03:00.0: eth2: PBA No: e43709-004
igb 0000:03:00.1: eth3: (PCIe:2.5Gb/s:Width x4) 00:1b:21:63:55:45
igb 0000:03:00.1: eth3: PBA No: e43709-004


I have rebooted server at Dec 25 18:02:51
Code: Select all
Dec 25 18:02:51 l3-core-hrk1 shutdown[5900]: shutting down for system reboot
Dec 25 18:02:51 l3-core-hrk1 init: Switching to runlevel: 6


And now it seems I found the cause of the problem
Code: Select all
Dec 25 18:07:18 l3-core-hrk1 kernel: igb 0000:03:00.0: Intel(R) Gigabit Ethernet Network Connection
Dec 25 18:07:18 l3-core-hrk1 kernel: igb 0000:03:00.0: eth0: (PCIe:2.5Gb/s:Width x4) 00:1b:21:63:55:44
Dec 25 18:07:18 l3-core-hrk1 kernel: igb 0000:03:00.0: eth0: PBA No: E43709-004
Dec 25 18:07:18 l3-core-hrk1 kernel: igb 0000:03:00.0: Using MSI-X interrupts. 4 rx queue(s), 1 tx queue(s)

Dec 25 18:07:18 l3-core-hrk1 kernel: igb 0000:03:00.1: 0 vfs allocated
Dec 25 18:07:18 l3-core-hrk1 kernel: igb 0000:03:00.1: Intel(R) Gigabit Ethernet Network Connection
Dec 25 18:07:18 l3-core-hrk1 kernel: igb 0000:03:00.1: eth1: (PCIe:2.5Gb/s:Width x4) 00:1b:21:63:55:45
Dec 25 18:07:18 l3-core-hrk1 kernel: igb 0000:03:00.1: eth1: PBA No: E43709-004
Dec 25 18:07:18 l3-core-hrk1 kernel: igb 0000:03:00.1: Using MSI-X interrupts. 4 rx queue(s), 1 tx queue(s)
Dec 25 18:07:18 l3-core-hrk1 kernel: PCI: Enabling device 0000:00:1f.3 (0001 -> 0003)

Dec 25 18:07:18 l3-core-hrk1 kernel: e1000e 0000:0d:00.0: Disabling ASPM  L1
Dec 25 18:07:18 l3-core-hrk1 kernel: e1000e 0000:0d:00.0: Disabling ASPM L0s
Dec 25 18:07:18 l3-core-hrk1 kernel: e1000e 0000:0d:00.0: eth2: (PCI Express:2.5GB/s:Width x1) 00:30:48:66:a1:fa
Dec 25 18:07:18 l3-core-hrk1 kernel: e1000e 0000:0d:00.0: eth2: Intel(R) PRO/1000 Network Connection
Dec 25 18:07:18 l3-core-hrk1 kernel: e1000e 0000:0d:00.0: eth2: MAC: 2, PHY: 2, PBA No: FFFFFF-0FF
Dec 25 18:07:18 l3-core-hrk1 kernel: e1000e 0000:0f:00.0: Disabling ASPM  L1

Dec 25 18:07:18 l3-core-hrk1 kernel: e1000e 0000:0f:00.0: Disabling ASPM L0s
Dec 25 18:07:18 l3-core-hrk1 kernel: e1000e 0000:0f:00.0: eth3: (PCI Express:2.5GB/s:Width x1) 00:30:48:66:a1:fb
Dec 25 18:07:18 l3-core-hrk1 kernel: e1000e 0000:0f:00.0: eth3: Intel(R) PRO/1000 Network Connection
Dec 25 18:07:18 l3-core-hrk1 kernel: e1000e 0000:0f:00.0: eth3: MAC: 2, PHY: 2, PBA No: FFFFFF-0FF

Why does it load igb driver for internal nic (eth0/eth1) and e1000e for external (eth2/eth3)? And because later the bond1 is not up correctly

Code: Select all
Dec 25 18:07:19 l3-core-hrk1 kernel: Ethernet Channel Bonding Driver: v3.4.0-1 (October 7, 2008)
Dec 25 18:07:19 l3-core-hrk1 kernel: bonding: MII link monitoring set to 80 ms
Dec 25 18:07:19 l3-core-hrk1 kernel: 8021q: adding VLAN 0 to HW filter on device bond0
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: bonding: bond0: Adding slave eth0.
Dec 25 18:07:19 l3-core-hrk1 kernel: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Dec 25 18:07:19 l3-core-hrk1 kernel: 8021q: adding VLAN 0 to HW filter on device eth0
Dec 25 18:07:19 l3-core-hrk1 kernel: bonding: bond0: enslaving eth0 as an active interface with an up link.
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Dec 25 18:07:19 l3-core-hrk1 kernel: bonding: bond0: Adding slave eth1.
Dec 25 18:07:19 l3-core-hrk1 kernel: igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Dec 25 18:07:19 l3-core-hrk1 kernel: 8021q: adding VLAN 0 to HW filter on device eth1
Dec 25 18:07:19 l3-core-hrk1 kernel: bonding: bond0: enslaving eth1 as an active interface with an up link.
Dec 25 18:07:19 l3-core-hrk1 kernel: bonding: bond1 is being created...
Dec 25 18:07:19 l3-core-hrk1 kernel: 8021q: adding VLAN 0 to HW filter on device bond1
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: bonding: bond1: Adding slave eth2.
Dec 25 18:07:19 l3-core-hrk1 kernel: 8021q: adding VLAN 0 to HW filter on device eth2
Dec 25 18:07:19 l3-core-hrk1 kernel: bonding: bond1: enslaving eth2 as an active interface with a down link.
Dec 25 18:07:19 l3-core-hrk1 kernel: bonding: bond1: Adding slave eth3.
Dec 25 18:07:19 l3-core-hrk1 kernel: 8021q: adding VLAN 0 to HW filter on device eth3
Dec 25 18:07:19 l3-core-hrk1 kernel: bonding: bond1: enslaving eth3 as an active interface with a down link.
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.100: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.1000: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.200: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.2000: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.201: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.202: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.203: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.204: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.205: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.206: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.207: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.208: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.209: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.210: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.211: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.212: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.213: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.214: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.215: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.3011: link is not ready
Dec 25 18:07:19 l3-core-hrk1 kernel: ADDRCONF(NETDEV_UP): bond1.3013: link is not ready


Could you post the output from

Code: Select all
# lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation 3200/3210 Chipset DRAM Controller [8086:29f0] (rev 01)
00:01.0 PCI bridge [0604]: Intel Corporation 3200/3210 Chipset Host-Primary PCI Express Bridge [8086:29f1] (rev 01)
00:06.0 PCI bridge [0604]: Intel Corporation 3210 Chipset Host-Secondary PCI Express Bridge [8086:29f9] (rev 01)
00:1a.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02)
00:1a.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02)
00:1a.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 02)
00:1a.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02)
00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 02)
00:1c.4 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 [8086:2948] (rev 02)
00:1c.5 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 [8086:294a] (rev 02)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 02)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 02)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 02)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 02)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 92)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801IR (ICH9R) LPC Interface Controller [8086:2916] (rev 02)
00:1f.2 IDE interface [0101]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 4 port SATA IDE Controller [8086:2920] (re)
00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 02)
00:1f.5 IDE interface [0101]: Intel Corporation 82801I (ICH9 Family) 2 port SATA IDE Controller [8086:2926] (rev 02)
00:1f.6 Signal processing controller [1180]: Intel Corporation 82801I (ICH9 Family) Thermal Subsystem [8086:2932] (rev)
01:00.0 PCI bridge [0604]: Intel Corporation 6702PXH PCI Express-to-PCI Bridge A [8086:032c] (rev 09)
01:00.1 PIC [0800]: Intel Corporation 6700/6702PXH I/OxAPIC Interrupt Controller A [8086:0326] (rev 09)
03:00.0 Ethernet controller [0200]: Intel Corporation 82576 Gigabit Network Connection [8086:10c9] (rev 01)
03:00.1 Ethernet controller [0200]: Intel Corporation 82576 Gigabit Network Connection [8086:10c9] (rev 01)
0d:00.0 Ethernet controller [0200]: Intel Corporation 82573E Gigabit Ethernet Controller (Copper) [8086:108c] (rev 03)
0f:00.0 Ethernet controller [0200]: Intel Corporation 82573L Gigabit Ethernet Controller [8086:109a]
11:03.0 VGA compatible controller [0300]: ATI Technologies Inc ES1000 [1002:515e] (rev 02)
11:04.0 IDE interface [0101]: Integrated Technology Express, Inc. IT8213 IDE Controller [1283:8213]


Code: Select all
# modinfo /lib/modules/2.6.18-238.19.1.el5/kernel/drivers/net/igb/igb.ko
filename:       /lib/modules/2.6.18-238.19.1.el5/kernel/drivers/net/igb/igb.ko
version:        2.1.0-k2-1
license:        GPL
description:    Intel(R) Gigabit Ethernet Network Driver
author:         Intel Corporation, <e1000-devel@lists.sourceforge.net>
srcversion:     53DE31944CEBA8B3896B7E8
alias:          pci:v00008086d000010D6sv*sd*bc*sc*i*
alias:          pci:v00008086d000010A9sv*sd*bc*sc*i*
alias:          pci:v00008086d000010A7sv*sd*bc*sc*i*
alias:          pci:v00008086d000010E8sv*sd*bc*sc*i*
alias:          pci:v00008086d00001526sv*sd*bc*sc*i*
alias:          pci:v00008086d0000150Dsv*sd*bc*sc*i*
alias:          pci:v00008086d000010E7sv*sd*bc*sc*i*
alias:          pci:v00008086d000010E6sv*sd*bc*sc*i*
alias:          pci:v00008086d00001518sv*sd*bc*sc*i*
alias:          pci:v00008086d0000150Asv*sd*bc*sc*i*
alias:          pci:v00008086d000010C9sv*sd*bc*sc*i*
alias:          pci:v00008086d00001516sv*sd*bc*sc*i*
alias:          pci:v00008086d00001511sv*sd*bc*sc*i*
alias:          pci:v00008086d00001510sv*sd*bc*sc*i*
alias:          pci:v00008086d0000150Fsv*sd*bc*sc*i*
alias:          pci:v00008086d0000150Esv*sd*bc*sc*i*
alias:          pci:v00008086d00001524sv*sd*bc*sc*i*
alias:          pci:v00008086d00001523sv*sd*bc*sc*i*
alias:          pci:v00008086d00001522sv*sd*bc*sc*i*
alias:          pci:v00008086d00001521sv*sd*bc*sc*i*
depends:        dca,8021q
vermagic:       2.6.18-238.19.1.el5 SMP mod_unload gcc-4.1
parm:           max_vfs:Maximum number of virtual functions to allocate per physical function (uint)
module_sig:     883f3504e202da181fdede8fe88d215112303a09f5a41fe5afba112841e59590f38f2b99fb47f53e09f415b58f7483232bf8c5c


Code: Select all
# modinfo /lib/modules/2.6.18-274.12.1.el5/kernel/drivers/net/igb/igb.ko
filename:       /lib/modules/2.6.18-274.12.1.el5/kernel/drivers/net/igb/igb.ko
version:        3.0.6-k2-1
license:        GPL
description:    Intel(R) Gigabit Ethernet Network Driver
author:         Intel Corporation, <e1000-devel@lists.sourceforge.net>
srcversion:     17F9D85F4FF5F020816E891
alias:          pci:v00008086d000010D6sv*sd*bc*sc*i*
alias:          pci:v00008086d000010A9sv*sd*bc*sc*i*
alias:          pci:v00008086d000010A7sv*sd*bc*sc*i*
alias:          pci:v00008086d000010E8sv*sd*bc*sc*i*
alias:          pci:v00008086d00001526sv*sd*bc*sc*i*
alias:          pci:v00008086d0000150Dsv*sd*bc*sc*i*
alias:          pci:v00008086d000010E7sv*sd*bc*sc*i*
alias:          pci:v00008086d000010E6sv*sd*bc*sc*i*
alias:          pci:v00008086d00001518sv*sd*bc*sc*i*
alias:          pci:v00008086d0000150Asv*sd*bc*sc*i*
alias:          pci:v00008086d000010C9sv*sd*bc*sc*i*
alias:          pci:v00008086d00000440sv*sd*bc*sc*i*
alias:          pci:v00008086d0000043Csv*sd*bc*sc*i*
alias:          pci:v00008086d0000043Asv*sd*bc*sc*i*
alias:          pci:v00008086d00000438sv*sd*bc*sc*i*
alias:          pci:v00008086d00001516sv*sd*bc*sc*i*
alias:          pci:v00008086d00001511sv*sd*bc*sc*i*
alias:          pci:v00008086d00001510sv*sd*bc*sc*i*
alias:          pci:v00008086d00001527sv*sd*bc*sc*i*
alias:          pci:v00008086d0000150Fsv*sd*bc*sc*i*
alias:          pci:v00008086d0000150Esv*sd*bc*sc*i*
alias:          pci:v00008086d00001524sv*sd*bc*sc*i*
alias:          pci:v00008086d00001523sv*sd*bc*sc*i*
alias:          pci:v00008086d00001522sv*sd*bc*sc*i*
alias:          pci:v00008086d00001521sv*sd*bc*sc*i*
depends:        dca,8021q
vermagic:       2.6.18-274.12.1.el5 SMP mod_unload gcc-4.1
parm:           max_vfs:Maximum number of virtual functions to allocate per physical function (uint)
module_sig:     883f3504ed52e21198c980dfcdbd44112b3e10a09c9d22b587825e4dcae816e37aae92936136c0a0b498621a51442fef7dc299a
ALex_hha
 
Posts: 89
Joined: 2010/04/07 13:02:13

Re: bond interface doesn't work after update kernel

Postby ALex_hha » 2011/12/29 11:27:41

From the following output it seems that new kernel enumerate PCI device other way than 2.6.18-238 does

Dec 25 18:07:18 l3-core-hrk1 kernel: igb 0000:03:00.0: eth0: (PCIe:2.5Gb/s:Width x4) 00:1b:21:63:55:44
Dec 25 18:07:18 l3-core-hrk1 kernel: igb 0000:03:00.1: eth1: (PCIe:2.5Gb/s:Width x4) 00:1b:21:63:55:45
Dec 25 18:07:18 l3-core-hrk1 kernel: e1000e 0000:0d:00.0: eth2: (PCI Express:2.5GB/s:Width x1) 00:30:48:66:a1:fa
Dec 25 18:07:18 l3-core-hrk1 kernel: e1000e 0000:0f:00.0: eth3: (PCI Express:2.5GB/s:Width x1) 00:30:48:66:a1:fb

Because now

# uname -r
2.6.18-238.19.1.el5

# dmesg | grep eth2
igb 0000:03:00.0: eth2: (PCIe:2.5Gb/s:Width x4) 00:1b:21:63:55:44
igb 0000:03:00.0: eth2: PBA No: e43709-004

# dmesg | grep eth3
igb 0000:03:00.1: eth3: (PCIe:2.5Gb/s:Width x4) 00:1b:21:63:55:45
igb 0000:03:00.1: eth3: PBA No: e43709-004

So my question is - How can I create mapping between name of the device and nic? So my external Intel Gigabit ET Dual Port E1G42ETBLK always be eth2/eth3
ALex_hha
 
Posts: 89
Joined: 2010/04/07 13:02:13

Re: bond interface doesn't work after update kernel

Postby TrevorH » 2011/12/29 12:34:47

On CentOS 6 there is a file /etc/udev/rules.d/70-persistent-net.rules that has udev rules in it to handle this sort of thing. I am not sure if the same rules will work on CentOS 5 but it could be worth a try as long as you have local access to the machine to revert the change in case it breaks it completely!

The content of the file looks like this:

Code: Select all
# PCI device 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="zz:zz:zz:zz:zz:zz", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x168c:0x002b (ath9k) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="zz:zz:zz:zz:zz:zz", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"


where zz:zz:zz:zz:zz:zz is the MAC address of each of the cards.
User avatar
TrevorH
Forum Moderator
 
Posts: 9147
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: bond interface doesn't work after update kernel

Postby ALex_hha » 2011/12/29 14:56:52

Can this issue caused by that I don't explicitly specify hw addresses in the /etc/sysconfig/network-scripts/ifcfg-ethX files
ALex_hha
 
Posts: 89
Joined: 2010/04/07 13:02:13

Re: bond interface doesn't work after update kernel

Postby TrevorH » 2011/12/29 18:01:35

That's certainly worth a try. Just add lines to those files

Code: Select all
HWADDR=zz:zz:zz:zz:zz:zz
User avatar
TrevorH
Forum Moderator
 
Posts: 9147
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Next

Return to CentOS 5 - Networking Support

Who is online

Users browsing this forum: No registered users and 2 guests