bond解除 centos7_centos7.1-bond丢包问题

于 2020-12-31 07:17:14 发布
阅读量1.3k 收藏
点赞数 1
文章标签： bond解除 centos7
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_39638623/article/details/112815258
版权

服务器配置：

品牌：SA5212H2  CPU:Intel(R) Xeon(R) CPU E5-2407 0 @ 2.20GHz  内存：16g

服务器资源使用

操作系统版本：

[root@]# uname -a

Linux 3.10.0-229.20.1.el7.x86_64 #1 SMP Tue Nov 3 19:10:07 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

[root@f ]# cat /etc/redhat-release

CentOS Linux release 7.1.1503 (Core)

bond0配置(bond是我在重装系统的时候做的)

网卡配置

eth0

NAME=bond0 slave 1

MASTER=a25343c6-c96c-4683-ae48-848e3fca704f

HWADDR=

TYPE=Ethernet

ONBOOT=yes

UUID=0a553f1d-85a8-4446-9ee2-88dc085a4e92

eth1

# Generated by parse-kickstart

NAME=bond0 slave 2

MASTER=a25343c6-c96c-4683-ae48-848e3fca704f

HWADDR=

TYPE=Ethernet

ONBOOT=yes

UUID=f0426c72-a3c4-4803-b797-37824fa34c87

出现的问题是：

bond0 (bond0使用的mac地址是eth1的)接口dropped 丢包每一秒丢一个包。

关掉eth0 bond0 dropped 丢包消失

以下是我截取到的http报文

tcpdump -i bond0 dst port 80

17:05:40.338486 IP 61.1.10.1.39215 > 61.156.241.174.http: Flags [F.], seq 978338840, ack 1177028699, win 31, length 0

17:05:40.710831 IP 61.1.10.1.35946 > 61.158.164.155.http: Flags [F.], seq 47910714, ack 2457429085, win 31, length 0

17:05:46.027797 IP 115.29.222.217.63731 > 61.1.10.1.http: Flags [S], seq 4281715269, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0

17:05:46.061259 IP 115.29.222.217.63731 > 61.1.10.1.http: Flags [.], ack 2669976514, win 256, length 0

17:05:46.061901 IP 115.29.222.217.63731 > 61.1.10.1.http: Flags [P.], seq 0:208, ack 1, win 256, length 208

17:05:46.110941 IP 115.29.222.217.63732 > 61.1.10.1.http: Flags [S], seq 2654506387, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0

17:05:46.139890 IP 115.29.222.217.63732 > 61.1.10.1.http: Flags [.], ack 3781507412, win 256, length 0

17:05:46.140269 IP 115.29.222.217.63732 > 61.1.10.1.http: Flags [P.], seq 0:558, ack 1, win 256, length 558

17:05:46.297245 IP 115.29.222.217.63731 > 61.1.10.1.http: Flags [.], ack 239, win 255, length 0

17:05:46.374184 IP 115.29.222.217.63732 > 61.1.10.1.http: Flags [.], ack 239, win 255, length 0

17:05:46.852699 IP 115.29.222.217.63731 > 61.1.10.1.http: Flags [F.], seq 208, ack 239, win 255, length 0

17:05:46.886398 IP 115.29.222.217.63731 > 61.1.10.1.http: Flags [.], ack 240, win 255, length 0

17:05:50.981886 IP 139.226.22.194.53517 > 61.1.10.1.http: Flags [.], ack 1945224633, win 35250, length 0

17:05:51.050212 IP 61.135.170.194.43668 > 61.1.10.1.http: Flags [S], seq 464709165, win 5840, options [mss 1460,sackOK,TS val 2835300322 ecr 0,nop,wscale 7], length 0

17:05:51.053238 IP 61.135.170.194.51171 > 112.65.222.182.http: Flags [S], seq 470525896, win 5840, options [mss 1460,sackOK,TS val 2835300323 ecr 0,nop,wscale 7], length 0

