Shulou(Shulou.com)06/01 Report--

This article mainly shows you the "example analysis of dual Nic binding and related problems in Centos7.2", which is easy to understand and well-organized. I hope it can help you solve your doubts. Let the editor lead you to study and learn the "sample analysis of dual Nic binding and related problems in Centos7.2".

Preface

Recently working as an online server, installing centos7.2 x64 to minimize installation, need to do link aggregation, dual network card binding. Test OK on both centos 6.x and centos 7, so go straight to it.

As described, the following environments are implemented in a virtual machine:

System: centos7.2 x64 minimizes installation.

For demonstration purposes, there are three network cards:

Eno16777736: bridge Network Card: 10.0.0.11Universe 24

The remaining two NICs are ready to bind:

Eno33554984

Eno50332208

[root@bogon] # nmcli con sh NAME UUID TYPE DEVICE Wired connection 2 bf0cf9b6-c7fb-4c0a-ada4-abfb650dd5f0 802-3-ethernet-- Wired connection 1 5b4e0b3e-c469-404c root@bogon 8839-76d18442fc20 802-3-ethernet-- eno16777736 100e462e-c0d0-4271-9b5a-1c8e47ff0d03 802-3-ethernet eno16777736 [root@bogon] # nmcli con del 5b4e0b3e-c469-404c Wired connection 8839-76d18442fc20 bf0cf9b6-c7fb-4c0a-ada4-abfb650dd5f0Connection 'Wired connection 1' (5b4e0b3e-c469-404c Mel 8839- 76d18442fc20) successfully deleted.Connection 'Wired connection 2' (bf0cf9b6-c7fb-4c0a-ada4-abfb650dd5f0) successfully deleted. [root@bogon ~] # nmcli con add type team ifname team0 con-name team0 config' {"runner": {"name": "roundrobin"}} 'Connection' team0' (913f05c2-15d8-49a9-a35f-8bc5ee843c0c) successfully added. [root@bogon ~] # nmcli con add type team-slave ifname eno50332208 con-name team0-port2 master team0Connection 'team0-port2' (1583854c-1f85-4c76-8cc7- C643071d4b82) successfully added. [root@bogon ~] # nmcli con mod team0 ipv4.address "192.168.121.100 8cc7-c643071d4b82 24" [root@bogon ~] # nmcli con mod team0 ipv4.method manual [root@bogon ~] # nmcli con sh NAME UUID TYPE DEVICE eno16777736 100e462e-c0d0-4271-9b5a-1c8e47ff0d03 802-3-ethernet eno16777736 team0-port2 1583854c-1f85-4c76-8cc7-c643071d4b82 802-3-ethernet-team0-port1 bfd408b4-76d9-4f5c-ad5b-4d92430eb6ba 802-3-ethernet-- Team0 913f05c2-15d8-49a9-a35f-8bc5ee843c0c team-

There's nothing wrong with being here.

[root@bogon ~] # nmcli con up team0Error: Connection activation failed: NetworkManager plugin for 'team' unavailable

What the hell? The NetworkManager "team" plug-in is not available. So we started canvassing.

Whether there is a team module

[root@bogon ~] # lsmod | egrep * team*

No. Then just restart network.

[root@bogon] # systemctl restart network Job for network.service failed because the control process exited with error code. See "systemctl status network.service" and "journalctl-xe" for details. [root@bogon ~] # systemctl status network...Mar 25 04:47:56 bogon network [2742]: Bringing up interface team0: Error: Connection activation failed: NetworkManager plugin for 'team' unavailableMar 25 04:47:56 bogon network [2742]: [FAILED].

The same error report, what package is not installed to?

[root@bogon ~] # yum list all | grep NetworkManager*NetworkManager.x86_64 1VR 1.0.6-27.el7 @ anacondaNetworkManager-libnm.x86_64 1Rose 1.0.6-27.el7 @ anacondaNetworkManager-tui.x86_64 1Rover 1.0.6-27.el7 @ anacondaNetworkManager-wifi.x86_64 1RO 1.0.6-27.el7 @ anacondaNetworkManager-adsl.x86_64 1vig 1.0.6-27.el7 Yum NetworkManager-bluetooth.x86_64 127.el7 yum NetworkManager-libreswan.x86_64 1.0.6-27.el7 yum NetworkManager-glib.x86_64 1RV 1.0.6-27.el7 yum NetworkManager-libreswan.x86_64 1.0.6-3.el7 yum NetworkManager-libreswan-gnome.x86_64 1.0.6-3.el7 yum NetworkManager-team.x86_64 1RO 1.0.6-27.el7 yum NetworkManager-wwan.x86_64 1RO 1.0.6-27.el7 yum

Oh, there is a NetworkManager-team that is not installed.

[root@bogon ~] # yum install NetworkManager-team-y

Then try again:

[root@bogon] # nmcli con sh NAME UUID TYPE DEVICE eno16777736 100e462e-c0d0-4271-9b5a-1c8e47ff0d03 802-3-ethernet eno16777736 team0-port2 1583854c-1f85-4c76-8cc7-c643071d4b82 802-3-ethernet-team0-port1 bfd408b4-76d9-4f5c-ad5b-4d92430eb6ba 802-3-ethernet-team0 913f05c2-15d8-49a9-a35f-8bc5ee843c0c team-- [root@bogon] # nmcli con up team0Error: Connection activation failed: NetworkManager plugin for 'team' unavailable

Nima, it's the same mistake. It's embarrassing. Then restart NetworkManager and take a look.

[root@bogon] # systemctl restart NetworkManager [root@bogon] # nmcli con sh NAME UUID TYPE DEVICE team0-port2 1583854c-1f85-4c76-8cc7-c643071d4b82 802-3-ethernet eno50332208 eno16777736 100e462e-c0d0-4271-9b5a-1c8e47ff0d03 802-3-ethernet eno16777736 team0-port1 bfd408b4-76d9-4f5c-ad5b-4d92430eb6ba 802-3-ethernet eno33554984 team0 913f05c2-15d8-49a9-a35f-8bc5ee843c0c team team0

Okay? What the fuck! Check to see if it is in roundrobin mode.

[root@bogon ~] # teamdctl team0 stsetup: runner: roundrobinports: eno33554984 link watches: link summary: up instance [link _ watch_0]: name: ethtool link: up down count: 0 eno50332208 link watches: link summary: up instance [link _ watch_0]: name: ethtool link: up down count: 0 [root@bogon ~] # teamnl team0 ports 4: eno50332208: up 1000Mbit FD 3: eno33554984: up 1000Mbit FD

Everything OK, old buddy, is in the heart.

Next, test roundrobin.

The following is explained here: the bind mode of roundrobin:

Let's first talk about the principle of the network card bind:

By virtualizing two or more network cards to a logical network card through the software, there are many modes of bind. For example, the one above is the link aggregation mode. When using this mode, the mac addresses of the two physical network cards and logical network cards are set to be the same. As we all know, we do link aggregation to allow multiple physical network cards to aggregate together to expand data bandwidth. Since we are logically a network card, then the mac address must be the same, right? Otherwise, if we connect to the switch or router, the logical network card will be the mac address of the physical network card 1 and the address of the physical network card 2. Then how can the data be transmitted.

In link aggregation, because it is a bundled mode of two physical network cards, if one of the network cards down falls off, the whole link will crash.

It is as follows:

The above is all the contents of this article entitled "sample Analysis of double Network Card binding and related problems in Centos7.2". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.