- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Comware Based
- >
- Loop protection
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
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
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
тАО08-07-2017 10:47 AM
тАО08-07-2017 10:47 AM
Loop protection
Hi,
i have an entire L2 network based on HP/HPE switches (most of them are comware based). I never needed to enable STP because i preferred use of LAGs between access switches and core. I faced a noisy issue last days when someone (worker or cleaner) plugged the same patch into 2 wall plates. This caused a flood storm toward core switches and i had to isolate a floor before to detect this issue. I'm wondering if there's a way to automatically prevent this kind of incident (bpdu guard or other kind of loop protection). Thanks a lot!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2017 01:04 AM
тАО08-08-2017 01:04 AM
Re: Loop protection
Hello
To prevent loops from being created at the edge of your network.
Perform the below on the switch:
1. system-view
2. loopback-detection enable
3. loopback-detection multi-port-mode enable
4. interface interface-type interface-number
5. loopback-detection enable
6. loopback-detection control enable
7. loopback-detection per-vlan enable
8. loopback-detection action { no-learning | semi-block |
shutdown } Optional.
By default, a looped interface drops the incoming packets and correctly sends packets; the system generates traps and log messages, and deletes all MAC address entries of the looped interface. With the shutdown keyword specified, the switch shuts down the looped ports and set their physical state to Loop down. When a looped port recovers, you must use the undo shutdown command to restore its forwarding capability.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2017 01:26 AM
тАО08-08-2017 01:26 AM
Re: Loop protection
Hello,
thanks for your reply. Do you suggest to enable only for access ports? For uplink trunks i'd like to avoid because they're in LACP toward core switches.
Thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2017 01:42 AM
тАО08-08-2017 01:42 AM
Re: Loop protection
Yes, Only enabling loopdetection on access ports is enough. I don't like it either that it disables my uplink ports.
Kind regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2017 02:50 AM
тАО08-08-2017 02:50 AM
Re: Loop protection
1. system-view
2. loopback-detection enable
3. loopback-detection multi-port-mode enable
these commands enable as system global? they affect on uplinks too or not?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2017 02:55 AM
тАО08-08-2017 02:55 AM
Re: Loop protection
You need to configure it globally first to enable it.
If you don't configure loopdetection on port level for your uplinks you will be fine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2017 02:57 AM
тАО08-08-2017 02:57 AM
Re: Loop protection
Great! Thanks again
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2017 04:33 AM - edited тАО08-08-2017 04:38 AM
тАО08-08-2017 04:33 AM - edited тАО08-08-2017 04:38 AM
Re: Loop protection
See the mmr_sf-EN_US000005234 HPE Knowledge Article (title: HPE Networking Switches - How to Guard Against Edge Loops), just as a reference.
The @Anonymous statement "I never needed to enable STP because i preferred use of LAGs between access switches and core" is a little bit unclear: enabling STP (or RSTP) feature on network swithces is not mutually exclusive (like saying either (R)STP or LAGs) with the presence of LAGs between Core and Edge switches...
I'm not an HPE Employee