Reset Search
 

 

Article

MCT CCEP LAG is going in to LACP-BLOCKED

« Go Back

Information

 
TitleMCT CCEP LAG is going in to LACP-BLOCKED
Symptoms
  • MLX MCT CCEP LAG port was going in to LACP-BLOCKED
Oct 31 10:35:44:I:System: Interface ethernet 1/6, state up
Oct 31 10:35:44:W:LACP: ethernet 1/6 state changes from LACP-BLOCKED to FORWARD
Oct 31 10:35:44:I:LACP: Port 1/6 mux state transition: not aggregate -> aggregate
Oct 31 10:35:02:I:LACP: Port 1/6 partner port state transition: not aggregate -> aggregate
Oct 31 10:35:02:I:LACP: Port 1/6 rx state transition: defaulted -> current
Oct 31 10:34:40:I:LACP: Port 1/6 rx state transition: current -> expired (reason: timeout)
Oct 31 10:34:38:I:CLUSTER FSM: Cluster <cluster name> (Id: <Id>), client <client ID> (RBridge Id: <Rbridge Id>) - Local client CCEP down
Oct 31 10:34:38:I:System: Interface ethernet 1/6, state down - lacp block
Oct 31 10:34:38:I:LACP: Port 1/6 mux state transition: aggregate -> not aggregate (reason: peer is out of sync)
Oct 31 10:34:38:W:LACP: ethernet 1/6 state changes from FORWARD to LACP-BLOCKED
  • Possible stack instability was seen on the connected peer stack for each instance
  • Multiple CCEP LAG ports were going in to LACP-BLOCKED to different peer ICX7450 stacks
Environment
  • MLX
  • MCT
  • NetIron
  • ICX7450
Cause
  • For each instance possible stack instability was present on the peer ICX7450 stack
Mar 17 05:48:35:I:Stack: Stack unit 1 has been elected as ACTIVE unit of the stack system
Mar 17 05:48:33:I:System: Logical link on dynamic lag interface ethernet 4/2/1 is up.
Mar 17 05:47:29:I:System: Logical link on dynamic lag interface ethernet 4/2/1 is down.
Mar 17 05:46:56:W:Warning! U1, mac= xxxx.xxxx.xxxx, ages out stack-port 1/4/1 linking to u4.
Resolution
  • Ruckus/Arris/Commscope was engaged to review the ICX7450 logs and they recommended implementing 802.1w
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255