17:05:51.076869 IP 61.135.170.194.43668 > 61.1.10.1.http: Flags [.], ack 2979511321, win 46, options [nop,nop,TS val 2835300329 ecr 1148734261], length 0

17:05:51.077953 IP 61.135.170.194.51171 > 112.65.222.182.http: Flags [.], ack 1019414286, win 46, options [nop,nop,TS val 2835300330 ecr 1148734264], length 0

17:05:51.079276 IP 61.135.170.194.43668 > 61.1.10.1.http: Flags [P.], seq 0:279, ack 1, win 46, options [nop,nop,TS val 2835300330 ecr 1148734261], length 279

17:05:51.081615 IP 61.135.170.194.51171 > 112.65.222.182.http: Flags [P.], seq 0:279, ack 1, win 46, options [nop,nop,TS val 2835300330 ecr 1148734264], length 279

17:05:51.106661 IP 61.135.170.194.51171 > 112.65.222.182.http: Flags [.], ack 258, win 54, options [nop,nop,TS val 2835300337 ecr 1148734293], length 0

17:05:51.114997 IP 61.135.170.194.51171 > 112.65.222.182.http: Flags [F.], seq 279, ack 259, win 54, options [nop,nop,TS val 2835300339 ecr 1148734293], length 0

17:05:51.115768 IP 61.135.170.194.43668 > 61.1.10.1.http: Flags [F.], seq 279, ack 259, win 54, options [nop,nop,TS val 2835300339 ecr 1148734291], length 0

17:05:58.889023 IP 58.247.15.35.nm-assessor > 61.1.10.1.http: Flags [S], seq 3404001604, win 65535, options [mss 1460,nop,wscale 0,nop,nop,sackOK], length 0

17:05:58.892591 IP 58.247.15.35.nm-assessor > 61.1.10.1.http: Flags [.], ack 4119620738, win 65535, length 0

17:05:58.892947 IP 58.247.15.35.nm-assessor > 61.1.10.1.http: Flags [P.], seq 0:260, ack 1, win 65535, length 260

17:05:58.897836 IP 58.247.15.35.nm-assessor > 61.1.10.1.http: Flags [P.], seq 260:448, ack 444, win 65092, length 188

17:05:58.902468 IP 58.247.15.35.nm-assessor > 61.1.10.1.http: Flags [.], ack 3364, win 65535, length 0

17:05:58.902505 IP 58.247.15.35.nm-assessor > 61.1.10.1.http: Flags [.], ack 4824, win 65535, length 0

17:05:59.199284 IP 58.247.15.35.nm-assessor > 61.1.10.1.http: Flags [.], ack 582292, win 64767, length 0

17:06:02.428984 IP 112.64.235.86.44454 > 61.1.10.1.http: Flags [S], seq 3264687314, win 5840, options [mss 1460,sackOK,TS val 24553782 ecr 0,nop,wscale 9], length 0

17:06:02.431358 IP 112.64.235.86.44454 > 61.1.10.1.http: Flags [.], ack 4086212070, win 12, options [nop,nop,TS val 24553782 ecr 1148745640], length 0

17:06:02.431406 IP 112.64.235.86.44454 > 61.1.10.1.http: Flags [P.], seq 0:439, ack 1, win 12, options [nop,nop,TS val 24553782 ecr 1148745640], length 439

17:06:02.432274 IP 61.1.10.1.50392 > 61.156.241.175.http: Flags [S], seq 3530807695, win 14600, options [mss 1460,sackOK,TS val 1148745643 ecr 0,nop,wscale 9], length 0

17:06:02.448167 IP 61.1.10.1.50392 > 61.156.241.175.http: Flags [.], ack 152401547, win 29, length 0

17:06:02.448227 IP 61.1.10.1.50392 > 61.156.241.175.http: Flags [P.], seq 0:533, ack 1, win 29, length 533

17:06:02.546523 IP 61.1.10.1.50392 > 61.156.241.175.http: Flags [.], ack 360, win 31, length 0

