一、bond 网络接口

Red Hat Enterprise Linux 允许管理员使用 bonding 内核模块和称为通道绑定接口的特殊网络接口将多个网络接口绑定到一个通道。根据选择的绑定模式,通道绑定使两个或更多个网络接口作为一个网络接口,从而增加带宽和 / 提供冗余性。

选择linux以太网绑定模式

目前网卡绑定mode共有七种(0~6):bond0、bond、bond1、bond2、bond3、bond4、bond5、bond6。这里介绍几种,然后会有关于模式1的实验详细说明。

模式0(平衡轮循):轮循策略。所有接口都采用轮循方式在所有 Slave 中传输封包;任何 Slave 都可以接收。

模式1(主动备份):容错。一次只能使用一个 Slave 接口,但是如果该接口出现故障,另一个 Slave 将接替它。

模式3(广播):容错。所有封包都通过所有 Slave 接口广播。

实验——mode1(主动备份)

1.为做实验的虚拟机添加两块网卡 eth0 和 eth1(步骤见图)

[root@localhost Desktop]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500inet 172.25.254.150  netmask 255.255.255.0  broadcast 172.25.254.255inet6 fe80::5054:ff:fe00:320a  prefixlen 64  scopeid 0x20<link>ether 52:54:00:00:32:0a  txqueuelen 1000  (Ethernet)RX packets 27  bytes 2832 (2.7 KiB)RX errors 0  dropped 0  overruns 0  frame 0TX packets 221  bytes 12177 (11.8 KiB)TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500ether 52:54:00:80:fa:d5  txqueuelen 1000  (Ethernet)RX packets 35  bytes 1734 (1.6 KiB)RX errors 0  dropped 0  overruns 0  frame 0TX packets 0  bytes 0 (0.0 B)TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536inet 127.0.0.1  netmask 255.0.0.0inet6 ::1  prefixlen 128  scopeid 0x10<host>loop  txqueuelen 0  (Local Loopback)RX packets 136  bytes 13228 (12.9 KiB)RX errors 0  dropped 0  overruns 0  frame 0TX packets 136  bytes 13228 (12.9 KiB)TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
[root@localhost Desktop]# nmcli connection delete eth0    ##将已经配置过的eth0恢复到默认状态,即未配置前
[root@localhost Desktop]# ifconfig eth0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500ether 52:54:00:00:32:0a  txqueuelen 1000  (Ethernet)RX packets 27  bytes 2832 (2.7 KiB)RX errors 0  dropped 0  overruns 0  frame 0TX packets 223  bytes 12273 (11.9 KiB)TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
[root@localhost Desktop]# nmcli connection add con-name bond0 ifname bond0 type bond mode active-backup ip4 172.25.254.129/24      ##配置bond网络接口,ip为172.25.254.129
Connection 'bond0' (68750e7d-8636-48aa-b9e6-89971dc56516) successfully added.
[root@localhost Desktop]# ifconfig bond0
bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST>  mtu 1500inet 172.25.254.129  netmask 255.255.255.0  broadcast 172.25.254.255ether 7a:c0:6f:e4:c3:22  txqueuelen 0  (Ethernet)RX packets 0  bytes 0 (0.0 B)RX errors 0  dropped 0  overruns 0  frame 0TX packets 0  bytes 0 (0.0 B)TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
[root@localhost Desktop]# cat /proc/net/bonding/bond0   ##查看网络接口bond0的信息。该文件只会在bond0接口添加后生成
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: None
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
[root@localhost Desktop]#

开启第二个命令面板,输入以下监控命令:

[root@localhost Desktop]# watch -n 15 cat /proc/net/bonding/bond0

除了用命令的方式添加,还可以通过建立配置文件的方式

