- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Comware Based
- >
- 802.3AD/LACP Issue
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
09-27-2012 07:40 AM - edited 09-27-2012 07:41 AM
09-27-2012 07:40 AM - edited 09-27-2012 07:41 AM
802.3AD/LACP Issue
I've got this weird issue with Link-Agg right now and I'm seriously confounded by it. I have Link-Agg setup for two HP StoreOnce (D2D 2504i) devices. One device sits at site A and another at site B.
Little background:
Site A has 4 HP A5800-48Gs. The 48Gs are configured in a single IRF domain with forward and backward redundancy (read daisy chained). Site B has 2 HP A5800-24Gs. the 24Gs are configured in a single IRF domain with forward redundancy (read a single link between the switches). The StoreOnce device has a port on alternating switches.
In site a the LAG is working optimally. Everything is up and going and testing so far has yeilded good behaviors. My problem is in site B. The StoreOnce device only works when one member of the LAG is administratively down. If you bring up both ports of the LAG, I am unable to ping it from any other host on the network. Interesting part: The switch can ping the StoreOnce device when both of the LAG links are up.
Here is an example of the config (both sites are configured identically with exception to the design of the cores):
interface Bridge-Aggregation1
description Uplink for HP D2D Device
port access vlan 7
interface GigabitEthernet1/0/11
port link-mode bridge
description HPD2D Port 1
port access vlan 7
port link-aggregation group 1
interface GigabitEthernet2/0/11
port link-mode bridge
description HPD2D Port 2
port access vlan 7
port link-aggregation group 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2012 04:31 AM
09-30-2012 04:31 AM
Re: 802.3AD/LACP Issue
Could you please attach your (full) config in txt on both switch stacks? It would make it easier to look for the cause, I can't determine much from the excerpts posted here.
Justin
Working @ HPE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2012 06:26 AM
10-02-2012 06:26 AM
Re: 802.3AD/LACP Issue
Concerning your config LACP is not active. Hit the following command into the switch when both links are connected and post it here:
disp link-aggregation verbose br 1
br
Manuel