- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- 1800-24G losing trunks
Switches, Hubs, and Modems
1752687
Members
5486
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
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
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
04-07-2009 03:42 AM
04-07-2009 03:42 AM
1800-24G losing trunks
We use 1800-24G switches (f/w v3.00) for the front end iSCSI fabric on our SAN. These generally work fine, and have been in place for over a year now.
I've configured standard LACP trunks between the two core switches on ports 21/22, and the LACP status always shows ok. The problem is that, on two occasions now, the trunks have failed, and when they fail, they fail 'open' and create a network loop, effectively killing the front end to our SAN. Manually disconnecting one of the links sorts things out, but it's very, very concerning.
We operate many LACP trunks on 1800's and other 5300/2600 switches with no problems, so I don't know what's happening on these. Nothing has changed on the config, and they'll work for months as expected.
I originally set the port keys to 'auto', but after the previous occasion, manually assigned them. Obviously, this didn't help when it happened again yesterday! All trunked ports have flow control enabled, and are set to auto-neg speeds.
With so little to configure on the 1800's, much of the setup is handled automatically, so I'm wondering if this might be a bug in the firmware?
I've configured standard LACP trunks between the two core switches on ports 21/22, and the LACP status always shows ok. The problem is that, on two occasions now, the trunks have failed, and when they fail, they fail 'open' and create a network loop, effectively killing the front end to our SAN. Manually disconnecting one of the links sorts things out, but it's very, very concerning.
We operate many LACP trunks on 1800's and other 5300/2600 switches with no problems, so I don't know what's happening on these. Nothing has changed on the config, and they'll work for months as expected.
I originally set the port keys to 'auto', but after the previous occasion, manually assigned them. Obviously, this didn't help when it happened again yesterday! All trunked ports have flow control enabled, and are set to auto-neg speeds.
With so little to configure on the 1800's, much of the setup is handled automatically, so I'm wondering if this might be a bug in the firmware?
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