LACP Aggregate Down between OAS-6000 and 6860

[Rens]

Hello

Anyone experience with connecting a OAW-6000 via LACP to an 6860 stack of switches?

Somehow the different interfaces leave the LACP agg for a short while, sometimes at the same time like today:
Nov 2 09:48:15 NLAMS-1105AT-SW01 swlogd: linkAggNi main info(5) LACP Link 4 -> 2 is OUT_OF_SYNC agg=5
Nov 2 09:48:15 NLAMS-1105AT-SW01 swlogd: linkAggCmm main info(5) Port Leave .LACP port: 1005 agg: 5 link:UP agg_admin:UP timedout:TRUE
Nov 2 09:48:15 NLAMS-1105AT-SW01 swlogd: linkAggCmm main info(5) Port Join . LACP port: 1/1/5(1005) agg: 5
Nov 2 09:48:16 NLAMS-1105AT-SW01 swlogd: linkAggNi main info(5) LACP Link 4 -> 2 is IN_SYNC agg_id=5
Nov 2 09:51:18 NLAMS-1105AT-SW01 swlogd: linkAggCmm main info(5) Port Leave .LACP port: 1005 agg: 5 link:UP agg_admin:UP timedout:TRUE
Nov 2 09:51:18 NLAMS-1105AT-SW01 swlogd: linkAggNi main info(5) LACP Link 4 -> 2 is OUT_OF_SYNC agg=5
Nov 2 09:51:19 NLAMS-1105AT-SW01 swlogd: linkAggCmm main info(5) Aggregate Down . LACP port: 2/1/5(101005) agg: 5 link:UP agg_admin:UP timedout:TRUE
Nov 2 09:51:19 NLAMS-1105AT-SW01 swlogd: linkAggCmm main info(5) Aggregate UP . LACP port: 1/1/5(1005) agg: 5
Nov 2 09:51:19 NLAMS-1105AT-SW01 swlogd: linkAggCmm main info(5) Port Join . LACP port: 2/1/5(101005) agg: 5
Nov 2 09:51:19 NLAMS-1105AT-SW01 swlogd: linkAggNi main info(5) LACP Link 4 -> 2 is IN_SYNC agg_id=5

Do I need to tune the lacp settings?

I hope someone can assist us.

With kind regards,

Rens

[cedric1]

Hello

You have no interface down/up or phy. link flapping ?

Can you test to go with long timeout instead of short timeout.

Example:
-> no linkagg lacp port 1/1 actor admin-state timeout

After enabling long timeout command and execute below show command to confirm the timout value is set is “0”. By default the value is “1” // value “1” is short time out and value “0” is long timeout//

Output:
-> show linkagg port 1/1

Dynamic Aggregable Port
SNMP Id : 1001,
Chassis/Slot/Port : 1/1,
Administrative State : ENABLED,
Operational State : DOWN,
Port State : CONFIGURED,
Link State : DOWN,
Selected Agg Number : NONE,
Primary port : UNKNOWN
LACP
Actor System Priority : 0,
Actor System Id : [e8:e7:32:e4cd],
Actor Admin Key : 122,
Actor Oper Key : 122,
Partner Admin System Priority : 0,
Partner Oper System Priority : 0,
Partner Admin System Id : [00:00:00:00:00:00],
Partner Oper System Id : [00:00:00:00:00:00],
Partner Admin Key : 0,
Partner Oper Key : 0,
Selected Agg Id : 0,
Attached Agg Id : 0,
Actor Port : 2,
Actor Port Priority : 0,
Partner Admin Port : 0,
Partner Oper Port : 0,
Partner Admin Port Priority : 0,
Partner Oper Port Priority : 0,
Actor Admin State : act1.tim0.agg1.syn0.col0.dis0.def1.exp0,
Actor Oper State : act1.tim0.agg1.syn0.col0.dis0.def1.exp0,
Partner Admin State : act0.tim0.agg1.syn0.col1.dis1.def1.exp0,
Partner Oper State : act0.tim0.agg1.syn0.col1.dis1.def1.exp0

Here tim0 say long timeout :

Actor Admin State : act1.tim0.agg1.syn0.col0.dis0.def1.exp0,
Actor Oper State : act1.tim0.agg1.syn0.col0.dis0.def1.exp0,

[Rens]

Hello Cedric,

The interfaces themselves don't go down, they simply leave and join the linkagg.

We started with "linkagg lacp port 1/1 actor admin-state active", which then gave the issue.
Then we used "linkagg lacp port 1/1 actor admin-state timeout" which still didn't work.
Obviously a different command from yours.

This morning I found a different command "linkagg lacp port 1/1 actor admin-state default" which as far as I understand is the same as yours but I haven't tested.

I have a eSR for this with Alcatel and they are currently analysing wireshark traces we created. Offcourse it only happens when users are connected. Yesterday and today (Sunday) the links didn't leave but to make sure Monday the users can work without interruption today I finaly ended up removing the linkagg and replacing it with two links of which one is blocked by spanning tree.

When I have some answers from Alcatel I'll post them

Regards,

Rens

[slaskaridis]

hi
did you get a solution for this issue ?? please post here.