17:06:02.549152 IP 112.64.235.86.44454 > 61.1.10.1.http: Flags [.], ack 391, win 14, options [nop,nop,TS val 24553812 ecr 1148745758], length 0

17:06:02.549215 IP 112.64.235.86.44454 > 61.1.10.1.http: Flags [F.], seq 439, ack 392, win 14, options [nop,nop,TS val 24553812 ecr 1148745758], length 0

17:06:02.549241 IP 112.64.235.86.44485 > 61.1.10.1.http: Flags [S], seq 3266762300, win 5840, options [mss 1460,sackOK,TS val 24553812 ecr 0,nop,wscale 9], length 0

17:06:02.551294 IP 112.64.235.86.44485 > 61.1.10.1.http: Flags [.], ack 535628582, win 12, options [nop,nop,TS val 24553812 ecr 1148745760], length 0

17:06:02.551344 IP 112.64.235.86.44485 > 61.1.10.1.http: Flags [P.], seq 0:417, ack 1, win 12, options [nop,nop,TS val 24553812 ecr 1148745760], length 417

17:06:02.554195 IP 112.64.235.86.44485 > 61.1.10.1.http: Flags [.], ack 1449, win 18, options [nop,nop,TS val 24553813 ecr 1148745763], length 0

17:06:02.554215 IP 112.64.235.86.44485 > 61.1.10.1.http: Flags [.], ack 4345, win 23, options [nop,nop,TS val 24553813 ecr 1148745763], length 0

17:06:02.554228 IP 112.64.235.86.44485 > 61.1.10.1.http: Flags [R.], seq 417, ack 4345, win 23, options [nop,nop,TS val 24553813 ecr 1148745763], length 0

17:06:16.171119 IP 115.29.222.217.63732 > 61.1.10.1.http: Flags [.], ack 240, win 255, length 0

17:06:20.817635 IP 139.226.22.194.53517 > 61.1.10.1.http: Flags [F.], seq 0, ack 1, win 35250, length 0

17:06:20.831027 IP 139.226.22.194.53523 > 61.1.10.1.http: Flags [S], seq 2255959654, win 8192, options [mss 1400,nop,wscale 2,nop,nop,sackOK], length 0

17:06:20.846405 IP 139.226.22.194.53523 > 61.1.10.1.http: Flags [.], ack 3361684270, win 16567, length 0

17:06:20.846442 IP 139.226.22.194.53523 > 61.1.10.1.http: Flags [P.], seq 0:260, ack 1, win 16567, length 260

17:06:20.856858 IP 139.226.22.194.53523 > 61.1.10.1.http: Flags [P.], seq 260:448, ack 444, win 16456, length 188

17:06:20.863273 IP 139.226.22.194.53523 > 61.1.10.1.http: Flags [.], ack 3244, win 16567, length 0

17:06:20.865772 IP 139.226.22.194.53523 > 61.1.10.1.http: Flags [.], ack 7444, win 16567, length 0

17:06:20.866249 IP 139.226.22.194.53523 > 61.1.10.1.http: Flags [.], ack 11644, win 16567, length 0

17:06:21.055303 IP 139.226.22.194.53523 > 61.1.10.1.http: Flags [.], ack 571644, win 16567, length 0

17:06:21.064680 IP 139.226.22.194.53523 > 61.1.10.1.http: Flags [.], ack 575508, win 16567, length 0

17:06:21.064693 IP 139.226.22.194.53523 > 61.1.10.1.http: Flags [.], ack 579260, win 16567, length 0

17:06:21.064696 IP 139.226.22.194.53523 > 61.1.10.1.http: Flags [.], ack 582292, win 16567, length 0

17:06:28.981425 IP 58.247.15.35.nm-assessor > 61.1.10.1.http: Flags [.], ack 582293, win 64767, length 0

17:06:32.545946 IP 61.1.10.1.50392 > 61.156.241.175.http: Flags [F.], seq 533, ack 361, win 31, length 0

