NIC Teaming

Issues related to configuring your network
Post Reply
kocharli
Posts: 1
Joined: 2018/11/12 16:44:44

NIC Teaming

Post by kocharli » 2018/11/12 17:17:45

Hello Everyone!

I'm trying to configure Teaming with two NICs. I'm running CentOS 7.5.1804 on VMware Workstation 14.1.2.

Steps I have done:
1) added team interface with below command

Code: Select all

[root@client1 ~]# nmcli c a type team ifname myteam1 con-name myteam1 config my.conf
Connection 'myteam1' (6d95c6a4-cde9-437f-81e2-6c2cc2c0064e) successfully added.
Content of my.conf file:

Code: Select all

[root@client1 ~]# cat my.conf 
{
	"device":	"myteam1",
	"runner":	{"name": "activebackup"}
}
2) I have added 2 slave interfaces:

Code: Select all

[root@client1 ~]# nmcli c a type ethernet ifname ens33 con-name myteam1_slave1 master myteam1 
Connection 'myteam1_slave1' (dd1d1bde-ff15-4d53-a174-96225e95f431) successfully added.
[root@client1 ~]# nmcli c a type ethernet ifname ens37 con-name myteam1_slave2 master myteam1 
Connection 'myteam1_slave2' (bcd1319c-cb9b-4290-87ab-ef35d2a127b7) successfully added.
3) Restarted network and NetworkManager services.
4) Checked the my team interface state:

Code: Select all

[root@client1 ~]# teamdctl myteam1 state
setup:
  runner: activebackup
ports:
  ens33
    link watches:
      link summary: up
      instance[link_watch_0]:
        name: ethtool
        link: up
        down count: 0
  ens37
    link watches:
      link summary: up
      instance[link_watch_0]:
        name: ethtool
        link: up
        down count: 0
runner:
  active port: ens33
When I try to check connection everything is fine. But when I try to take down myteam1_slave1 (ens33) I am losing connectivity despite the fact that it switches runner active port to ens37.

Please assist!

Below information maybe helpful for you.

Code: Select all

[root@client1 ~]# nmcli con down myteam1_slave1
Connection 'myteam1_slave1' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/3)
[root@client1 ~]# 
[root@client1 ~]# teamdctl myteam1 state
setup:
  runner: activebackup
ports:
  ens37
    link watches:
      link summary: up
      instance[link_watch_0]:
        name: ethtool
        link: up
        down count: 0
runner:
  active port: ens37
[root@client1 ~]# 
[root@client1 ~]# 
[root@client1 ~]# ping google.com
^C
[root@client1 ~]# nmcli c s
NAME            UUID                                  TYPE      DEVICE  
myteam1         6d95c6a4-cde9-437f-81e2-6c2cc2c0064e  team      myteam1 
myteam1_slave2  bcd1319c-cb9b-4290-87ab-ef35d2a127b7  ethernet  ens37   
virbr0          cf294a4d-b615-4cb3-b191-2c806fd4eb9b  bridge    virbr0  
myteam1_slave1  dd1d1bde-ff15-4d53-a174-96225e95f431  ethernet  --      
[root@client1 ~]# nmcli d s
DEVICE      TYPE      STATE         CONNECTION     
myteam1     team      connected     myteam1        
virbr0      bridge    connected     virbr0         
ens37       ethernet  connected     myteam1_slave2 
ens33       ethernet  disconnected  --             
lo          loopback  unmanaged     --             
virbr0-nic  tun       unmanaged     --             
[root@client1 ~]# 

Code: Select all

[root@client1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-myteam1
TEAM_CONFIG=$'{\n\t\"device\":\t\"myteam1\",\n\t\"runner\":\t{\"name\": \"activebackup\"}\n}\n'
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=myteam1
UUID=6d95c6a4-cde9-437f-81e2-6c2cc2c0064e
DEVICE=myteam1
ONBOOT=yes
DEVICETYPE=Team
[root@client1 ~]# 

Code: Select all

[root@client1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-myteam1_slave1
NAME=myteam1_slave1
UUID=dd1d1bde-ff15-4d53-a174-96225e95f431
DEVICE=ens33
ONBOOT=yes
TEAM_MASTER=myteam1
DEVICETYPE=TeamPort
[root@client1 ~]# 

Code: Select all

[root@client1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-myteam1_slave2
NAME=myteam1_slave2
UUID=bcd1319c-cb9b-4290-87ab-ef35d2a127b7
DEVICE=ens37
ONBOOT=yes
TEAM_MASTER=myteam1
DEVICETYPE=TeamPort
[root@client1 ~]# 

aks
Posts: 2567
Joined: 2014/09/20 11:22:14

Re: NIC Teaming

Post by aks » 2018/11/14 21:24:39

But when I try to take down myteam1_slave1
How? Administratively?

AFIACS, your fail over event is based on "layer1/2) physical link.
Perhaps review https://access.redhat.com/documentation ... md_runners

Post Reply