- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Has anyone experienced issues with loosing LACP co...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2011 07:29 AM
10-28-2011 07:29 AM
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2014 11:54 AM
05-13-2014 11:54 AM
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?
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