RHEL Teaming LACP

Latest response

Hi all,
Environment:

Rhel 7.9
3.10.0-1160.el7.x86_64
libteam-1.29-3.el7.x86_64
NIC: Ethernet Connection X722 for 10GbE SFP+
driver: i40e
version: 2.8.20-k
firmware-version: 4.11 0x80001fa0 1.2585.0
Cisco Nexus 5k switches

LACP Runner configuration
team.config:                            {"device": "team10G", "runner": {"name": "lacp", "fast_rate": true, "tx_hash": ["eth", "ipv4", "ipv6"]}, "link_watch": {"name": "ethtool"}, "ports": {"eno1": {}, "eno2": {}}}

setup:
  runner: lacp
ports:
  eno1
    link watches:
      link summary: up
      instance[link_watch_0]:
        name: ethtool
        link: up
        down count: 0
    runner:
      aggregator ID: 2, Selected
      selected: yes
      state: current
  eno2
    link watches:
      link summary: up
      instance[link_watch_0]:
        name: ethtool
        link: up
        down count: 0
    runner:
      aggregator ID: 2, Selected
      selected: yes
      state: current
runner:
  active: yes
  fast rate: yes

We have setup teaming/lacp in two 10G slave interfaces on the physical server. When I bring down connection from the eno2 card I still have connectivity. Bring eno2 up again, so both NICs are up and current. Then when I bring down connection from the eno1 card I lose connectivity.

I am not sure whether this is an issue with the server configuration or on the Cisco Nexus switches.

Has anyone come across this before? Is it worth destroying this configuration and trying bond instead?

Thanks in advance

rg

Responses