I set up the interface aggregation as follows:
#vi ifcfg-bond0
DEVICE=bond0
BOOTPROTO=none
BONDING_OPTS="mode=balance-rr"
USERCTL=no
NAME=bond0
ONBOOT=yes
TYPE=bond
#vi ifcfg-bond0.102
DEVICE=bond0.102
BOOTPROTO=static
IPADDR=10.20.2.3
NETMASK=255.255.255.0
GATEWAY=10.20.2.254
NAME=bond0.102
ONBOOT=yes
VLAN=yes
#vi ifcfg-enp4s0f0
TYPE=Ethernet
NAME=enp4s0f0
ONBOOT=yes
MASTER=bond0
DEVICE=enp4s0f0
SLAVE=yes
#vi ifcfg-enp4s0f1
TYPE=Ethernet
NAME=enp4s0f0
ONBOOT=yes
MASTER=bond0
DEVICE=enp4s0f0
SLAVE=yes
When I started the network card using the command "service network start" , there was no problem.
However, when I execute the command "service network restart", the network card cannot start successfully.
I execute the command "systemctl status network.service" to see the details below:
Because centos7 64-bit system is used, so also try the NMCLI method.
Using the NMCLI to create a TEAM interface, you can PING the gateway, but not other devices in the same segment.
It's not clear whether it's the system itself or the configuration, after all, the same configuration, no problems found on other devices.
CentOS7 64-bit system network card aggregation model problem.
-
- Posts: 1
- Joined: 2018/06/16 10:32:12
Re: CentOS7 64-bit system network card aggregation model problem.
It appears to be complaining about an interface with a name that starts 'enp5' but because you didn't use the -l switch to systemctl status, the output was truncated and it is impossible to tell which one.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
-
- Posts: 2019
- Joined: 2015/02/17 15:14:33
- Location: Bulgaria
- Contact:
Re: CentOS7 64-bit system network card aggregation model problem.
The preffered method is to use NetworkManager.service .
If you are unfamiliar with the 'nmtui' and 'nmcli' you can always set the configuration files and then just restart the NetworkManager.service .
Also a very nice command is.
If you are unfamiliar with the 'nmtui' and 'nmcli' you can always set the configuration files and then just restart the NetworkManager.service .
Also a very nice command is
Code: Select all
nmcli con show