绑定无法正常工作(CentOS 5.4,Intel 10G,802.3ad)

前端之家收集整理的这篇文章主要介绍了绑定无法正常工作(CentOS 5.4,Intel 10G,802.3ad)前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。
我们使用带有两个端口的英特尔网络适配器X540配置了网络绑定.两个端口都连接到具有已配置LACP中继的Brocade交换机. Everthing似乎工作得很好;但是当我们物理断开两个端口时,绑定接口的状态仍然是正常的!链接状态应该是关闭的,不是吗?我们无法ping或连接到此接口;连接一个或两个从端口后,一切都很好.

有任何想法吗?

  1. [root@er ~]# cat /proc/net/bonding/bond0
  2. Ethernet Channel Bonding Driver: v3.4.0 (October 7,2008)
  3.  
  4. Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  5. Transmit Hash Policy: layer2 (0)
  6. MII Status: up
  7. MII Polling Interval (ms): 100
  8. Up Delay (ms): 0
  9. Down Delay (ms): 0
  10.  
  11. 802.3ad info
  12. LACP rate: slow
  13. Active Aggregator Info:
  14. Aggregator ID: 1
  15. Number of ports: 2
  16. Actor Key: 0
  17. Partner Key: 1
  18. Partner Mac Address: 00:00:00:00:00:00
  19.  
  20. Slave Interface: eth2
  21. MII Status: down
  22. Link Failure Count: 1
  23. Permanent HW addr: 90:e2:ba:37:41:28
  24. Aggregator ID: 1
  25.  
  26. Slave Interface: eth3
  27. MII Status: down
  28. Link Failure Count: 1
  29. Permanent HW addr: 90:e2:ba:37:41:29
  30. Aggregator ID: 1
  1. [root@er ~]# ethtool bond0
  2. Settings for bond0:
  3. Link detected: yes
  1. [root@er ~]# ethtool eth2
  2. Settings for eth2:
  3. Supported ports: [ FIBRE ]
  4. Supported link modes: 1000baseT/Full
  5. Supports auto-negotiation: Yes
  6. Advertised link modes: 1000baseT/Full
  7. 10000baseT/Full
  8. Advertised auto-negotiation: Yes
  9. Speed: Unknown! (65535)
  10. Duplex: Unknown! (255)
  11. Port: FIBRE
  12. PHYAD: 0
  13. Transceiver: external
  14. Auto-negotiation: on
  15. Supports Wake-on: d
  16. Wake-on: d
  17. Current message level: 0x00000007 (7)
  18. Link detected: no
  1. [root@er ~]# ethtool eth3
  2. Settings for eth3:
  3. Supported ports: [ FIBRE ]
  4. Supported link modes: 1000baseT/Full
  5. Supports auto-negotiation: Yes
  6. Advertised link modes: 1000baseT/Full
  7. 10000baseT/Full
  8. Advertised auto-negotiation: Yes
  9. Speed: Unknown! (65535)
  10. Duplex: Unknown! (255)
  11. Port: FIBRE
  12. PHYAD: 0
  13. Transceiver: external
  14. Auto-negotiation: on
  15. Supports Wake-on: d
  16. Wake-on: d
  17. Current message level: 0x00000007 (7)
  18. Link detected: no
  1. [root@er ~]# cat /etc/modprobe.conf
  2. ...
  3. alias eth2 ixgbe
  4. alias eth3 ixgbe
  5. alias bond0 bonding
  6. options bond0 mode=4 miimon=100
  1. [root@er ~]# modinfo ixgbe
  2. filename: /lib/modules/2.6.18-164.el5/kernel/drivers/net/ixgbe/ixgbe.ko
  3. version: 3.11.33
  4. license: GPL
  5. description: Intel(R) 10 Gigabit PCI Express Network Driver
  6. author: Intel Corporation,<linux.nics@intel.com>
  7. srcversion: 739E88C99BF8038F878AE91
  8. ...
  1. [root@er ~]# cat /etc/sysconfig/network-scripts/ifcfg-bond0
  2. DEVICE=bond0
  3. IPADDR=192.168.100.23
  4. NETMASK=255.255.255.0
  5. NETWORK=192.168.100.0
  6. GATEWAY=192.168.100.1
  7. ONBOOT=yes
  8. BOOTPROTO=none
  9. USERCTL=no
  10. IPV6INIT=no
  11. [root@er ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth2
  12. DEVICE=eth2
  13. BOOTPROTO=none
  14. ONBOOT=yes
  15. MASTER=bond0
  16. SLAVE=yes
  17. USERCTL=no
  18. HWADDR=90:e2:ba:37:41:28
  19. [root@er ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth3
  20. DEVICE=eth3
  21. BOOTPROTO=none
  22. ONBOOT=yes
  23. MASTER=bond0
  24. SLAVE=yes
  25. USERCTL=no
  26. HWADDR=90:e2:ba:37:41:29
  1. [root@er ~]# uname -a
  2. Linux er.dve.intern 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
  1. [root@er ~]# tail /var/log/messages
  2. Feb 25 18:11:42 er kernel: ixgbe 0000:0a:00.0: eth2: NIC Link is Down
  3. Feb 25 18:11:42 er kernel: bonding: bond0: link status definitely down for interface eth2,disabling it
  4. Feb 25 18:11:43 er kernel: ixgbe 0000:0a:00.1: eth3: NIC Link is Down
  5. Feb 25 18:11:43 er kernel: bonding: bond0: link status definitely down for interface eth3,disabling it
  6. Feb 25 18:11:43 er kernel: bonding: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond
您的输出显示ethtool认为您的两个接口都已关闭(绑定模块也是如此). Google“bonding.txt”并阅读内核的绑定文档,特别是有关链接监控的第7节(和第7.3节).既然看起来ethtool无法确定你的接口是否正常运行,因此绑定驱动程序也不能,或者尝试使用’use_carrier = 0’会有帮助吗?或者尝试使用arp监控模式而不是miimon?

编辑:我的道歉,我想我错误地读了你的问题…看起来你的命令输出是你拔掉你的NIC的时间段,你想知道为什么bond0仍然说它已经出现了?我不知道有什么有用的.我仍然建议使用bonding.txt作为所有“linux bonding”的圣经但是:)

猜你在找的CentOS相关文章