- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- LACP issues with Virtual Connect v3.18
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
11-17-2011 10:29 AM
11-17-2011 10:29 AM
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??