LACP Key Mismatch Issue Between Extreme 7520 VOSS and HPE 8360 VSX Switches

[nassar2000]

I am experiencing an issue with LACP key mismatch between my Extreme 7520 VOSS switches and HPE 8360 VSX switches. Here are the details of my setup and the problem:

Setup:

• Extreme Switches: 2 x Extreme 7520 VOSS
• HPE Switches: 2 x HPE 8360 VSX
• LACP Configuration: 4 ports configured as one LACP link

Issue: When configuring the LACP link, I encounter a key mismatch error on the Extreme switches. The LACP key values do not seem to match between the Extreme and HPE switches, causing the link to fail.

Steps Taken:

1. Verified LACP configuration on both Extreme and HPE switches.
2. Checked port settings (speed, duplex, etc.) to ensure they are identical.
3. Explicitly set the LACP key values on both switches to ensure they match.
4. Updated firmware on both Extreme and HPE switches to the latest versions.
5. Reviewed official documentation for both Extreme VOSS and HPE VSX switches.

1 2025-02-27T15:06:38.791Z  - 0x000ec5ba - 00000000 GlobalRouter LACP INFO lacpOperDisablePort: LACP operationally disabled on port 1/9 because the port's capability doesn't match key 1224 's capability
1 2025-02-27T15:06:38.791Z  - 0x00000026 - 00000000 GlobalRouter SW INFO Port 1/9 is a trunk port
1 2025-02-27T15:07:08.644Z  - 0x000ec5d1 - 00000000 GlobalRouter LACP INFO A churn condition has been detected for port 1/9 as the PARTNER is out of sync.

this log 

1 2025-02-27T15:07:23.002Z1 CP1 - 0x0000c5e7 - 00300001.200 DYNAMIC SET GlobalRouter HW INFO Link Down(1/9)
1 2025-02-27T15:07:23.002Z  CP1 - 0x00000026 - 00000000 GlobalRouter SW INFO Port 1/9 is a trunk port
1 2025-02-27T15:07:27.123Z  - 0x0000c5ec - 00300001.200 DYNAMIC CLEAR GlobalRouter HW INFO Link Up(1/9)
1 2025-02-27T15:07:27.123Z  - 0x000ec5ba - 00000000 GlobalRouter LACP INFO lacpOperDisablePort: LACP operationally disabled on port 1/9 because the port's capability doesn't match key 1224 's capability
1 2025-02-27T15:07:27.123Z  - 0x00000026 - 00000000 GlobalRouter SW INFO Port 1/9 is a trunk port
1 2025-02-27T15:07:57.040Z  - 0x000ec5d1 - 00000000 GlobalRouter LACP INFO A churn condition has been detected for port 1/9 as the PARTNER is out of sync.

[MJS]

Not sure if you found an answer here, but I just worked through this same issue last week. From the documentation:

https://extreme-networks.my.site.com/ExtrArticleDetail?an=000059673&q=MLT%20port%27s%20capability%20...

The LACP will aggregate ports depending on the consistency with the reference key port.
The reference key port is the first port UP with the same LACP key. When a LAG is formed, all the ports must have the same capabilities: same VLANs, same speed. So, when the LACP key is configured on a port, this port is added to a “same key” list. When LACP is enabled on port or the port is brought up its capabilities are compared with the first port UP having the same key.

In my case, I didn't have identical vlan assignment for all the ports in the MLT. They need to be the same. And in another instance I was troubleshooting, the client was attempting to use a 1Gb sfp and a 10Gb sfp in the same MLT. Same error message in both instances. This error message points to the Extreme side configuration, not anything on the HP side; although the link may not come up if configured incorrectly on the HP side, but you would get a different error message.

Good luck!

[Miguel-Angel_RO]

Here an example of config for port 2/3 on an Extreme switche:

#!!!!!Enable Globally LACP mode

#
# MLT CONFIGURATION
#
mlt 203 enable name "MLT-Description"
mlt 203 encapsulation dot1q
interface mlt 203
smlt
lacp enable key 203
exit
#
# VLAN CONFIGURATION
#
vlan mlt 100 203
vlan mlt 101 203
vlan mlt 110 203
vlan mlt 115 203
vlan mlt 246 203

# PORT CONFIGURATION - PHASE II
#
interface GigabitEthernet 2/3
shutdown
no spanning-tree mstp force-port-state enable
y
lacp key 203 aggregation enable
lacp enable
no shutdown
exit

Share your config on Extreme and HP to have a look.

Mig

[RobertD1]

Solution: VOSS : LACP port(s) operationally disabled with log "LACP operationally disabled on port <...

[CordScott]

The ports are not configured the same, in some way, which is a prerequisite for lacp. Is this SMLT?