- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- static lacp trunk and STP
Switches, Hubs, and Modems
1752770
Members
4830
Online
108789
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО05-01-2007 05:08 PM
тАО05-01-2007 05:08 PM
static lacp trunk and STP
I wasn't using stp until an unintended loop occured.
I have one DL320G5 that is connected to a 2900 (with address 192.168.0.2 in attachment) using a static lacp trunk comprised of 2 1GbE copper links. The hp utility shows that we're getting tx/rx on both links as well as successful lacp negotiation in the switch. Until I enabled spanning tree this worked fine for ~3-4 months.
Since I've enabled STP:
The LACP trunk to the DL320G5 will fail earlier than the rest of the switch. When this link fails, traffic still flows, for hours/(days?) even. Eventually, I won't be able to ping the address of the switch from a computer attached directly to the switch, but I will be able to talk to other devices on the network on different switches and beyond the router.
When I lose the ability to ping the switch, I also lose serial access. I note that the other 2900 becomes the CST Root (the first one happens to have a numerically lower mac). Eventually though, the only thing left to do is power cycle the switch.
I've dissolved the lacp trunk and am using TLB for the nic team now (which seems to work fine in the other 2900) in an effort to see if there are any differences.
Have I just not configured spanning-tree correctly or is there something else that I should look into?
Spanning tree in all switches is enabled with the spanning-tree command.
In addition, this behavior is exhibited on both 12.01 and 12.02 firmware.
Suggestions?
I have one DL320G5 that is connected to a 2900 (with address 192.168.0.2 in attachment) using a static lacp trunk comprised of 2 1GbE copper links. The hp utility shows that we're getting tx/rx on both links as well as successful lacp negotiation in the switch. Until I enabled spanning tree this worked fine for ~3-4 months.
Since I've enabled STP:
The LACP trunk to the DL320G5 will fail earlier than the rest of the switch. When this link fails, traffic still flows, for hours/(days?) even. Eventually, I won't be able to ping the address of the switch from a computer attached directly to the switch, but I will be able to talk to other devices on the network on different switches and beyond the router.
When I lose the ability to ping the switch, I also lose serial access. I note that the other 2900 becomes the CST Root (the first one happens to have a numerically lower mac). Eventually though, the only thing left to do is power cycle the switch.
I've dissolved the lacp trunk and am using TLB for the nic team now (which seems to work fine in the other 2900) in an effort to see if there are any differences.
Have I just not configured spanning-tree correctly or is there something else that I should look into?
Spanning tree in all switches is enabled with the spanning-tree command.
In addition, this behavior is exhibited on both 12.01 and 12.02 firmware.
Suggestions?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-03-2007 08:13 AM
тАО05-03-2007 08:13 AM
Re: static lacp trunk and STP
Nevermind -- the switch died -- hardware failure.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-03-2007 08:15 AM
тАО05-03-2007 08:15 AM
Re: static lacp trunk and STP
close thread
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP