BladeSystem Virtual Connect
cancel
Showing results for 
Search instead for 
Did you mean: 

Has anyone experienced issues with loosing LACP connectivity.

 
chuckk281
Trusted Contributor

Has anyone experienced issues with loosing LACP connectivity.

Joe has Cisco Nexus and Virtual Connect issue:

 

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

 

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

 

 

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

 

From Bob:

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.

 

From Greg:

If you have want an ACTIVE/ACTIVE config then create TWO vPCs within the Nexus Switches.  Uplinks from VC1 -> vPC1 and VC2 ->vPC2.  

 

Note - This is a requirement of LACP std.  It is not a fault of the VC or the Nexus products

 

From Dan:

 If you want more help, get the PortChannel and member port configs.

show run int po305
Etc

 

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

 

Any other comments or suggestions for Joe?

1 REPLY
technewbie
Occasional Visitor

Re: Has anyone experienced issues with loosing LACP connectivity.

I am having the same problem in order to configure Active/Active solution with our HP c7000.

 

"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".

 

According to HP documentation Diagram 3 page 11, it shows you can connect two different VC modules to one Nexus vPC with same vPC identification, in this case  vPC 11 and vPC 11 from two different modules. We have tried this solution, it does not work, all connection to Nexus 5k-1 are active and all connection to Nexus 5k-2 standby. When connected VC module to each switch, we get active/active but without vPC. Am I missing something?

 

 

http://h20566.www2.hp.com/portal/site/hpsc/template.BINARYPORTLET/public/kb/docDisplay/resource.process/?spf_p.tpst=kbDocDisplay_ws_BI&spf_p.rid_kbDocDisplay=docDisplayResURL&javax.portlet.begCacheTok=com.vignette.cachetoken&spf_p.rst_kbDocDisplay=wsrp-resourceState%3DdocId%253Demr_na-c02656171-3%257CdocLocale%253D&javax.portlet.endCacheTok=com.vignette.cachetoken

 

If connecting two different VC modules to single Nexus vPC is not supported, what other way to accomplish Active/Active in Nexus vPC?

 

 

Thanks

Technewbie