centos7服務器進行雙網卡綁定
配置文件
#cat ifcfg-em1 TYPE=Ethernet BOOTPROTO=none DEFROUTE=yes NAME=em1 DEVICE=em1 ONBOOT=yes MASTER=bond0 SLAVE=yes # cat ifcfg-em2 TYPE=Ethernet BOOTPROTO=none IPV4_FAILURE_FATAL=no NAME=em2 ONBOOT=yes MASTER=bond0 SLAVE=yes # cat ifcfg-bond0 TYPE=Ethernet BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=no NAME=bond0 DEVICE=bond0 ONBOOT=yes DNS1=223.5.5.5 IPADDR=*.*.*.* PREFIX=24 GATEWAY=*.*.*.* # cat /etc/modprobe.d/bond0.conf alias bond0 bonding options bond0 miimon=100 mode=1 重啓網卡發現配置沒生效。 查看message日誌 Aug 31 21:54:24 localhost systemd: Stopping LSB: Bring up/down networking... Aug 31 21:54:25 localhost NetworkManager[1115]: <info> [1504187665.0955] ifcfg-rh: update /etc/sysconfig/network-scripts/ifcfg-em1 (1dad842d-1912-ef5a-a43a-bc238fb267e7,"em1") Aug 31 21:54:25 localhost NetworkManager[1115]: <info> [1504187665.2204] device (em1): state change: activated -> deactivating (reason 'user-requested') [100 110 39] Aug 31 21:54:25 localhost NetworkManager[1115]: <info> [1504187665.2206] manager: NetworkManager state is now DISCONNECTING Aug 31 21:54:25 localhost dbus[1114]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Aug 31 21:54:25 localhost dbus-daemon: dbus[1114]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Aug 31 21:54:25 localhost systemd: Starting Network Manager Script Dispatcher Service... Aug 31 21:54:25 localhost dbus[1114]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Aug 31 21:54:25 localhost dbus-daemon: dbus[1114]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Aug 31 21:54:25 localhost nm-dispatcher: req:1 'connectivity-change': new request (2 scripts) Aug 31 21:54:25 localhost systemd: Started Network Manager Script Dispatcher Service. Aug 31 21:54:25 localhost nm-dispatcher: req:1 'connectivity-change': start running ordered scripts... Aug 31 21:54:25 localhost NetworkManager[1115]: <info> [1504187665.2323] audit: op="device-disconnect" interface="em1" ifindex=2 pid=14176 uid=0 result="success" Aug 31 21:54:25 localhost NetworkManager[1115]: <info> [1504187665.2333] device (em1): state change: deactivating -> disconnected (reason 'user-requested') [110 30 39] Aug 31 21:54:25 localhost NetworkManager[1115]: <info> [1504187665.2449] manager: NetworkManager state is now DISCONNECTED Aug 31 21:54:25 localhost nm-dispatcher: req:2 'down' [em1]: new request (2 scripts) Aug 31 21:54:25 localhost nm-dispatcher: req:2 'down' [em1]: start running ordered scripts... Aug 31 21:54:25 localhost network: Shutting down interface em1: Device 'em1' successfully disconnected. Aug 31 21:54:25 localhost network: [ OK ] Aug 31 21:54:25 localhost NetworkManager[1115]: <info> [1504187665.3211] ifcfg-rh: update /etc/sysconfig/network-scripts/ifcfg-em2 (0578038a-64e9-a2fd-0a28-e4cd0b553930,"em2") Aug 31 21:54:25 localhost NetworkManager[1115]: <info> [1504187665.3220] policy: auto-activating connection 'em2' Aug 31 21:54:25 localhost network: Shutting down interface em2: ERROR : [ipv6_test_device_status] Missing parameter 'device' (arg 1) Aug 31 21:54:25 localhost ipv6_test_device_status: Missing parameter 'device' (arg 1) Aug 31 21:54:25 localhost network: /etc/sysconfig/network-scripts/ifdown-eth: line 121: /sys/class/net/bond0/bonding/slaves: No such file or directory Aug 31 21:54:25 localhost network: [ OK ] Aug 31 21:54:26 localhost network: Shutting down interface em3: [ OK ] Aug 31 21:54:26 localhost network: Shutting down interface em4: [ OK ] Aug 31 21:54:26 localhost network: Shutting down loopback interface: [ OK ] Aug 31 21:54:26 localhost systemd: Starting LSB: Bring up/down networking... Aug 31 21:54:26 localhost NetworkManager[1115]: <info> [1504187666.6322] ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-bond0 (ad33d8b0-1f7b-cab9-9447-ba07f855b143,"bond0") Aug 31 21:54:26 localhost NetworkManager[1115]: <info> [1504187666.6327] policy: auto-activating connection 'em2' Aug 31 21:54:26 localhost NetworkManager[1115]: <info> [1504187666.7241] device (lo): link connected Aug 31 21:54:26 localhost network: Bringing up loopback interface: [ OK ] Aug 31 21:54:27 localhost NetworkManager[1115]: <info> [1504187667.0860] policy: auto-activating connection 'em2' Aug 31 21:54:27 localhost NetworkManager[1115]: <info> [1504187667.0871] audit: op="connection-activate" uuid="ad33d8b0-1f7b-cab9-9447-ba07f855b143" name="bond0" result="fail" reason="No suitable device found for this connection." Aug 31 21:54:27 localhost network: Bringing up interface bond0: Error: Connection activation failed: No suitable device found for this connection. Aug 31 21:54:27 localhost network: [FAILED] Aug 31 21:54:27 localhost NetworkManager[1115]: <info> [1504187667.2963] policy: auto-activating connection 'em2' Aug 31 21:54:27 localhost NetworkManager[1115]: <info> [1504187667.2976] audit: op="connection-activate" uuid="1dad842d-1912-ef5a-a43a-bc238fb267e7" name="em1" pid=14650 uid=0 result="fail" reason="Can not find a master for em1: Master connection not found or invalid" Aug 31 21:54:27 localhost network: Bringing up interface em1: Error: Connection activation failed: Can not find a master for em1: Master connection not found or invalid Aug 31 21:54:27 localhost network: [FAILED] Aug 31 21:54:27 localhost NetworkManager[1115]: <info> [1504187667.4642] policy: auto-activating connection 'em2' Aug 31 21:54:27 localhost NetworkManager[1115]: <info> [1504187667.4655] audit: op="connection-activate" uuid="0578038a-64e9-a2fd-0a28-e4cd0b553930" name="em2" pid=14682 uid=0 result="fail" reason="Can not find a master for em2: Master connection not found or invalid" Aug 31 21:54:27 localhost network: Bringing up interface em2: Error: Connection activation failed: Can not find a master for em2: Master connection not found or invalid Aug 31 21:54:27 localhost network: [FAILED] Aug 31 21:54:27 localhost systemd: network.service: control process exited, code=exited status=1 Aug 31 21:54:27 localhost systemd: Failed to start LSB: Bring up/down networking. Aug 31 21:54:27 localhost systemd: Unit network.service entered failed state. Aug 31 21:54:27 localhost systemd: network.service failed. NetworkManager不識別 bond0設備 關閉NetworkManager以後，重啓網絡服務 Aug 31 21:57:47 localhost systemd: Stopped Network Manager Wait Online. Aug 31 21:57:47 localhost NetworkManager[1115]: <info> [1504187867.5810] caught SIGTERM, shutting down normally. Aug 31 21:57:47 localhost systemd: Stopping Network Manager Wait Online... Aug 31 21:57:47 localhost systemd: Stopping Network Manager... Aug 31 21:57:47 localhost NetworkManager[1115]: <info> [1504187867.6005] exiting (success) Aug 31 21:57:47 localhost systemd: Stopped Network Manager. Aug 31 21:57:58 localhost systemd: Reloading. Aug 31 21:58:06 localhost systemd: Starting LSB: Bring up/down networking... Aug 31 21:58:06 localhost network: Bringing up loopback interface: [ OK ] Aug 31 21:58:06 localhost kernel: Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Aug 31 21:58:06 localhost kernel: MII link monitoring set to 100 ms Aug 31 21:58:07 localhost kernel: IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready Aug 31 21:58:07 localhost kernel: bond0: Adding slave em1 Aug 31 21:58:07 localhost kernel: bond0: Enslaving em1 as a backup interface with a down link Aug 31 21:58:07 localhost network: Bringing up interface bond0: ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Device does not seem to be present, delaying initialization. Aug 31 21:58:07 localhost /etc/sysconfig/network-scripts/ifup-eth: Device does not seem to be present, delaying initialization. Aug 31 21:58:07 localhost network: WARN : [/etc/sysconfig/network-scripts/ifup-eth] Unable to start slave device ifcfg-em2 for master bond0. Aug 31 21:58:07 localhost /etc/sysconfig/network-scripts/ifup-eth: Unable to start slave device ifcfg-em2 for master bond0. Aug 31 21:58:07 localhost kernel: IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready Aug 31 21:58:10 localhost kernel: tg3 0000:01:00.0 em1: Link is up at 1000 Mbps, full duplex Aug 31 21:58:10 localhost kernel: tg3 0000:01:00.0 em1: Flow control is off for TX and off for RX Aug 31 21:58:10 localhost kernel: tg3 0000:01:00.0 em1: EEE is disabled Aug 31 21:58:10 localhost kernel: bond0: link status definitely up for interface em1, 1000 Mbps full duplex Aug 31 21:58:10 localhost kernel: bond0: making interface em1 the new active one Aug 31 21:58:10 localhost kernel: bond0: first active interface up! 正常綁定,服務啓動 ########################## 下面是網絡摘取的文檔內容 http://www.cnblogs.com/zhangjianghua/p/6179136.html Bonding的模式一共有7種： mode=0(balance-rr)(平衡掄循環策略) 鏈路負載均衡，增加帶寬，支持容錯，一條鏈路故障會自動切換正常鏈路。交換機需要配置聚合口，思科叫port channel。 特點：傳輸數據包順序是依次傳輸（即：第1個包走eth0，下一個包就走eth1….一直循環下去，直到最後一個傳輸完畢），此模式提供負載平衡和容錯能力；但是我們知道如果一個連接 或者會話的數據包從不同的接口發出的話，中途再經過不同的鏈路，在客戶端很有可能會出現數據包無序到達的問題，而無序到達的數據包需要重新要求被髮送，這樣網絡的吞吐量就會下降 mode=1(active-backup)(主-備份策略) 這個是主備模式，只有一塊網卡是active，另一塊是備用的standby，所有流量都在active鏈路上處理，交換機配置的是捆綁的話將不能工作，因爲交換機往兩塊網卡發包，有一半包是丟棄的。 特點：只有一個設備處於活動狀態，當一個宕掉另一個馬上由備份轉換爲主設備。mac地址是外部可見得，從外面看來，bond的MAC地址是唯一的，以避免switch(交換機)發生混亂。 此模式只提供了容錯能力；由此可見此算法的優點是可以提供高網絡連接的可用性，但是它的資源利用率較低，只有一個接口處於工作狀態，在有 N 個網絡接口的情況下，資源利用率爲1/N mode=2(balance-xor)(平衡策略) 表示XOR Hash負載分擔，和交換機的聚合強制不協商方式配合。（需要xmit_hash_policy，需要交換機配置port channel） 特點：基於指定的傳輸HASH策略傳輸數據包。缺省的策略是：(源MAC地址 XOR 目標MAC地址) % slave數量。其他的傳輸策略可以通過xmit_hash_policy選項指定，此模式提供負載平衡和容錯能力 mode=3(broadcast)(廣播策略) 表示所有包從所有網絡接口發出，這個不均衡，只有冗餘機制，但過於浪費資源。此模式適用於金融行業，因爲他們需要高可靠性的網絡，不允許出現任何問題。需要和交換機的聚合強制不協商方式配合。 特點：在每個slave接口上傳輸每個數據包，此模式提供了容錯能力 mode=4(802.3ad)(IEEE 802.3ad 動態鏈接聚合) 表示支持802.3ad協議，和交換機的聚合LACP方式配合（需要xmit_hash_policy）.標準要求所有設備在聚合操作時，要在同樣的速率和雙工模式，而且，和除了balance-rr模式外的其它bonding負載均衡模式一樣，任何連接都不能使用多於一個接口的帶寬。 特點：創建一個聚合組，它們共享同樣的速率和雙工設定。根據802.3ad規範將多個slave工作在同一個激活的聚合體下。 外出流量的slave選舉是基於傳輸hash策略，該策略可以通過xmit_hash_policy選項從缺省的XOR策略改變到其他策略。需要注意的 是，並不是所有的傳輸策略都是802.3ad適應的， 尤其考慮到在802.3ad標準43.2.4章節提及的包亂序問題。不同的實現可能會有不同的適應 性。 必要條件： 條件1：ethtool支持獲取每個slave的速率和雙工設定 條件2：switch(交換機)支持IEEE 802.3ad Dynamic link aggregation 條件3：大多數switch(交換機)需要經過特定配置才能支持802.3ad模式 mode=5(balance-tlb)(適配器傳輸負載均衡) 是根據每個slave的負載情況選擇slave進行發送，接收時使用當前輪到的slave。該模式要求slave接口的網絡設備驅動有某種ethtool支持；而且ARP監控不可用。 特點：不需要任何特別的switch(交換機)支持的通道bonding。在每個slave上根據當前的負載（根據速度計算）分配外出流量。如果正在接受數據的slave出故障了，另一個slave接管失敗的slave的MAC地址。 必要條件： ethtool支持獲取每個slave的速率 mode=6(balance-alb)(適配器適應性負載均衡) 在5的tlb基礎上增加了rlb(接收負載均衡receive load balance).不需要任何switch(交換機)的支持。接收負載均衡是通過ARP協商實現的. 特點：該模式包含了balance-tlb模式，同時加上針對IPV4流量的接收負載均衡(receive load balance, rlb)，而且不需要任何switch(交換機)的支持。接收負載均衡是通過ARP協商實現的。bonding驅動截獲本機發送的ARP應答，並把源硬件地址改寫爲bond中某個slave的唯一硬件地址，從而使得不同的對端使用不同的硬件地址進行通信。 來自服務器端的接收流量也會被均衡。當本機發送ARP請求時，bonding驅動把對端的IP信息從ARP包中複製並保存下來。當ARP應答從對端到達 時，bonding驅動把它的硬件地址提取出來，併發起一個ARP應答給bond中的某個slave。 使用ARP協商進行負載均衡的一個問題是：每次廣播 ARP請求時都會使用bond的硬件地址，因此對端學習到這個硬件地址後，接收流量將會全部流向當前的slave。這個問題可以通過給所有的對端發送更新 （ARP應答）來解決，應答中包含他們獨一無二的硬件地址，從而導致流量重新分佈。 當新的slave加入到bond中時，或者某個未激活的slave重新 激活時，接收流量也要重新分佈。接收的負載被順序地分佈（round robin）在bond中最高速的slave上 當某個鏈路被重新接上，或者一個新的slave加入到bond中，接收流量在所有當前激活的slave中全部重新分配，通過使用指定的MAC地址給每個 client發起ARP應答。下面介紹的updelay參數必須被設置爲某個大於等於switch(交換機)轉發延時的值，從而保證發往對端的ARP應答 不會被switch(交換機)阻截。 必要條件： 條件1：ethtool支持獲取每個slave的速率； 條件2：底層驅動支持設置某個設備的硬件地址，從而使得總是有個slave(curr_active_slave)使用bond的硬件地址，同時保證每個bond 中的slave都有一個唯一的硬件地址。如果curr_active_slave出故障，它的硬件地址將會被新選出來的 curr_active_slave接管 其實mod=6與mod=0的區別：mod=6，先把eth0流量佔滿，再佔eth1，….ethX；而mod=0的話，會發現2個口的流量都很穩定，基本一樣的帶寬。而mod=6，會發現第一個口流量很高，第2個口只佔了小部分流量。 mode5和mode6不需要交換機端的設置，網卡能自動聚合。mode4需要支持802.3ad。mode0，mode2和mode3理論上需要靜態聚合方式。 但實測中mode0可以通過mac地址欺騙的方式在交換機不設置的情況下不太均衡地進行接收。