[root@localhost network-scripts]# ls
ifcfg-bond0  ifdown-post      ifup-bnep   ifup-routes
ifcfg-eth0   ifdown-ppp       ifup-eth    ifup-sit
ifcfg-lo     ifdown-routes    ifup-ippp   ifup-Team
ifdown       ifdown-sit       ifup-ipv6   ifup-TeamPort
ifdown-bnep  ifdown-Team      ifup-isdn   ifup-tunnel
ifdown-eth   ifdown-TeamPort  ifup-plip   ifup-wireless
ifdown-ippp  ifdown-tunnel    ifup-plusb  init.ipv6-global
ifdown-ipv6  ifup             ifup-post   network-functions
ifdown-isdn  ifup-aliases     ifup-ppp    network-functions-ipv6
[root@localhost network-scripts]# cat ifcfg-bond0
DEVICE=bond0
BONDING_OPTS=mode=active-backup
TYPE=Bond
BONDING_MASTER=yes
BOOTPROTO=none
IPADDR0=172.25.254.129
PREFIX0=24
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME=bond0
UUID=68750e7d-8636-48aa-b9e6-89971dc56516
ONBOOT=yes
[root@localhost network-scripts]# cat ifcfg-eth0
TYPE=Ethernet
NAME=eth0
UUID=e179929b-633b-4caf-87ad-d98cf7024354
DEVICE=eth0
ONBOOT=yes
MASTER=bond0
SLAVE=yes
[root@localhost network-scripts]#

注意:删除bond网络接口bond0的所有配置(不影响下面team网络接口的实验)

[root@localhost network-scripts]# nmcli connection delete eth0
[root@localhost network-scripts]# nmcli connection delete eth1
[root@localhost network-scripts]# nmcli connection delete bond0

二、team 网络接口(企业七之前的版本没有这个功能)

  • Team 和 bond0 功能类似
  • Team 不需要手动加载相应内核模块
  • Team 有更强的扩展性
  • 支持8块网卡
  • Team 的种类:

broadcast     广播容错

roundrobin    平衡轮叫:比较机械

activebackup  主动备份

loadbalance   负载均衡:将任务平衡分配

team 网络接口

[root@localhost ~]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500ether 52:54:00:00:32:0a  txqueuelen 1000  (Ethernet)RX packets 195  bytes 11502 (11.2 KiB)RX errors 0  dropped 129  overruns 0  frame 0TX packets 330  bytes 18401 (17.9 KiB)TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500ether 52:54:00:80:fa:d5  txqueuelen 1000  (Ethernet)RX packets 180  bytes 9202 (8.9 KiB)RX errors 0  dropped 3  overruns 0  frame 0TX packets 118  bytes 6270 (6.1 KiB)TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536inet 127.0.0.1  netmask 255.0.0.0inet6 ::1  prefixlen 128  scopeid 0x10<host>loop  txqueuelen 0  (Local Loopback)RX packets 513  bytes 50444 (49.2 KiB)RX errors 0  dropped 0  overruns 0  frame 0TX packets 513  bytes 50444 (49.2 KiB)TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
[root@localhost ~]# nmcli connection add con-name team0 ifname team0 type team config '{"runner":{"name":"activebackup"}}' ip4 172.25.254.129/24
##成功添加team网络接口team0,ip为172.25.254.129
Connection 'team0' (97c3112a-532d-41ca-aa92-da48dad4adb5) successfully added.
[root@localhost ~]# teamdctl team0 stat   ##查看team0的信息
setup:runner: activebackup
runner:active port:    ##此处表示是可用接口,当前表示没有可用接口
[root@localhost ~]#

开启第二个命令面板:输入以下监控命令

[root@localhost ~]# watch -n 5 teamdctl team0 stat

注意:删除team网络接口team0的所有配置

[root@localhost ~]# nmcli connection delete eth0
[root@localhost ~]# nmcli connection delete eth1
[root@localhost ~]# nmcli connection delete team0 

三、有无网桥的区别实验(真机)

[kiosk@foundation50 Desktop]$ su
Password:
[root@foundation50 Desktop]# cd /etc/sysconfig/network-scripts/
[root@foundation50 network-scripts]# ls
ifcfg-br0    ifdown-isdn      ifup          ifup-plip      ifup-tunnel
ifcfg-lo     ifdown-post      ifup-aliases  ifup-plusb     ifup-wireless
ifdown       ifdown-ppp       ifup-bnep     ifup-post      init.ipv6-global
ifdown-bnep  ifdown-routes    ifup-eth      ifup-ppp       network-functions
ifdown-eth   ifdown-sit       ifup-ib       ifup-routes    network-functions-ipv6
ifdown-ib    ifdown-Team      ifup-ippp     ifup-sit
ifdown-ippp  ifdown-TeamPort  ifup-ipv6     ifup-Team
ifdown-ipv6  ifdown-tunnel    ifup-isdn     ifup-TeamPort
[root@foundation50 network-scripts]# mv ifcfg-br0 /opt/     ##做备份!!!一定要做的
[root@foundation50 network-scripts]# ls
ifcfg-lo     ifdown-post      ifup-aliases  ifup-plusb     ifup-wireless
ifdown       ifdown-ppp       ifup-bnep     ifup-post      init.ipv6-global
ifdown-bnep  ifdown-routes    ifup-eth      ifup-ppp       network-functions
ifdown-eth   ifdown-sit       ifup-ib       ifup-routes    network-functions-ipv6
ifdown-ib    ifdown-Team      ifup-ippp     ifup-sit
ifdown-ippp  ifdown-TeamPort  ifup-ipv6     ifup-Team
ifdown-ipv6  ifdown-tunnel    ifup-isdn     ifup-TeamPort
ifdown-isdn  ifup             ifup-plip     ifup-tunnel
[root@foundation50 network-scripts]# nm-connection-editor

