KVM team and bridge NIC

Issues related to configuring your network
Post Reply
PoPNicoW
Posts: 1
Joined: 2018/01/31 13:11:15

KVM team and bridge NIC

Post by PoPNicoW » 2018/01/31 13:25:28

Hello All,

i'm currently trying to set up teaming NIC with bridge to use KVM and cloudstack.
i'm stuck as one of my teaming remains down...

so first question : is it possible to set up a bridge over a teamed NIC ?
As all of the "how-to" document i have check talk about bonded nic with bridge

Here the configuration and command used :
team-TRUNK with nic ens1f1/enp2s0f1

nmcli connection add type team ifname TRUNK
nmcli con add type team-slave con-name TRUNK-port1 ifname enp2s0f1 master TRUNK
nmcli con add type team-slave con-name TRUNK-port2 ifname ens1f1 master TRUNK

the configuration IP on basic nic has been deleted

Bridge has been created manually :
DEVICE=cloudbr1
BOOTPROTO=static
IPADDR=192.168.1.100
NETMASK=255.255.255.0
GATEWAY=192.168.1.254
DNS1=8.8.8.8
ONBOOT=yes
TYPE=Bridge

At this time, i get this erro when i try to up the teaming
Master Device 'TRUNK' can't be activated: Device unmanaged or not available

i did multiple time the configuration but i have still the error.

here the configuration of the device team-TRUNK
DEVICE=TRUNK
PROXY_METHOD=none
BOOTPROTO=static
DEFROUTE=yes
IPv4_FAILURE_FATAL=no
NAME=team-TRUNK
UUID=xxxx.xxxxx.xxxxx….
ONBOOT=yes
DEVICETYPE=Team
BRIDGE=cloudbr1

Configuration of port1 from team-TRUNK :
NAME=TRUNK-port1
UUID=XXXXXXX.XXXX.XXXXX…
DEVICE=enp2s0f1
ONBOOT=yes
TEAM_MASTER=TRUNK
DEVICETYPE=TeamPort

For information, this team/bridge will be use with VLAn so i ditnt set up any IP configuration.

don't know where the mistake could be...i performed a teaming NIC (without bridge) with no problem earlier.
any help will be appriciate,

Best regards,
PoP!

User avatar
jlehtone
Posts: 1957
Joined: 2007/12/11 08:17:33
Location: Finland

Re: KVM team and bridge NIC

Post by jlehtone » 2018/01/31 14:52:19

I have no experience about teams. Hence,

Code: Select all

man nmcli-examples
Interestingly, uses different type for the team-slaves.

Furthermore, the bridge can be defined with nmcli and then the team probably should be enslaved to the bridge (with nmcli). Mixing use of nmcli and direct edits of config files may work too, but "nmcli con edit" has command 'verify' (with fix option) to solve some hurdless.

Post Reply