HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem Virtual Connect
cancel
Showing results for 
Search instead for 
Did you mean: 

LACP issues with Virtual Connect v3.18

 
chuckk281
Trusted Contributor

LACP issues with Virtual Connect v3.18

Joe was having LACP issues with a Nexus switch:

 

******************

 

Has anyone experienced issues with losing LACP connectivity, Cisco Nexus disabled the port within 24hrs.

 

Here are the errors from the switch:

2011 Oct 26 11:03:29 NJDC-B-17-N5K-3 %LACP-FEX102-5-LACP_SUSPEND_INDIVIDUAL: LACP port Ethernet102/1/5(0x1f650100) of port-cha

nnel port-channel305(0x16000130) not receiving any LACP BPDUs  suspending (individual) port

2011 Oct 26 11:04:18 NJDC-B-17-N5K-3 %LACP-FEX102-5-LACP_SUSPEND_INDIVIDUAL: LACP port Ethernet102/1/5(0x1f650100) of port-cha

nnel port-channel305(0x16000130) not receiving any LACP BPDUs  suspending (individual) port

2011 Oct 26 11:05:13 NJDC-B-17-N5K-3 %LACP-FEX102-5-LACP_SUSPEND_INDIVIDUAL: LACP port Ethernet102/1/6(0x1f650140) of port-cha

nnel port-channel306(0x16000131) not receiving any LACP BPDUs  suspending (individual) port

2011 Oct 26 11:07:06 NJDC-B-17-N5K-3 %LACP-FEX102-5-LACP_SUSPEND_INDIVIDUAL: LACP port Ethernet102/1/6(0x1f650140) of port-cha

nnel port-channel306(0x16000131) not receiving any LACP BPDUs  suspending (individual) port

 

************

 

Robert replied:

 

******************

 

Not trying to jump to conclusions, but I cannot recall any issue where VC was at fault for a failing LACP channel.  That is one thing it does very well.  One of the biggest mistakes made in the Nexus config is creating a single vPC with member ports connecting to more than one VC module.  A port channel or a vPC must terminate on a single VC module. 

 

For example, you can create a vPC on the Nexus with member ports from two different Nexus switches, but both of those ports in that vPC must connect to only one VC module. 

 

We also frequently see a single vPC with one or more connections from two different Nexus switches, connecting to two different VC modules.  This simply is not supported.

 

**************

 

Any help for Joe??