17:06:33.019369 IP 61.1.10.1.50392 > 61.156.241.175.http: Flags [.], ack 361, win 31, options [nop,nop,sack 1 {360:361}], length 0

17:06:33.301454 IP 61.1.10.1.50392 > 61.156.241.175.http: Flags [F.], seq 533, ack 361, win 31, length 0

17:06:35.354688 IP 210.13.94.157.16702 > 61.1.10.1.http: Flags [F.], seq 999380700, ack 53647190, win 65535, length 0

17:06:35.355157 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [S], seq 3536386158, win 65535, options [mss 1460,nop,nop,sackOK], length 0

17:06:35.361759 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [.], ack 2449944162, win 65535, length 0

17:06:35.362296 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [P.], seq 0:235, ack 1, win 65535, length 235

17:06:35.373074 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [.], ack 7301, win 65535, length 0

17:06:35.373846 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [.], ack 16061, win 59695, length 0

17:06:35.374822 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [.], ack 20441, win 55315, length 0

17:06:35.376290 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [.], ack 35041, win 40715, length 0

17:06:35.380174 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [.], ack 37961, win 37795, length 0

17:06:35.380765 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [.], ack 43801, win 31955, length 0

17:06:35.381143 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [.], ack 48181, win 27575, length 0

17:06:35.381153 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [.], ack 52561, win 23195, length 0

17:06:35.382164 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [.], ack 59861, win 15895, length 0

17:06:35.382694 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [.], ack 65701, win 10055, length 0

17:06:35.383286 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [.], ack 71541, win 4215, length 0

17:06:35.383714 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [.], ack 74461, win 1295, length 0

17:06:35.393351 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [.], ack 74461, win 5055, length 0

17:06:35.393399 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [.], ack 74461, win 65535, length 0

17:06:35.401663 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [.], ack 80301, win 65535, length 0

17:06:35.402996 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [.], ack 83221, win 65535, length 0

17:06:35.403311 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [.], ack 87601, win 65535, length 0

17:06:35.403335 IP 210.13.94.157.16703 > 61.1.10.1.http: Flags [.], ack 93314, win 65535, length 0

17:06:48.552942 IP 115.29.222.217.64786 > 61.1.10.1.http: Flags [S], seq 3863560027, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0

17:06:48.587482 IP 115.29.222.217.64786 > 61.1.10.1.http: Flags [.], ack 516459580, win 256, length 0

17:06:48.587529 IP 115.29.222.217.64786 > 61.1.10.1.http: Flags [P.], seq 0:208, ack 1, win 256, length 208

17:06:48.636870 IP 115.29.222.217.64790 > 61.1.10.1.http: Flags [S], seq 1459101229, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0

17:06:48.664935 IP 115.29.222.217.64790 > 61.1.10.1.http: Flags [.], ack 3239240326, win 256, length 0

17:06:48.665547 IP 115.29.222.217.64790 > 61.1.10.1.http: Flags [P.], seq 0:558, ack 1, win 256, length 558

17:06:48.821821 IP 115.29.222.217.64786 > 61.1.10.1.http: Flags [.], ack 239, win 255, length 0

17:06:48.890830 IP 115.29.222.217.64790 > 61.1.10.1.http: Flags [.], ack 239, win 255, length 0

17:06:49.742476 IP 115.29.222.217.64786 > 61.1.10.1.http: Flags [F.], seq 208, ack 239, win 255, length 0

17:06:49.775921 IP 115.29.222.217.64786 > 61.1.10.1.http: Flags [.], ack 240, win 255, length 0

17:06:50.976340 IP 139.226.22.194.53523 > 61.1.10.1.http: Flags [.], ack 582293, win 16567, length 0

17:06:58.888931 IP 58.247.15.35.s8-client-port > 61.1.10.1.http: Flags [S], seq 264411760, win 65535, options [mss 1460,nop,wscale 0,nop,nop,sackOK], length 0

