LACP issues

[Jason_Hilt]

I have some 450G2 switches that I can not get LACP LAG to work on. Core 670 switch is grouping ports 19 and 20. Sh lacp lag displays:
Member Port Rx Sel Mux Actor Partner
Port Priority State Logic State Flags Port
--------------------------------------------------------------------------------
19 0 Current Selected Collect-Dist A-GSCD-- 1049
20 0 Current Selected Attached A-GS---- 2049
================================================================================
Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization
C-Collecting, D-Distributing, F-Defaulted, E-Expired

Remote switch shows:
Member Port Rx Sel Mux Actor Partner
Port Priority State Logic State Flags Port
--------------------------------------------------------------------------------
1:49 0 Current Selected Collect-Dist A-GSCD-- 1019
2:49 0 Defaulted Unselected Detached A-G---F- 0
================================================================================
Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization
C-Collecting, D-Distributing, F-Defaulted, E-Expired

I have tried moving the fiber cable to different pairs. removed and added the grouping. Disabled ports, renabled ports, all with no affect. Link lights are on both switches.

What can be wrong?

Not sure if this is a connected issue or not, but all of my network switches are also showing a loop detected on the uplink port from the core. ELRP is active on edge switches with the uplink ports excluded.
Slot-1: [CLI:vlan:2] LOOP DETECTED : 846382 transmitted, 9114521 received, ingress slot:port (1:49) egress slot:port (1:49)

Fairly new to Extreme switching so bear with me.

[Jason_Hilt]

Is this a random issue as we have quite a few other buildings with the same switches, SFPs, and cables that are working just fine running 21.1.1.4?

[Ty_Kolff]

We discovered an issue with LACP last week with EXOS version 21.1.2. It's a known issue that will be resolved in 21.1.3, but it hasn't been released yet. In this case, we had to roll back to 16.1.4.2 patch 1-7.

[Jason_Hilt]

ELRP is not configured on the core switch. Only on edge switches.

[Patrick_Voss]

Hello Jason,

The "A" indicates the port is active. When there is a "Y" it means that it is active in the share group. So in this case port 20 and 2:49 are not passing traffic. The ELRP messages may be unrelated to the LACP issue. I would look into the other side of 1:49 and see if ELRP is being triggered on that switch.

[Jason_Hilt]

There is only a Y on one port on each end. The other port shows a - for the Agg Mbr.
Core:
19 19 LACP 1 L2 A 19 Y A 8
L2 20 - A 14
Remote switch:
1:49 1:49 LACP 1 L2 A 1:49 Y A 3
L2 2:49 - A 12
================================================================================

Sh lacp lag on the core is:
Member Port Rx Sel Mux Actor Partner
Port Priority State Logic State Flags Port
--------------------------------------------------------------------------------
19 0 Current Selected Collect-Dist A-GSCD-- 1049
20 0 Current Selected Attached A-GS---- 2049
================================================================================

Sh lacp lag on the remote switch is:
Member Port Rx Sel Mux Actor Partner
Port Priority State Logic State Flags Port
--------------------------------------------------------------------------------
1:49 0 Current Selected Collect-Dist A-GSCD-- 1019
2:49 0 Defaulted Unselected Detached A-G---F- 0
================================================================================

Connections are 10gig fiber on SM fiber using Extreme Network branded SumitomoElectric SFP+ optics.