[root@foundation50 network-scripts]# ifconfig
enp1s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500inet 172.25.254.50  netmask 255.255.255.0  broadcast 172.25.254.255inet6 fe80::ca5b:76ff:fe87:3653  prefixlen 64  scopeid 0x20<link>ether c8:5b:76:87:36:53  txqueuelen 1000  (Ethernet)RX packets 0  bytes 0 (0.0 B)RX errors 0  dropped 0  overruns 0  frame 0TX packets 0  bytes 0 (0.0 B)TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536inet 127.0.0.1  netmask 255.0.0.0inet6 ::1  prefixlen 128  scopeid 0x10<host>loop  txqueuelen 0  (Local Loopback)RX packets 819357  bytes 263780151 (251.5 MiB)RX errors 0  dropped 0  overruns 0  frame 0TX packets 819357  bytes 263780151 (251.5 MiB)TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255ether 52:54:00:37:a4:20  txqueuelen 0  (Ethernet)RX packets 0  bytes 0 (0.0 B)RX errors 0  dropped 0  overruns 0  frame 0TX packets 0  bytes 0 (0.0 B)TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
[root@foundation50 network-scripts]# virt-manager

建立网桥

[root@foundation50 network-scripts]# ls
ifcfg-enp1s0  ifdown-isdn      ifup          ifup-plip      ifup-tunnel
ifcfg-lo      ifdown-post      ifup-aliases  ifup-plusb     ifup-wireless
ifdown        ifdown-ppp       ifup-bnep     ifup-post      init.ipv6-global
ifdown-bnep   ifdown-routes    ifup-eth      ifup-ppp       network-functions
ifdown-eth    ifdown-sit       ifup-ib       ifup-routes    network-functions-ipv6
ifdown-ib     ifdown-Team      ifup-ippp     ifup-sit
ifdown-ippp   ifdown-TeamPort  ifup-ipv6     ifup-Team
ifdown-ipv6   ifdown-tunnel    ifup-isdn     ifup-TeamPort
[root@foundation50 network-scripts]# vim ifcfg-enp1s0
[root@foundation50 network-scripts]# cat ifcfg-enp1s0
DEVICE=enp1s0
BOOTPROTO=none
ONBOOT=yes
BRIDGE=br0
[root@foundation50 network-scripts]# vim ifcfg-br0
[root@foundation50 network-scripts]# cat ifcfg-br0
DEVICE=br0
ONBOOT=yes
BOOTPROTO=none
IPADDR=172.25.254.50
NETMASK=255.255.255.0
TYPE=Bridge
[root@foundation50 network-scripts]# systemctl stop NetworkManager.service
[root@foundation50 network-scripts]# systemctl restart network
[root@foundation50 network-scripts]# brctl show
bridge name bridge id STP enabled interfaces
br0      8000.c85b76873653  no     enp1s0
virbr0   8000.52540037a420  yes    virbr0-nic
[root@foundation50 network-scripts]# virt-manager 

其他步骤和没网桥的相同,不同的是如下图:

四、网桥的建立与删除(虚拟机)

  • 网桥的建立与删除

网桥的建立