17:06:58.891584 IP 58.247.15.35.s8-client-port > 61.1.10.1.http: Flags [.], ack 2739712364, win 65535, length 0

17:06:58.891978 IP 58.247.15.35.s8-client-port > 61.1.10.1.http: Flags [P.], seq 0:260, ack 1, win 65535, length 260

17:06:58.896269 IP 58.247.15.35.s8-client-port > 61.1.10.1.http: Flags [P.], seq 260:448, ack 444, win 65092, length 188

17:06:58.900719 IP 58.247.15.35.s8-client-port > 61.1.10.1.http: Flags [.], ack 3364, win 65535, length 0

17:06:58.900765 IP 58.247.15.35.s8-client-port > 61.1.10.1.http: Flags [.], ack 4824, win 65535, length 0

17:06:58.901119 IP 58.247.15.35.s8-client-port > 61.1.10.1.http: Flags [.], ack 7744, win 65535, length 0

17:06:58.901133 IP 58.247.15.35.s8-client-port > 61.1.10.1.http: Flags [.], ack 9204, win 65535, length 0

dropwatch -l kas

2 drops at ip_rcv_finish+16c (0xffffffff815364ec)

3 drops at tcp_rcv_state_process+1b0 (0xffffffff81550af0)

3 drops at tcp_v4_do_rcv+ac (0xffffffff8155a19c)

1 drops at sk_stream_kill_queues+50 (0xffffffff814f3090)

2 drops at unix_stream_connect+2ca (0xffffffff815a340a)

1 drops at __netif_receive_skb_core+703 (0xffffffff814fc173)

1 drops at tcp_rcv_state_process+1b0 (0xffffffff81550af0)

1 drops at sk_stream_kill_queues+50 (0xffffffff814f3090)

6 drops at tcp_rcv_state_process+1b0 (0xffffffff81550af0)

6 drops at tcp_v4_do_rcv+ac (0xffffffff8155a19c)

2 drops at ip_rcv_finish+16c (0xffffffff815364ec)

2 drops at unix_stream_connect+2ca (0xffffffff815a340a)

5 drops at tcp_rcv_state_process+1b0 (0xffffffff81550af0)

5 drops at tcp_v4_do_rcv+ac (0xffffffff8155a19c)

2 drops at ip_rcv_finish+16c (0xffffffff815364ec)

2 drops at unix_stream_connect+2ca (0xffffffff815a340a)

1 drops at __netif_receive_skb_core+703 (0xffffffff814fc173)

8 drops at skb_queue_purge+18 (0xffffffff814ecd38)

2 drops at unix_stream_connect+2ca (0xffffffff815a340a)

3 drops at ip_rcv_finish+16c (0xffffffff815364ec)

2 drops at unix_stream_connect+2ca (0xffffffff815a340a)

2 drops at tcp_rcv_state_process+1b0 (0xffffffff81550af0)

2 drops at tcp_v4_do_rcv+ac (0xffffffff8155a19c)

2 drops at unix_stream_connect+2ca (0xffffffff815a340a)

3 drops at ip_rcv_finish+16c (0xffffffff815364ec)

2 drops at tcp_rcv_state_process+1b0 (0xffffffff81550af0)

2 drops at tcp_v4_do_rcv+ac (0xffffffff8155a19c)

2 drops at unix_stream_connect+2ca (0xffffffff815a340a)

1 drops at __netif_receive_skb_core+703 (0xffffffff814fc173)

4 drops at tcp_rcv_state_process+1b0 (0xffffffff81550af0)

4 drops at tcp_v4_do_rcv+ac (0xffffffff8155a19c)

14 drops at unix_stream_connect+2ca (0xffffffff815a340a)

2 drops at tcp_rcv_state_process+1b0 (0xffffffff81550af0)

2 drops at tcp_v4_do_rcv+ac (0xffffffff8155a19c)

1 drops at __netif_receive_skb_core+703 (0xffffffff814fc173)

8 drops at skb_queue_purge+18 (0xffffffff814ecd38)

