![两台思科交换机之间的 Linux 绑定故障转移问题](https://linux22.com/image/113211/%E4%B8%A4%E5%8F%B0%E6%80%9D%E7%A7%91%E4%BA%A4%E6%8D%A2%E6%9C%BA%E4%B9%8B%E9%97%B4%E7%9A%84%20Linux%20%E7%BB%91%E5%AE%9A%E6%95%85%E9%9A%9C%E8%BD%AC%E7%A7%BB%E9%97%AE%E9%A2%98.png)
我有上面的场景,其中服务器的bond0
接口连接到服务器的 SW1 和 SW2 相关接口,昨晚以某种方式SW1
重新启动,服务器失去eth0
连接,但每次交换机成功重新启动后,它也没有故障转移到 eth1 网络关闭,这发生在多台服务器上不是单身。所以最后我在所有服务器上重新启动网络以使其正常工作。我们已经primary=eth0
在 bond0 配置中进行了设置。
ifcfg-bond0
DEVICE=bond0
BOOTPROTO=none
ONBOOT=yes
BONDING_OPTS=mode=1 arp_interval=1000 arp_ip_target=192.168.10.1 miimon=500 downdelay=1000 primary=eth0 primary_reselect=always
NETMASK=255.255.255.0
IPADDR=192.168.10.20
GATEWAY=192.168.10.1
ifcfg-eth0
DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
ifcfg-eth1
DEVICE=eth1
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
这就是发生这种情况时我在日志中看到的内容
[root@server1 ~]# cat /var/log/messages | grep eth
Jun 8 05:03:05 [email protected] kernel: : bnx2 0000:02:00.0: eth0: NIC Copper Link is Down
Jun 8 05:03:05 [email protected] kernel: : bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 8 05:03:05 [email protected] kernel: : bonding: bond0: making interface eth1 the new active one.
Jun 8 05:07:03 [email protected] kernel: : bnx2 0000:02:00.0: eth0: NIC Copper Link is Up, 1000 Mbps full duplex
Jun 8 05:07:03 [email protected] kernel: : bonding: bond0: link status definitely up for interface eth0.
Jun 8 05:20:45 [email protected] kernel: : bonding: bond0: Removing slave eth0
Jun 8 05:20:45 [email protected] kernel: : bonding: bond0: Warning: the permanent HWaddr of eth0 - 18:A9:05:3A:39:1D - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts.
Jun 8 05:20:45 [email protected] kernel: : bonding: bond0: releasing backup interface eth0
Jun 8 05:20:46 [email protected] kernel: : bonding: bond0: Removing slave eth1
Jun 8 05:20:46 [email protected] kernel: : bonding: bond0: releasing active interface eth1
Jun 8 05:20:46 [email protected] kernel: : bonding: bond0: Adding slave eth0.
Jun 8 05:20:46 [email protected] kernel: : bnx2 0000:02:00.0: eth0: using MSIX
Jun 8 05:20:46 [email protected] kernel: : bonding: bond0: enslaving eth0 as a backup interface with a down link.
Jun 8 05:20:46 [email protected] kernel: : bonding: bond0: Adding slave eth1.
Jun 8 05:20:46 [email protected] kernel: : bnx2 0000:02:00.1: eth1: using MSIX
Jun 8 05:20:46 [email protected] kernel: : bonding: bond0: enslaving eth1 as a backup interface with a down link.
Jun 8 05:20:49 [email protected] kernel: : bnx2 0000:02:00.0: eth0: NIC Copper Link is Up, 1000 Mbps full duplex
Jun 8 05:20:49 [email protected] kernel: : bonding: bond0: link status definitely up for interface eth0.
Jun 8 05:20:49 [email protected] kernel: : bonding: bond0: making interface eth0 the new active one.
Jun 8 05:20:49 [email protected] kernel: : bnx2 0000:02:00.1: eth1: NIC Copper Link is Up, 1000 Mbps full duplex
Jun 8 05:20:50 [email protected] kernel: : bonding: bond0: link status definitely up for interface eth1.