- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Comware Based
- >
- Re: Best Practices for loopback-detection configur...
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
05-15-2013 09:41 AM
05-15-2013 09:41 AM
Best Practices for loopback-detection configuration?
Has anyone deployed loopback-detection acrossed their LAN? For my access ports I was going to go with this:
interface GigabitEthernet1/0/1
port link-mode bridge
loopback-detection enable
loopback-detection action shutdown
For my trunk links I was thinking of going this route:
interface GigabitEthernet1/0/48
port link-mode bridge
port link-type trunk
port trunk permit vlan 1
loopback-detection enable
loopback-detection control enable
loopback-detection action semi-block
With this deployment the access ports with shutdown when a loop is detected (this will send a trap). If the trunk sees a loop condition it will go into the "semi-block" mode which still sends traps and bpdu's, but I am not sure what this would look like over a large deployment. Does anyone have any insight?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2013 05:57 AM
05-16-2013 05:57 AM
Re: Best Practices for loopback-detection configuration?
Wow, nobody?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2014 09:13 AM
05-05-2014 09:13 AM
Re: Best Practices for loopback-detection configuration?
Hi
I'm working on the same.
you finished making your implementation?
you can help me?
regards
Atte.
Francisco
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2014 11:41 AM
05-05-2014 11:41 AM
Re: Best Practices for loopback-detection configuration?
I wish I could say I had an answer for you. I have come up with nothing I feel comfortable with trying to deploy and I don't feel like forging this path on an environment of the size I am in.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-06-2014 04:53 AM
06-06-2014 04:53 AM
Re: Best Practices for loopback-detection configuration?
This doc has some info on loopback detection but I guess you have already read it?
A previous example I have seen (I dont use loopback detection myself, yet) is:
Globally:
loopback-detection enable
loopback-detection multi-port-mode enable
loopback-detection interval-time 5
Per interface:
loopback-detection enable
loopback-detection control enable
loopback-detection per-vlan enable
loopback-detection action shutdown
A drawback of "action shutdown" is that you need to manually login to the device and enable the interface again, I guess this is what "semi-block" is supposed to take care of.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2015 11:11 PM
08-25-2015 11:11 PM
Re: Best Practices for loopback-detection configuration?
Link is broken.
Why on god's earth did HP have to change their site and break 1000s of links to important information?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2015 11:40 PM
08-25-2015 11:40 PM
Re: Best Practices for loopback-detection configuration?
Yeah I dont get that either, my bets are on bad management who makes stupid decisions...
In this case you can change hp.com into hpe.com to get networkingrelated links to work again.
That is:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2015 02:08 AM
08-27-2015 02:08 AM
Re: Best Practices for loopback-detection configuration?
Hi All,
Do you know what exact means command : "loopback-detection per-vlan enable"
How it works on the trunk (e.g. all vlans allowed) without this "extra" entry?
Br,
Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2015 09:02 PM - edited 08-28-2015 09:05 PM
08-28-2015 09:02 PM - edited 08-28-2015 09:05 PM
Re: Best practices for loopback-detection configuration?
>Why on god's earth did HP have to change their site and break 1000s of links
Due to the company split, HP Inc got the hp.com domain name and HPE moved to hpe.com.
If you have not disabled the HP vs HPE popup, clicking on "HP Support Center - Hewlett Packard Enterprise" will show you the right webpage.