1 drops at tcp_rcv_state_process+1b0 (0xffffffff81550af0)

1 drops at tcp_v4_do_rcv+ac (0xffffffff8155a19c)

8 drops at unix_stream_connect+2ca (0xffffffff815a340a)

20 drops at unix_stream_connect+2ca (0xffffffff815a340a)

12 drops at unix_stream_connect+2ca (0xffffffff815a340a)

1 drops at tcp_rcv_state_process+1b0 (0xffffffff81550af0)

1 drops at tcp_v4_do_rcv+ac (0xffffffff8155a19c)

2 drops at ip_rcv_finish+16c (0xffffffff815364ec)

2 drops at tcp_rcv_state_process+1b0 (0xffffffff81550af0)

2 drops at tcp_v4_do_rcv+ac (0xffffffff8155a19c)

1 drops at tcp_v4_rcv+78 (0xffffffff8155bf88)

2 drops at tcp_rcv_state_process+1b0 (0xffffffff81550af0)

2 drops at tcp_v4_do_rcv+ac (0xffffffff8155a19c)

2 drops at ip_rcv_finish+16c (0xffffffff815364ec)

2 drops at unix_stream_connect+2ca (0xffffffff815a340a)

4 drops at tcp_rcv_state_process+1b0 (0xffffffff81550af0)

4 drops at tcp_v4_do_rcv+ac (0xffffffff8155a19c)

^CGot a stop message

请高手指点谢谢

