Support for LACP short timeouts on N5K

krunal_shah · ‎03-29-2010

Anyone knowns if there is way to configure LACP timeout value. My customer is hitting a bug CSCta60232. Not sure if this bug has been fixed in recent version of NX-OS.

Also what is Cisco recommendation to form vPC. should customers use Active Active on both end of the vPC. If this is true then there might be many compatibility issues with different vendors.

N5K-1# sh lacp interface ex/y
Interface Ethernet1/4 is individual
Channel group is 4 port channel is Po4
PDUs sent: 395402
PDUs rcvd: 42817
Markers sent: 0
Markers rcvd: 0
Marker response sent: 0
Marker response rcvd: 0
Unknown packets rcvd: 44212
Illegal packets rcvd: 44212
Lag Id: [ [(0, 0-0-0-0-0-0, 0, 0, 0), (0, 0-0-0-0-0-0, 0, 0, 0)] ]
Operational as aggregated link since Fri Mar 26 14:22:15 2010

Local Port: Ethx/y    MAC Address= 0-d-ec-f2-c9-7c
System Identifier=0x8000,0-d-ec-f2-c9-7c
Port Identifier=0x8000,0x104
   Operational key=32772
   LACP_Activity=active
LACP_Timeout=Long Timeout (30s)
   Synchronization=IN_SYNC
   Collecting=true
   Distributing=true
Partner information refresh timeout=Short Timeout (3s)
Actor Admin State=(Ac-1:To-1:Ag-1:Sy-0:Co-0:Di-0:De-0:Ex-0)
Actor Oper State=(Ac-1:To-0:Ag-1:Sy-1:Co-1:Di-1:De-1:Ex-0)
Neighbor: 0/0
MAC Address= 0-0-0-0-0-0
System Identifier=0x0,0-0-0-0-0-0
Port Identifier=0x0,0x0
Operational key=0
   LACP_Activity=unknown
LACP_Timeout=short Timeout (1s) <<<<<<<<<<<<<< Mismatch in parameters of LACP from Neighbor.
   Synchronization=NOT_IN_SYNC
   Collecting=false
   Distributing=false
Partner Admin State=(Ac-0:To-1:Ag-0:Sy-0:Co-0:Di-0:De-0:Ex-0)
Partner Oper State=(Ac-0:To-1:Ag-0:Sy-0:Co-0:Di-0:De-0:Ex-0)

Ganesh Hariharan · ‎04-01-2010

Anyone knowns if there is way to
configure LACP timeout value. My cusotmer is hitting CSCta60232. Not
sure if this bug has been fixed in recent version of NX-OS.
Also
what is Cisco recommendation to form vPC. should cusotmer use Active
Active on both end of the vPC. If this is true then there might be many
compatibility issues with different vendors.
N5K-1# sh lacp  interface ex/y
Interface Ethernet1/4  is individual 
  Channel group is 4  port channel is Po4 
  PDUs sent: 395402 
  PDUs rcvd: 42817 
  Markers sent: 0 
  Markers rcvd: 0 
  Marker response sent:  0 
  Marker response rcvd:  0 
  Unknown packets rcvd:  44212 
  Illegal packets rcvd:  44212 
Lag Id: [ [(0,  0-0-0-0-0-0, 0, 0, 0), (0, 0-0-0-0-0-0, 0, 0, 0)] ] 
Operational as  aggregated link since Fri Mar 26 14:22:15 2010 
  
Local Port: Ethx/y    MAC Address= 0-d-ec-f2-c9-7c 
  System  Identifier=0x8000,0-d-ec-f2-c9-7c 
  Port  Identifier=0x8000,0x104 
   Operational key=32772 
   LACP_Activity=active 
  LACP_Timeout=Long  Timeout (30s) 
   Synchronization=IN_SYNC 
   Collecting=true 
   Distributing=true 
  Partner information  refresh timeout=Short Timeout (3s) 