[root@localhost Desktop]# brctl show
bridge name bridge id STP enabled interfaces
[root@localhost Desktop]# brctl addbr br0
[root@localhost Desktop]# ifconfig br0
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500inet6 fe80::bcab:1bff:fea8:249e  prefixlen 64  scopeid 0x20<link>ether be:ab:1b:a8:24:9e  txqueuelen 0  (Ethernet)RX packets 0  bytes 0 (0.0 B)RX errors 0  dropped 0  overruns 0  frame 0TX packets 8  bytes 648 (648.0 B)TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
[root@localhost Desktop]# ifconfig br0 172.25.254.127/24
[root@localhost Desktop]# ifconfig br0
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500inet 172.25.254.127  netmask 255.255.255.0  broadcast 172.25.254.255inet6 fe80::bcab:1bff:fea8:249e  prefixlen 64  scopeid 0x20<link>ether be:ab:1b:a8:24:9e  txqueuelen 0  (Ethernet)RX packets 0  bytes 0 (0.0 B)RX errors 0  dropped 0  overruns 0  frame 0TX packets 19  bytes 3377 (3.2 KiB)TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
[root@localhost Desktop]# brctl show
bridge name bridge id STP enabled interfaces
br0    8000.000000000000    no
[root@localhost Desktop]# ping 172.25.254.50
PING 172.25.254.50 (172.25.254.50) 56(84) bytes of data.
From 172.25.254.127 icmp_seq=1 Destination Host Unreachable
From 172.25.254.127 icmp_seq=2 Destination Host Unreachable
From 172.25.254.127 icmp_seq=3 Destination Host Unreachable
From 172.25.254.127 icmp_seq=4 Destination Host Unreachable
^C
--- 172.25.254.50 ping statistics ---
5 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4000ms
pipe 4
[root@localhost Desktop]# brctl addif br0 eth0
[root@localhost Desktop]# brctl show
bridge name bridge id STP enabled interfaces
br0    8000.52540000320a    no     eth0
[root@localhost Desktop]# ping 172.25.254.50
PING 172.25.254.50 (172.25.254.50) 56(84) bytes of data.
64 bytes from 172.25.254.50: icmp_seq=1 ttl=64 time=0.316 ms
64 bytes from 172.25.254.50: icmp_seq=2 ttl=64 time=0.148 ms
64 bytes from 172.25.254.50: icmp_seq=3 ttl=64 time=0.340 ms
^C
--- 172.25.254.50 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.148/0.268/0.340/0.085 ms
[root@localhost Desktop]#

网桥的删除

[root@localhost Desktop]# brctl show
bridge name bridge id STP enabled interfaces
br0    8000.52540000320a    no    eth0
[root@localhost Desktop]# brctl delif br0 eth0
[root@localhost Desktop]# brctl show
bridge name bridge id STP enabled interfaces
br0    8000.000000000000    no
[root@localhost Desktop]# ifconfig br0 down
[root@localhost Desktop]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500ether 52:54:00:00:32:0a  txqueuelen 1000  (Ethernet)RX packets 13  bytes 1026 (1.0 KiB)RX errors 0  dropped 0  overruns 0  frame 0TX packets 4  bytes 336 (336.0 B)TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500ether 52:54:00:80:fa:d5  txqueuelen 1000  (Ethernet)RX packets 9  bytes 690 (690.0 B)RX errors 0  dropped 0  overruns 0  frame 0TX packets 0  bytes 0 (0.0 B)TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536inet 127.0.0.1  netmask 255.0.0.0inet6 ::1  prefixlen 128  scopeid 0x10<host>loop  txqueuelen 0  (Local Loopback)RX packets 13  bytes 1116 (1.0 KiB)RX errors 0  dropped 0  overruns 0  frame 0TX packets 13  bytes 1116 (1.0 KiB)TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
[root@localhost Desktop]# brctl delbr br0
[root@localhost Desktop]# brctl show
bridge name bridge id STP enabled interfaces
[root@localhost Desktop]#