weixin_39638623
关注
  • 1
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
bond解除 centos7_centos7 搭建双网卡bond1（主备模式）实例
weixin_39811166的博客
12-22 617
前景须知：在redhat6 中网卡叫bond，在redhat7及centos7中改名team,此处只记录centos7中双网卡主备搭建过程。应用情景：实现网络的高可用，防止一条网线或交换机故障影响该物理机进行数据交互此次环境是由于在上线业务之前是没有做Team的 ，现在由于要撤掉交换机过程期间需要将网线连接到另外一台交换机，为了防止数据中断，因此采用Team主备模式，这样断掉一个网卡就不影响业务，...
网卡做bond 导致丢包
weixin_30664051的博客
09-02 2811
值班中发现一台服务器报到网关丢包，带宽200M。 用 ethtool bond0 查看网卡带宽信息，发现 Speed 为 3100M ,非 1000 的整数倍或10000的整数倍，感觉不对，因为是做了bond , 查了下具体的网卡信息，发现bond0 是 4绑 1，3个千兆 + 1个百兆， 因此丢包是因为百兆卡跑满导致，将其从bond 里 删除后， 网卡恢复正...
Bonding的时候丢包严重和网卡重启变化问题
wodamazi
12-02 3173
Bonding导致丢包严重问题： （1）Bonding的mode设置不正确，使用mode=1，负载均衡模式，需要交换机的支持和配置； （2）采用mode=6来进行负载均衡，不需要交换机的支撑； Bonding导致网卡重启变化问题： （1）配置过程中，没有设置具体的MAC地址，导致重启后网卡变化，从而导致bond发生错误； （2）配置的过程中，一定记得备份文件，在发生错误的时候进行恢复...
centos 7 局域网丢包排查_宽带发生故障怎么办？教你几招轻松排查
weixin_39750731的博客
11-10 794
1 FTTH故障处理步骤第一步：查看ONT（光猫） “Power”电源灯的状态。（1）不亮，表示供电异常，需要检查电源连接和电源适配器是否工作正常（2）长亮，表示供电正常转第二步。第二步：查看ONT（光猫） “LOS”灯的状态。（1）熄灭，表示信号正常转第三步。（2）闪亮，表示光猫接收不到信号或低于灵敏度，转第五步。第三步：查看ONT（光猫） “PON”或“LINK”灯的状态。（1）常亮，表示ON...
设备板卡连接到交换机，bond1主备网卡切换丢包问题分析
靡不有初，鲜克有终。
03-25 3672
linux 系统板卡采用bond1模式（主备切换），bond驱动版本V3.7.1 问题描述：当主网口遇到网络问题或主网口网线被拔出时，切换到备用网口会有1秒左右的缓冲时间，期间造成设备数据的丢失。 问题分析: 因为在bond1模式下，交换机的两个接口不需要配置聚合，正常情况下服务器主网卡对应的交换机AC口上会有VLAN-VXLAN映射的配置，而备AC口上没有映射配置。当服务器网卡切换到...
centos6or7做bond
09-24
总之，CentOS 6和7中的bonding配置涉及到加载模块、创建bond接口和slave接口、设置网络参数以及调整modprobe配置，以实现网络接口的冗余和性能提升。正确实施后，将大大提高系统的网络稳定性与可靠性。
centos6or7做bond.docx
11-05
在本教程中，我们将介绍如何在 CentOS 6 和 CentOS 7 上配置网络接口绑定，这里以 bond0 为例。 首先，我们需要了解 CentOS 7 中配置 bond 的基本步骤： 1. **查看并加载 bonding 模块**： 在 CentOS 7 中，确保 ...
CentOS 8中使用NetworkManager创建和配置网卡bond-vlan.docx
03-24
CentOS 8中使用NetworkManager配置bond/vlan，以及为单物理网卡配置多个IP地址。
centos 7 下双网卡bond 与 trunk口的交换机通信(用作KVM虚拟机)
01-09
centos 7 下双网卡bond 与 trunk口的交换机通信 做这个首先要明白什么是trunk口 trunk 是实现不同网络设备的不同Vlan之间的通信 注意： 网卡也属于网络设备，设置vlan后也可以通信 先说下我的环境 网络工程师在两台...
Centos网卡bond模式配置 比较详细，希望能帮助到大家
01-30
nmcli connection add con-name ens32 ifname ens32 type bond-slave master bond0 nmcli connection add con-name ens36 ifname ens36 type bond-slave master bond0 3. 查看网口配置文件 执行完步骤 1 和 2 后，...
删除Redhat
weixin_34408717的博客
12-26 307
删除Redhat系统，只需将引导记录和系统数据删除即可，这些操作在救援模式下进行。 1. 进入救援模式：安装光盘引导，在boot提示符下输入：linux rescue 进入。 2. 删除引导记录：一般情况下，主引导记录装在硬盘的MBR（Master Boot Record）上。MBR为512字节，前446字节为引导信息，后64字节为硬盘分区表信息，最后两位为MBR签名。使...
bond解除 centos7_centos7.x网卡bond配置
weixin_39685674的博客
12-22 2558
本文摘抄自https://www.cnblogs.com/liwanggui/p/6807212.htmlcentos7网卡bond配置实验环境[root@localhost ~]# cat /etc/redhat-releaseCentOSLinux release 7.2.1511(Core)[root@localhost ~]# uname -r3.10.0-327.el7.x86_64l...
Centos 7 配置 Bonding
进京 的博客
12-22 6438
Centos 7 Bonding
Centos出现丢包问题解决办法
weixin_30511107的博客
09-13 2459
Centos出现丢包问题解决办法 环境介绍： 系统: CENTOS 5.5 64 bit 软件：nginx+mysql+php+NFS 故障排查： 早上突然收到nagios服务器check_icmp的报警，报警显示一台网站服务器的内网网络有问题。因为那台服务器挂载了内网的NFS，因此内网的网络就采用nagios的check_icmp来...
交换机loop detection 引起的服务器 bond0 口RX errors dropped 数量不断的增加
achejq的专栏
12-23 3069
RedHat 7配置bonding双网卡绑定
weixin_34342992的博客
06-17 857
redhat 7虽然新增了teaming技术支持双网卡绑定，但bonding技术依然可以沿用，本文测试的是bond的绑定方式。为了避免冲突，建议关闭NetworkManager：systemctl stop NetworkManager 、systemctl disable NetworkManager 。本文原始出处：江健龙的技术博客 http://jiangjianlong.blog.51ct...
bond解除 centos7_Centos7 / RHEL 7 双网卡绑定
weixin_32205057的博客
12-31 704
1. 简要双网卡绑定技术在centos7中使用了teaming技术，而在rhel6/centos7中使用的是bonding技术，在centos7中双网卡绑定既能使用teaming也可以使用bonding，这里推荐使用teaming技术，方便与查看和监控。2. 原理这里介绍两种最常见的双网卡绑定模式：(1) roundrobin - 轮询模式所有链路处于负载均衡状态，这种模式的特点增加了带宽，同时支...
[Linux基于rhel的高级网络部署] 配置bond网络 | 删除bond网络 | 配置team网络 | 删除team网络 | 配置网络桥接
Minz
05-21 7024
一，bond网络概述：允许管理员使用 bonding 内核模块和称为通道绑定接口的特殊网络接口将多个网络接口绑定到一个通道。根据选择的绑定模式 , 通道绑定使两个网络接口作为一个网络接口 , 从而增加带宽和冗余性模式 0 ( 平衡轮循 ) - 轮循策略 , 所有接口都使用采用轮循方式在所有 Slave 中传输封包模式 1 ( 主动备份 ) - 容错，一次只能使用一个 Slave 接口, 但是如果该...
redhat7.X与redhat6.X做网卡bond
yang1851965的博客
02-08 5829
 所谓bond，就是把多个物理网卡绑定成一个逻辑网卡，这样做可以实现增加带宽以及网卡的主备，不至于一个网卡坏了系统就不可用。首先说一下bond的模式： （1）balance-rr 轮询模式 mode=0 （2）active-backup 主被模式 mode=1 （3）balance-xor平衡模式 mode=2 （4）广播模式 mode=3 （5）802.3ad  链路聚合模式    mode=4...
