LACP Redhat With Cisco Switch and multiple Vlans

Redhat in Vlan10 (192.168.10.0/24)

Team10 : 192.168.10.100/24
GW: 192.168.10.254 ( The Gateway is interface Vlan10 in L3-SW)
DNS:8.8.8.8

The Cisco SW has 3 Vlans (10,20,30) and a routed interface to the Internet (Gig0/0) so we
could access the Redhat IP Teaming from outside.

[root@RHCE-SOC ~]# nmcli connection add type team con-name team10 ifname
team10 autoconnect yes config '{"runner": {"name": "lacp"}}'
ipv4.method manual ipv4.addresses 192.168.10.100/24 ipv4.gateway 192.168.10.254
ipv4.dns 8.8.8.8

[root@RHCE-SOC ~]# nmcli connection add type team-slave con-name t10-p1

ifname ens4 master team10
[root@RHCE-SOC ~]# nmcli connection add type team-slave con-name t10-p2
ifname ens5 master team10
[root@RHCE-SOC ~]# teamnl team10 ports
4: ens5: up 1000Mbit FD
3: ens4: up 1000Mbit FD

[root@RHCE-SOC ~]# teamdctl team10 state

setup:
runner: lacp
ports:
ens4
link watches:
link summary: up
instance[link_watch_0]:
name: ethtool
link: up
down count: 1
runner:
aggregator ID: 3, Selected
selected: yes
state: current
ens5
link watches:
link summary: up
instance[link_watch_0]:
name: ethtool
link: up
down count: 0
runner:
aggregator ID: 3, Selected
selected: yes
state: current
runner:
active: yes
fast rate: no
[root@RHCE-SOC ~]# teamdctl team10 config dump
{
"device": "team10",
"ports": {
"ens4": {
"link_watch": {
"name": "ethtool"
}
},
"ens5": {
"link_watch": {
"name": "ethtool"
}
}
},
"runner": {
"name": "lacp",
"tx_hash": [
"eth",
"ipv4",
"ipv6"
]
}
}
On Cisco SW:
Ping from PC1 From Vlan 20 ( 192.168.20.100)
Ping from PC2 from Vlan30 (192.168.30.100)
Ping from Redhat to Internet and i will disconnect port from Switch side (etherchannel) Gig0/1
and test the connectivity to outside

On SW

On Redhat

Done.