Actor  Admin State=(Ac-1:To-1:Ag-1:Sy-0:Co-0:Di-0:De-0:Ex-0) 
Actor Oper  State=(Ac-1:To-0:Ag-1:Sy-1:Co-1:Di-1:De-1:Ex-0) 
Neighbor:  0/0 
  MAC Address=  0-0-0-0-0-0 
  System  Identifier=0x0,0-0-0-0-0-0 
  Port  Identifier=0x0,0x0 
  Operational  key=0 
   LACP_Activity=unknown 
  LACP_Timeout=short  Timeout (1s)  <<<<<<<<<<<<<<  Mismatch in parameters of LACP from Neighbor. 
   Synchronization=NOT_IN_SYNC 
   Collecting=false 
   Distributing=false 
Partner Admin  State=(Ac-0:To-1:Ag-0:Sy-0:Co-0:Di-0:De-0:Ex-0) 
Partner Oper State=(Ac-0:To-1:Ag-0:Sy-0:Co-0:Di-0:De-0:Ex-0)

Hi ,

As per the bug detail in cisco sitestill now they have not realesed the fixed in version for this bug and short timeout cannot be configured in nexus 5k.

CSCta60232 Bug Details

Add configurable short timeout to Nexus 5000

Symptom:
The Nexus 5000 does not currently have support to request short timeout.

NOTE: The Nexus 5000 does move to a short timeout when the partner timeout is short. This is because the partner dictates the timeout for the actor. The N5k cannot get the partner to reciprocate due to it not being able to be configured for short timeout.

Workaround:
The channel should still form, but each side is using different timeouts. Whichever timeout is lost first will trigger the channel to re-initialization.

It is recommended to use long-timers on both sides until 4.2(1)N1(1)

Further Problem Description:

To identify the partner timeout:

sho lacp interface eth X/Y
Neighbor: 0/0
MAC Address= 0-0-0-0-0-0
System Identifier=0x0,0-0-0-0-0-0
Port Identifier=0x0,0x0
Operational key=0
LACP_Activity=unknown
LACP_Timeout=short Timeout (1s)<<<
Synchronization=NOT_IN_SYNC
Collecting=false
Distributing=false

Status
Fixed
(Resolved)
Severity
3 - moderate

Last Modified
In Last 3 Days

Product
Cisco Nexus 5000 Series Switches

Technology

1st Found-In
4.1(3)N1(0.164)

Fixed-In
Release-Pending

Component(s)
lacp

Hope to Help !!

Ganesh.H

Cisco are currently donating money to the Haiti earthquake appeal for every rating so please consider rating all helpful posts.

krunal_shah · ‎04-13-2010

Actual issue is related to N5K not accepting the LACP size not more then 128 bytes long. If anyone using simlar version of code and having same issue.

Use debug lacp packets and see following message will apear on the switch.

2010 Apr 1 17:27:58.215418 lacp: lacp_net_rx_data(242): Rcvd BAD PDU: Sanity failed: if_idx 0x1a00e000: pkt_len 128

Also in show lacp interface eth x/y will show illegal packets counter increasing rapidly.

This issue id related to software bug :

CSCtg01091 Accept LACPDU's that exceed 128B standard length

Above bug should be fixed in 4.2 code.

skint · ‎04-25-2010

Hi,

Although Cisco does not come right out and say it, the design guides for the N5K all point towards an Active/Passive relationship when forming vPC's.

http://www.cisco.com/en/US/products/ps9670/products_implementation_design_guides_list.html

Chapter 6 makes the most references, but they hint towards a hierarchical relationship moving towards the access layer.

-skint

kribrath · ‎02-21-2017

Hi!

I know this is an outdated post, but it comes up again in my network this year, theres a setting in Windows 2012Server enviroment that can change this behavior.

https://support.microsoft.com/en-us/help/3109099/update-adds-support-for-the-slow-timer-in-lacp-in-windows-server-2012-r2

Fast LACP is not compatible with ISSU (In service software upgrade) and this hotfix should be done on servers before performing an ISSU.

//BR
Kristian