centos7 网卡配置vlan_linux-Centos 7下bond与vlan技术的结合[推荐]
最新发布
06-06
好的，以下是CentOS 7下bond与vlan技术的结合的步骤： 1. 安装VLAN工具 ```bash yum install vlan -y ``` 2. 加载8021q内核模块 ```bash modprobe 8021q ``` 3. 配置bond 编辑网络配置文件`/etc/sysconfig/network-scripts/ifcfg-bond0`，添加以下内容： ```bash DEVICE=bond0 BOOTPROTO=none ONBOOT=yes BONDING_OPTS="mode=4 miimon=100" ``` 其中，`mode=4`表示bond模式为802.3ad，`miimon=100`表示检测网络连通性的时间间隔为100毫秒，可以根据实际情况修改。 4. 配置bond子网卡 编辑网络配置文件`/etc/sysconfig/network-scripts/ifcfg-eth0`和`/etc/sysconfig/network-scripts/ifcfg-eth1`，添加以下内容： ```bash DEVICE=eth0 BOOTPROTO=none ONBOOT=yes MASTER=bond0 SLAVE=yes ``` ```bash DEVICE=eth1 BOOTPROTO=none ONBOOT=yes MASTER=bond0 SLAVE=yes ``` 5. 配置VLAN 编辑VLAN配置文件`/etc/sysconfig/network-scripts/ifcfg-bond0.100`，其中100为VLAN ID，根据实际情况修改。添加以下内容： ```bash DEVICE=bond0.100 BOOTPROTO=none ONBOOT=yes VLAN=yes TYPE=Ethernet IPADDR=192.168.0.100 NETMASK=255.255.255.0 GATEWAY=192.168.0.1 ``` 6. 重启网络服务 ```bash systemctl restart network ``` 至此，CentOS 7下bond与vlan技术的结合的步骤已经完成。如果您还需要了解CentOS 7下网卡配置VLAN的步骤，可以参考以下文章： [CentOS 7下网卡配置VLAN](https://www.cnblogs.com/wangqiang2017/p/10143889.html)
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值