linux——高级网络配置之bond、team网络接口,网络桥接相关推荐

  1. 高级网络配置《 bond team桥接 》的建立

    bond 资料详情 一.链路聚合:以太网链路聚合简称链路聚合,它通过将多条以太网物理链路捆绑在一起成为一条逻辑链路,从而实现增加链路带宽的目的.同时,这些捆绑在一起的链路通过相互间的动态备份,可以有效 ...

  2. Linux多网卡绑定(bond)及网络组(team)

    Linux多网卡绑定(bond)及网络组(team)   很多时候,由于生产环境业务的特殊需求,我们需要对服务器的物理网卡实施特殊的配置,从而来满足不同业务场景下对服务器网络的特殊性要求.如高并发的网 ...

  3. 虚机安装Linux网络配置的一些笔记(隔离,桥接,NAT)

    我的需求: 记得最开始学Linux的时候,使用VM虚拟机安装,配置网络,希望可以和主机互通,同时希望可以访问外网,改配置文件,照着网上的博客,改了又改,捣鼓了好几天也弄不好. 我需要解决的问题: 后来 ...

  4. Linux之高级网络配置(bond,team以及网桥的搭建)

    bond网络 ##什么是bond,为什么要配置bond bond是将多块网卡虚拟链接成一块网卡的技术,通过bond技术让多块网卡看起来是一个单独的以太网接口设备并具有相同的ip地址. 特点:bond默 ...

  5. 高级网络配置:Bond网络接口、Team网络接口和网桥

    一.Bond网络接口 (一)概述 Bonding就是把多个物理网络接口绑定到一起,使它们就像一个网络接口那样运行.通过Bonding技术,可以实现网口冗余,负载均衡,从而达到高可用高可靠的目的. 那在 ...

  6. 高级网络配置(包括链路聚合和网络桥接)

    1.网卡的链路聚合 网卡的链路聚合就是将多块网卡连接起来,当一块网卡损坏,网络依旧可以正常运行 可以有效的防止因为网卡损坏带来的损失,同时也可以提高网络访问速度 网卡的链路聚合一般常用的有" ...

  7. docker 网络配置_Kafka的AWS Docker网络设置

    Kafka是一个分布式流处理平台,最近几年获得了长足的发展和进步.这篇文章主要针对在AWS 上部署 Kafka Docker镜像的注意事项.其中最容易出问题的部分就是Kafka的listeners配置 ...

  8. 远距离无线模块T900网络配置(点对多点网络)

    点对多点网络 点对多点网络中,主端可以和多个从端直接连接,也可以通过中继和多个从端连接.中继器也具有从端的功能,可以和主端通信,但其上行数据会和从端的上行数据混淆传输.点对多点网络需要配置网络类型寄存 ...

  9. VMware下网络配置三种模式对比(桥接模式,主机模式,网络地址转换)

    1 VMware三种网络模式简介 VMWare提供了三种工作模式,它们是bridged(桥接模式).NAT(网络地址转换模式)和host-only(主机模式).安装好虚拟机以后,在网络连接里面可以看到 ...

最新文章

  1. 深圳大学李猛教授报告:海洋古菌的微生物组学(11月17日晚7点)
  2. 如何安装Android SDK Emulator
  3. 想学python都要下载什么软件-学编程闲余时间建议下载的软件_Python新手入门教程...
  4. 无人驾驶遇见人工智能 百度将推有“大脑”的汽车
  5. Struts2中ValueStack结构和总结
  6. php必须汉字,php怎么只保留汉字
  7. [******] java多线程连续打印abc
  8. python中argsort_浅述python中argsort()函数的实例用法
  9. 眼儿媚·迟迟春日弄轻柔 [宋] 朱淑真
  10. PHP多次调用Mysql存储过程报错解决办法
  11. ArrayList和数组之间的一些转换
  12. java简单代码练习
  13. Layui 表格分页控件
  14. 加入域 提示 无法加载指定的脱机注册表配置单元
  15. LeetCode——150. 逆波兰表达式求值(Evaluate Reverse Polish Notation)[中等]——分析及代码(Java)
  16. 如何减少城市拥堵?——虹科利用激光雷达技术实现智能交通
  17. Java调用excel宏
  18. MapBoxGL 入门
  19. 计算机系统 ahci模式,打开ahci模式后需要重装系统吗
  20. LOCATE函数的用法

热门文章

  1. 【MM模块】Contract 采购合同简介
  2. 【PP操作手册】工艺路线相关操作
  3. SAP ABAP ALV构建动态输出列与构建动态内表
  4. 计划策略-30-按销售与库存订单以批量生产
  5. BAPI FOR MD61,MD62,MD63
  6. 通过LDB_PROCESS函数使用逻辑数据库
  7. 优胜教育暴雷之后,线下一对一还是门好生意吗?
  8. 骑手困在系统里,网友困在回应里,而王兴正在刷饭否
  9. 超出网络bios会话限制_什么是UEFI,它和BIOS有什么不同?
  10. 数据库查询某一列大写转化小写字母表示_算法/开发 面试必看! 【数据库】面试题合集...