[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Падает сетевое подключение при объединении в bond



Доброго всем времени!
Помогите выявить проблему в железе, либо в ПО...
Имеется двухпортовая сетевая Intel PRO/1000MT c PCI-X портом, установленная в порт с частотой 133Мгц.
Оба порта объединены в bond0-интерфейс:
====================console===============================
files ~ # cat /etc/network/interfaces
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto bond0 eth2 eth3
iface bond0 inet static
        address 10.0.0.11
        netmask 255.255.255.0
        gateway 10.0.0.254
        bond-slaves none
        bond-mode balance-alb
        bond-downdelay 200
        bond-updelay 200

allow-hotplug eth2
iface eth2 inet manual
        bond-master bond0
        bond-primary eth2 eth3

allow-hotplug eth3
iface eth3 inet manual
        bond-master bond0
        bond-primary eth2 eth3
files ~ # cat /etc/modprobe.d/aliases-bond.conf
alias bond0 bonding
        options bonding arp_interval=200 arp_ip_target=10.0.0.1,10.0.0.4

files ~ # ifconfig
bond0     Link encap:Ethernet  HWaddr 00:07:e9:a5:14:f7
          inet addr:10.0.0.11  Bcast:10.0.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:44564 errors:0 dropped:0 overruns:0 frame:0
          TX packets:47089 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:8311464 (7.9 MiB)  TX bytes:39156386 (37.3 MiB)

eth2      Link encap:Ethernet  HWaddr 00:07:e9:a5:14:f7
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:31352 errors:0 dropped:0 overruns:0 frame:0
          TX packets:37836 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5245222 (5.0 MiB)  TX bytes:38583024 (36.7 MiB)

eth3      Link encap:Ethernet  HWaddr 00:07:e9:a5:14:f6
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:13212 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9253 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3066242 (2.9 MiB)  TX bytes:573362 (559.9 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:31 errors:0 dropped:0 overruns:0 frame:0
          TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2568 (2.5 KiB)  TX bytes:2568 (2.5 KiB)
====================console===============================
При этом, если я физически вынимаю и вставляю провод из какого-либо интерфейса, на консоль валятся сообщения:
http://www.k-max.name/wp-content/uploads/2011/08/errors.jpg
При этом, один из интерфесов горит красным цветом, хотя в документации к сетевушке это не описано:
http://www.k-max.name/wp-content/uploads/2011/08/red_link.jpg
Во время "передергивания" интерфейса (физическим изъятием провода) в messages куча сообщений:
====================console===============================
Aug 5 18:40:25 files kernel: [ 9.912383] e1000: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Aug 5 18:40:25 files kernel: [ 9.925118] bonding: bond0: Warning: failed to get speed and duplex from eth3, assumed to be 100Mb/sec and Full. Aug 5 18:40:25 files kernel: [ 9.925149] bonding: bond0: enslaving eth3 as an active interface with an up link. Aug 5 18:40:25 files kernel: [ 9.925164] bonding: bond0: Setting eth2 as primary slave. Aug 5 18:40:25 files kernel: [ 9.930836] bonding: bond0: Setting eth2 as primary slave. Aug 5 18:40:25 files kernel: [ 9.944397] e1000: eth3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Aug 5 18:40:25 files kernel: [ 11.180611] lp0: using parport0 (interrupt-driven). Aug 5 18:40:25 files kernel: [ 11.197377] ppdev: user-space parallel port driver
Aug  5 18:42:57 files kernel: [  162.492113] e1000: eth2 NIC Link is Down
Aug 5 18:43:01 files kernel: [ 167.300017] bonding: bond0: interface eth2 is now down. Aug 5 18:43:01 files kernel: [ 167.300030] bonding: bond0: making interface eth3 the new active one. Aug 5 18:43:01 files kernel: [ 167.300253] Pid: 848, comm: bond0 Not tainted 2.6.32-5-686 #1
Aug  5 18:43:01 files kernel: [  167.300258] Call Trace:
Aug 5 18:43:01 files kernel: [ 167.300276] [<f8234266>] ? bond_alb_handle_active_change+0xec/0x158 [bonding] Aug 5 18:43:01 files kernel: [ 167.300286] [<f822f23e>] ? bond_change_active_slave+0x1dc/0x42b [bonding] Aug 5 18:43:01 files kernel: [ 167.300299] [<c126d49e>] ? schedule+0x78f/0x7dc Aug 5 18:43:01 files kernel: [ 167.300308] [<f822f7a8>] ? bond_select_active_slave+0x86/0xb4 [bonding] Aug 5 18:43:01 files kernel: [ 167.300317] [<f822fe10>] ? bond_loadbalance_arp_mon+0x186/0x1b8 [bonding] Aug 5 18:43:01 files kernel: [ 167.300327] [<c10412f7>] ? worker_thread+0x141/0x1bd Aug 5 18:43:01 files kernel: [ 167.300336] [<f822fc8a>] ? bond_loadbalance_arp_mon+0x0/0x1b8 [bonding] Aug 5 18:43:01 files kernel: [ 167.300345] [<c104403a>] ? autoremove_wake_function+0x0/0x2d Aug 5 18:43:01 files kernel: [ 167.300351] [<c10411b6>] ? worker_thread+0x0/0x1bd Aug 5 18:43:01 files kernel: [ 167.300358] [<c1043e08>] ? kthread+0x61/0x66 Aug 5 18:43:01 files kernel: [ 167.300365] [<c1043da7>] ? kthread+0x0/0x66 Aug 5 18:43:01 files kernel: [ 167.300374] [<c1003d47>] ? kernel_thread_helper+0x7/0x10 Aug 5 18:43:01 files kernel: [ 167.300475] Pid: 848, comm: bond0 Not tainted 2.6.32-5-686 #1
Aug  5 18:43:01 files kernel: [  167.300932] Call Trace:
Aug 5 18:43:01 files kernel: [ 167.300941] [<c121836f>] ? inetdev_event+0x40/0x3c3 Aug 5 18:43:01 files kernel: [ 167.300950] [<c11f39e6>] ? rt_cache_flush+0x13f/0x161 Aug 5 18:43:01 files kernel: [ 167.300957] [<c12702c8>] ? notifier_call_chain+0x2a/0x47 Aug 5 18:43:01 files kernel: [ 167.300964] [<c10476ce>] ? raw_notifier_call_chain+0x9/0xc Aug 5 18:43:01 files kernel: [ 167.300971] [<c11da5ea>] ? dev_set_mac_address+0x4d/0x52 Aug 5 18:43:01 files kernel: [ 167.300981] [<f8233933>] ? alb_set_slave_mac_addr+0x68/0xa2 [bonding] Aug 5 18:43:01 files kernel: [ 167.300991] [<f82339a7>] ? alb_swap_mac_addr+0x3a/0x4f [bonding] Aug 5 18:43:01 files kernel: [ 167.301000] [<f823427c>] ? bond_alb_handle_active_change+0x102/0x158 [bonding] Aug 5 18:43:01 files kernel: [ 167.301009] [<f822f23e>] ? bond_change_active_slave+0x1dc/0x42b [bonding] Aug 5 18:43:01 files kernel: [ 167.301017] [<c126d49e>] ? schedule+0x78f/0x7dc Aug 5 18:43:01 files kernel: [ 167.301025] [<f822f7a8>] ? bond_select_active_slave+0x86/0xb4 [bonding] Aug 5 18:43:01 files kernel: [ 167.301034] [<f822fe10>] ? bond_loadbalance_arp_mon+0x186/0x1b8 [bonding] Aug 5 18:43:01 files kernel: [ 167.301041] [<c10412f7>] ? worker_thread+0x141/0x1bd Aug 5 18:43:01 files kernel: [ 167.301049] [<f822fc8a>] ? bond_loadbalance_arp_mon+0x0/0x1b8 [bonding] Aug 5 18:43:01 files kernel: [ 167.301056] [<c104403a>] ? autoremove_wake_function+0x0/0x2d Aug 5 18:43:01 files kernel: [ 167.301062] [<c10411b6>] ? worker_thread+0x0/0x1bd Aug 5 18:43:01 files kernel: [ 167.301068] [<c1043e08>] ? kthread+0x61/0x66 Aug 5 18:43:01 files kernel: [ 167.301074] [<c1043da7>] ? kthread+0x0/0x66 Aug 5 18:43:01 files kernel: [ 167.301081] [<c1003d47>] ? kernel_thread_helper+0x7/0x10
.......
Aug 5 18:43:01 files kernel: [ 167.302048] Pid: 848, comm: bond0 Not tainted 2.6.32-5-686 #1
Aug  5 18:43:01 files kernel: [  167.302052] Call Trace:
Aug 5 18:43:01 files kernel: [ 167.302059] [<c11d8778>] ? __dev_set_promiscuity+0x2f/0x128 Aug 5 18:43:01 files kernel: [ 167.302066] [<c11d8c47>] ? dev_set_promiscuity+0x10/0x2e Aug 5 18:43:01 files kernel: [ 167.302075] [<f8233dcd>] ? rlb_teach_disabled_mac_on_primary+0x22/0x44 [bonding] Aug 5 18:43:01 files kernel: [ 167.302084] [<f8234288>] ? bond_alb_handle_active_change+0x10e/0x158 [bonding] Aug 5 18:43:01 files kernel: [ 167.302093] [<f822f23e>] ? bond_change_active_slave+0x1dc/0x42b [bonding] Aug 5 18:43:01 files kernel: [ 167.302101] [<c126d49e>] ? schedule+0x78f/0x7dc Aug 5 18:43:01 files kernel: [ 167.302109] [<f822f7a8>] ? bond_select_active_slave+0x86/0xb4 [bonding] Aug 5 18:43:01 files kernel: [ 167.302118] [<f822fe10>] ? bond_loadbalance_arp_mon+0x186/0x1b8 [bonding] Aug 5 18:43:01 files kernel: [ 167.302125] [<c10412f7>] ? worker_thread+0x141/0x1bd Aug 5 18:43:01 files kernel: [ 167.302134] [<f822fc8a>] ? bond_loadbalance_arp_mon+0x0/0x1b8 [bonding] Aug 5 18:43:01 files kernel: [ 167.302141] [<c104403a>] ? autoremove_wake_function+0x0/0x2d Aug 5 18:43:01 files kernel: [ 167.302147] [<c10411b6>] ? worker_thread+0x0/0x1bd Aug 5 18:43:01 files kernel: [ 167.302153] [<c1043e08>] ? kthread+0x61/0x66 Aug 5 18:43:01 files kernel: [ 167.302159] [<c1043da7>] ? kthread+0x0/0x66 Aug 5 18:43:01 files kernel: [ 167.302165] [<c1003d47>] ? kernel_thread_helper+0x7/0x10 Aug 5 18:43:01 files kernel: [ 167.302170] device eth3 entered promiscuous mode Aug 5 18:43:02 files kernel: [ 168.024374] e1000: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Aug 5 18:43:11 files kernel: [ 177.296030] device eth3 left promiscuous mode Aug 5 18:43:33 files kernel: [ 199.300018] bonding: bond0: interface eth2 is now up
Aug  5 18:43:45 files kernel: [  211.140114] e1000: eth2 NIC Link is Down
Aug 5 18:43:49 files kernel: [ 215.300017] bonding: bond0: interface eth2 is now down. Aug 5 18:43:51 files kernel: [ 217.332372] e1000: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Aug  5 18:44:00 files kernel: [  226.364113] e1000: eth3 NIC Link is Down
Aug 5 18:44:05 files kernel: [ 231.300021] bonding: bond0: interface eth3 is now down. Aug 5 18:44:05 files kernel: [ 231.300088] bonding: bond0: now running without any active interface ! Aug 5 18:44:07 files kernel: [ 232.980372] e1000: eth3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Aug 5 18:44:23 files kernel: [ 249.300014] bonding: bond0: link status definitely up for interface eth2, Aug 5 18:44:23 files kernel: [ 249.300034] bonding: bond0: making interface eth2 the new active one. Aug 5 18:44:23 files kernel: [ 249.300225] Pid: 848, comm: bond0 Not tainted 2.6.32-5-686 #1
Aug  5 18:44:23 files kernel: [  249.300230] Call Trace:
Aug 5 18:44:23 files kernel: [ 249.300248] [<f8234266>] ? bond_alb_handle_active_change+0xec/0x158 [bonding] Aug 5 18:44:23 files kernel: [ 249.300258] [<f822f23e>] ? bond_change_active_slave+0x1dc/0x42b [bonding] Aug 5 18:44:23 files kernel: [ 249.300270] [<c126d49e>] ? schedule+0x78f/0x7dc Aug 5 18:44:23 files kernel: [ 249.300279] [<f822f7a8>] ? bond_select_active_slave+0x86/0xb4 [bonding] Aug 5 18:44:23 files kernel: [ 249.300288] [<f822fe10>] ? bond_loadbalance_arp_mon+0x186/0x1b8 [bonding] Aug 5 18:44:23 files kernel: [ 249.300299] [<c10412f7>] ? worker_thread+0x141/0x1bd Aug 5 18:44:23 files kernel: [ 249.300307] [<f822fc8a>] ? bond_loadbalance_arp_mon+0x0/0x1b8 [bonding] Aug 5 18:44:23 files kernel: [ 249.300316] [<c104403a>] ? autoremove_wake_function+0x0/0x2d
====================console===============================
при этом, если интерфейсы опускать и поднимать через ifdown/ifup, то такой проблемы нет.

Данные системы:
Debian Release: 6.0.2
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
установлен ifenslave-2.6.

Заранее спасибо!


Reply to: