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.

[CordScott]

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

[MJS]

Don't forget VLAN memberships. All ports need to be configured similarly. Check this out:
https://extreme-networks.my.site.com/ExtrArticleDetail?an=000059673&q=MLT%20port%27s%20capability%20...

[Brent_Addis]

I'm with Fredrik here. Doesn't appear to be a key issue (They don't share keys anyway, I've never ever had to set the same keys on both ends of a link), it's going to be capability, most likely speed since it actively mentions "Port capability".

[FredrikB-NN2]

I'm mostly familiar with EXOS in the Extreme portfolio, but this looks interesting:

LACP operationally disabled on port 1/9 because the port's capability doesn't match key 1224 's capability

All LAG links need to match in terms of speed and duplex if running LACP, which you do. Are you sure all links are the same speed and duplex, on both sides?

Is this an SMLT (Extreme end) to MLAG or to LAG in a stack (HPE end)?