- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- HPE Aruba Networking & ProVision-based
- >
- 5300xl switch not handling downstream loops
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
Forums
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
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-24-2010 01:30 PM
11-24-2010 01:30 PM
5300xl switch not handling downstream loops
Hello,
At one of our sites, we have a pair of 5308xl switches, linked by a pair of aggregrated 1Gb links, acting as the core.
Someone looped two ports on a directly connected 1810G switch. Result ? Port on 5308xl was blocked by spanning-tree, as expected. However, whole network across both core switches pretty much ground to a halt, until the blocked port was actually disabled (I have now put loop-detection on all ports).
Question, if the port was correctly blocked, and "broadcast-limit" was enabled on both 5308xls, then why did the network take such a hit ? My understanding of the global "broadcast-limit" command is that broadcast/multicast traffic limits individual port traffic to1000pkts/sec, so is it the case that the 5308xl is simply unable to process this load ?
Anyone else had a similar experience ?