RHEL7/CentOS7雙網絡卡繫結-Network Teaming
RHEL7/CentOS7 Configure Network Teaming
Network Teaming可聯合或合併物理網路介面,形成具有較高吞吐量或冗餘方式的邏輯網路介面。其作為網絡卡繫結的備選方式出現,在系統中和傳統的bonding方式並存。
1. 系統環境
[[email protected] ~]# uname -a Linux test03 3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux [[email protected] ~]# ip addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno16777736: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:0c:29:56:69:4d brd ff:ff:ff:ff:ff:ff inet 192.168.231.13/24 brd 192.168.231.255 scope global eno16777736 valid_lft forever preferred_lft forever inet6 fe80::20c:29ff:fe56:694d/64 scope link valid_lft forever preferred_lft forever 3: eno33554992: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:0c:29:56:69:57 brd ff:ff:ff:ff:ff:ff 4: eno50332216: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:0c:29:56:69:61 brd ff:ff:ff:ff:ff:ff
2. 雙網絡卡繫結目標
-
網絡卡繫結模式:activebackup - 主備模式
一個網絡卡處於活躍狀態,另一個處於備份狀態,所有流量都在主鏈路上處理,當活躍網絡卡down掉時,啟用備份網絡卡。
-
繫結網絡卡:eno33554992+eno50332216=team0
-
設定eno33554992為主網絡卡(優先處於活躍狀態),eno50332216為輔網絡卡(備份狀態,主網絡卡鏈路正常時,輔網絡卡處於備份狀態);-- 此時無需設定輔網絡卡粘滯位。
-
設定eno33554992為主網絡卡,eno50332216為輔網絡卡,主網絡卡鏈路故障後,輔網絡卡切換為活躍狀態,主網絡卡鏈路恢復後,輔網絡卡仍保持活躍狀態直至其鏈路故障。 -- 此時需要設定輔網絡卡粘滯位{"sticky" true}。
-
3. 雙網絡卡繫結步驟
3.1 檢視物理網絡卡資訊:
[[email protected] network-scripts]# nmcli device DEVICE TYPE STATE CONNECTION eno16777736 ethernet connected eno16777736 eno33554992 ethernet connected eno33554992 eno50332216 ethernet connected eno50332216 lo loopback unmanaged -- # 共四張網絡卡,lo為本地迴環網絡卡,另外三張為物理網絡卡。
3.2 檢視網絡卡連線資訊
[[email protected] network-scripts]# nmcli connection show NAME UUID TYPE DEVICE eno50332216 36b38556-4bf8-4ce0-8045-4f5465530f67 802-3-ethernet eno50332216 eno33554992 46831ccf-905b-4361-b5ba-c5448133e288 802-3-ethernet eno33554992 eno16777736 613db14a-2375-4a89-b55a-d2abd8fc65d5 802-3-ethernet eno16777736
3.3 刪除網絡卡連線資訊
本次Network Teaming配置中,需要將eno33554992
和eno50332216
繫結為team0
,並且設定eno33554992
為主網絡卡,首先需要這兩塊網絡卡現有的配置資訊,否則team0
建立完成後,未刪除的網絡卡配置資訊會影響team0
的正常工作。
如果nmcli connection show
命令輸出中無將要進行配置的網絡卡連線資訊,則無需進行刪除操作。
[[email protected] network-scripts]# nmcli connection delete eno33554992 [[email protected] network-scripts]# nmcli connection delete eno50332216 [[email protected] network-scripts]# [[email protected] network-scripts]# nmcli connection show NAME UUID TYPE DEVICE eno16777736 613db14a-2375-4a89-b55a-d2abd8fc65d5 802-3-ethernet eno16777736 # 網絡卡連線資訊刪除成功。 # 這裡刪除的其實就是/etc/sysconfig/network-scripts目錄下兩塊網絡卡的配置檔案。 [[email protected] network-scripts]# pwd /etc/sysconfig/network-scripts [[email protected] network-scripts]# ls ifcfg-* ifcfg-eno16777736 ifcfg-lo
3.4 建立team0
[[email protected] network-scripts]# nmcli connection add type team ifname team0 con-name team0 config '{"runner": {"name":"activebackup"}}' ip4 192.168.231.100/24 Connection 'team0' (dfe2f884-40e0-4686-a7f9-2be4b1a4b5b2) successfully added.
裝置型別:team;裝置名稱和連線名稱:均為team0;繫結模式:activebackup - 主備模式;IP及子網掩碼:192.168.231.100/24;
當然,也可以後續設定IP地址,示例:
#建立team0並設定為主備模式 [[email protected] network-scripts]# nmcli connection add type team ifname team0 con-name team0 config '{"runner": {"name":"activebackup"}}' #設定IP地址及子網掩碼 [[email protected] network-scripts]# nmcli connection modify team0 ipv4.addresses 192.168.231.100/24 #設定IP地址獲取方法為手動 [[email protected] network-scripts]# nmcli connection modify team0 ipv4.method manual
配置完成後,會在/etc/sysconfig/network-scripts目錄下生成ifcfg-team0的配置檔案
[[email protected] network-scripts]# cat /etc/sysconfig/network-scripts/ifcfg-team0 DEVICE=team0 TEAM_CONFIG="{\"runner\": {\"name\":\"activebackup\"}}" DEVICETYPE=Team BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no NAME=team0 UUID=dfe2f884-40e0-4686-a7f9-2be4b1a4b5b2 ONBOOT=yes IPADDR=192.168.231.100 PREFIX=24 IPV6_PEERDNS=yes IPV6_PEERROUTES=yes
3.5 將兩塊網絡卡新增進team0
# 新增網絡卡eno33554992,裝置型別:team-slave;連線名稱:team0-p1;master:team0;優先順序:100 [[email protected] network-scripts]# nmcli connection add type team-slave ifname eno33554992 con-name team0-p1 master team0 config '{"prio": 100}' Connection 'team0-p1' (4c8901c7-0246-47ce-8d5a-272f23f88d70) successfully added. # 新增網絡卡eno50332216,裝置型別:team-slave;連線名稱:team0-p1;master:team0;優先順序:-10; 粘滯位:true(sticky標誌請根據實際需要設定) [[email protected] network-scripts]# nmcli connection add type team-slave ifname eno50332216 con-name team0-p2 master team0 config '{"prio": -10,"sticky": true}' Connection 'team0-p2' (d898f1f5-bb0f-496e-8cdd-7f3898c2a482) successfully added.
本次配置中
eno33554992
為主網絡卡,設定其優先順序為100;eno50332216
為輔網絡卡,設定其優先順序為-10,粘滯位為true。prio:優先順序。
數字越大,網絡卡優先順序越高,優先為活躍網絡卡;若不設定優先順序,則預設為0,先接入網路的網絡卡為活躍網絡卡,另一塊為備份網絡卡,直至活躍網絡卡斷開連線,備份網絡卡自動升級為活躍網絡卡,兩塊網絡卡角色互換。
sticky:粘滯位,預設為false;
輔網絡卡
eno50332216
中設定了sticky為true,代表如果輔網絡卡連線狀態變為為活躍狀態後,無論主網絡卡連線是否正常,其將會一直保持為活躍狀態。若不設定sticky,在輔網絡卡為活躍狀態時,若主網絡卡連線恢復正常,則活躍網絡卡由主網絡卡接管,輔網絡卡會變為備份狀態。
可根據實際需要進行引數設定。
配置完成後,此時會在/etc/sysconfig/network-scripts目錄下生成ifcfg-team0-p1,ifcfg-team0-p2的配置檔案:
[[email protected] network-scripts]# cat ifcfg-team0-p1 TEAM_PORT_CONFIG="{\"prio\": 100}" NAME=team0-p1 UUID=4c8901c7-0246-47ce-8d5a-272f23f88d70 DEVICE=eno33554992 ONBOOT=yes TEAM_MASTER=team0 DEVICETYPE=TeamPort [[email protected] network-scripts]# cat ifcfg-team0-p2 TEAM_PORT_CONFIG="{\"prio\": -10,\"sticky\": true}" NAME=team0-p2 UUID=d898f1f5-bb0f-496e-8cdd-7f3898c2a482 DEVICE=eno50332216 ONBOOT=yes TEAM_MASTER=team0 DEVICETYPE=TeamPort
4. 啟用team0及其子網絡卡
# 啟用team0-p1 [[email protected] ~]# nmcli connection up team0-p1 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/5) # 啟用team0-p2 [[email protected] ~]# nmcli connection up team0-p2 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/6) # 啟用team0 [[email protected] ~]# nmcli connection up team0 Connection successfully activated (master waiting for slaves) (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/7)
5. team0狀態檢視
5.1 檢視team0工作狀態:
# 檢視當前活躍網絡卡 [[email protected] network-scripts]# nmcli connection show --active NAME UUID TYPE DEVICE team0-p1 4c8901c7-0246-47ce-8d5a-272f23f88d70 802-3-ethernet eno33554992 eno16777736 613db14a-2375-4a89-b55a-d2abd8fc65d5 802-3-ethernet eno16777736 team0 d6e07840-dff8-49e9-a23c-35eb0cc0ec4b team team0 team0-p2 d898f1f5-bb0f-496e-8cdd-7f3898c2a482 802-3-ethernet eno50332216 #檢視team0埠狀態 [[email protected] network-scripts]# teamnl team0 ports 4: eno50332216: up 1000Mbit FD 3: eno33554992: up 1000Mbit FD [[email protected] network-scripts]# teamdctl team0 stat setup: runner: activebackup ports: eno33554992 link watches: link summary: up instance[link_watch_0]: name: ethtool link: up eno50332216 link watches: link summary: up instance[link_watch_0]: name: ethtool link: up runner: active port: eno33554992
5.2 檢視team0詳細配置
# 檢視team0詳細配置 [[email protected] network-scripts]# teamdctl team0 config dump { "device": "team0", "mcast_rejoin": { "count": 1 }, "notify_peers": { "count": 1 }, "ports": { "eno33554992": { "link_watch": { "name": "ethtool" }, "prio": 100 }, "eno50332216": { "link_watch": { "name": "ethtool" }, "prio": -10, "sticky": true } }, "runner": { "name": "activebackup" } } # 單獨檢視team0子網絡卡詳細配置 [[email protected] network-scripts]# teamdctl team0 port config dump eno33554992 { "link_watch": { "name": "ethtool" }, "prio": 100 } [[email protected] network-scripts]# teamdctl team0 port config dump eno50332216 { "link_watch": { "name": "ethtool" }, "prio": -10, "sticky": true }
6. team0切換測試
[[email protected] ~]# teamdctl team0 stat setup: runner: activebackup ports: eno33554992 link watches: link summary: up instance[link_watch_0]: name: ethtool link: up eno50332216 link watches: link summary: up instance[link_watch_0]: name: ethtool link: up runner: active port: eno33554992
當前活躍子網絡卡為eno33554992
,ping team0的IP地址一直可以ping通。現在將該網絡卡斷開連線:
# 斷開team0-p1的網路連線 [[email protected] ~]# nmcli connection down team0-p1 Connection 'team0-p1' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/2) # 檢視team0連線狀態 [[email protected] ~]# teamdctl team0 stat setup: runner: activebackup ports: eno50332216 link watches: link summary: up instance[link_watch_0]: name: ethtool link: up runner: active port: eno50332216 # 活躍網絡卡變為eno50332216,ping測試短暫中斷後恢復。 來自 192.168.231.100 的回覆: 位元組=32 時間<1ms TTL=64 來自 192.168.231.100 的回覆: 位元組=32 時間<1ms TTL=64 來自 192.168.231.100 的回覆: 位元組=32 時間=1ms TTL=64 來自 192.168.231.100 的回覆: 位元組=32 時間<1ms TTL=64 請求超時。 請求超時。 來自 192.168.231.100 的回覆: 位元組=32 時間=1ms TTL=64 來自 192.168.231.100 的回覆: 位元組=32 時間<1ms TTL=64 來自 192.168.231.100 的回覆: 位元組=32 時間<1ms TTL=64
由於本次測試在虛擬機器中進行,ping測試會出現較明顯的中斷,在真實的物理機上測試時,ping測試會一直正常或出現短暫中斷後恢復。
官方文件推薦使用:
nmcli device [disconnect|connect] ifname
命令來進行網絡卡的斷開和連線操作,但在虛擬機器上使用此方法斷開網絡卡連線後,恢復網絡卡連線時會報錯,這裡使用命令nmcli connection [down|up] ifname
進行操作。
當前活躍網絡卡為輔網絡卡eno50332216
,現在連線主網絡卡:
# 恢復team0-p1的網路連線 [[email protected] ~]# nmcli connection up team0-p1 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/7) # 檢視team0的連線狀態 [[email protected] ~]# teamdctl team0 stat setup: runner: activebackup ports: eno33554992 link watches: link summary: up instance[link_watch_0]: name: ethtool link: up eno50332216 link watches: link summary: up instance[link_watch_0]: name: ethtool link: up runner: active port: eno50332216 # ping測試短暫中斷後恢復 來自 192.168.231.100 的回覆: 位元組=32 時間<1ms TTL=64 請求超時。 請求超時。 來自 192.168.231.100 的回覆: 位元組=32 時間=1ms TTL=64 來自 192.168.231.100 的回覆: 位元組=32 時間<1ms TTL=64
由於本次測試在虛擬機器中進行,ping測試會出現較明顯的中斷,在真實的物理機上測試時,ping測試會一直正常或出現短暫中斷後恢復。
在主網絡卡連線恢復正常後,檢視team0發現當前活躍網絡卡仍為輔網絡卡
eno50332216
,沒有將活躍網絡卡切換為主網絡卡eno33554992
,原因是在輔網絡卡中設定了粘滯位sticky=true,sticky標誌使輔網絡卡為活躍狀態後,若其網路連線不發生故障,則會一直保持其為活躍網絡卡。如果在輔網絡卡配置中不設定sticky標誌,主網絡卡連線恢復正常後,活躍網絡卡由主網絡卡接管,輔網絡卡會變為備份狀態。
7. 雙網絡卡繫結各模式配置檔案示例
對於各種雙網絡卡繫結配置模式,請參考系統中的示例檔案,檔案位置:
/usr/share/doc/teamd-xx/example_configs/