- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: “loop-detected" trap on procurve
Switches, Hubs, and Modems
1748051
Members
5149
Online
108758
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
10-08-2008 12:48 PM
10-08-2008 12:48 PM
“loop-detected" trap on procurve
Hi
When enabling the loop-protection functionality on procurve switches, apparently a "loop-detected" trap is being sent when a port is shut down.
Do anyone have any info. about this trap? What snmp oid does it have? What MIB is it defined in?
Best regards,
Frank W. Mortensen
Managon
When enabling the loop-protection functionality on procurve switches, apparently a "loop-detected" trap is being sent when a port is shut down.
Do anyone have any info. about this trap? What snmp oid does it have? What MIB is it defined in?
Best regards,
Frank W. Mortensen
Managon
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2008 05:39 AM
11-27-2008 05:39 AM
Re: “loop-detected" trap on procurve
Hi
Did you figure this one out? I could use the information also.
Did you figure this one out? I could use the information also.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2009 12:42 AM
09-15-2009 12:42 AM
Re: “loop-detected" trap on procurve
Hm
I am back to this problem again, at another customer's site. They have triggered such a trap on a ProCurve 4900 switch. The trap oid in this case is 1.3.6.1.4.1.11.2.3.7.11.45.0.2.
But this oid seems to be specific for the ProCure 4900. Meaning that there might be a unique trap id for each of the ProCurve device models that will send such a trap..
Could anyone please confirm or refute?
Frank
I am back to this problem again, at another customer's site. They have triggered such a trap on a ProCurve 4900 switch. The trap oid in this case is 1.3.6.1.4.1.11.2.3.7.11.45.0.2.
But this oid seems to be specific for the ProCure 4900. Meaning that there might be a unique trap id for each of the ProCurve device models that will send such a trap..
Could anyone please confirm or refute?
Frank
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2010 08:08 AM
08-29-2010 08:08 AM
Re: “loop-detected" trap on procurve
Hey,
I was using procurve manager successfully to alert myself via email when the loop-detect trap was trigged. It worked real well until my pcm server crashed and when I rebuilt it I could not remember (successfully) how to make it alert again. If anyone could help with this I would be obliged.
I was using procurve manager successfully to alert myself via email when the loop-detect trap was trigged. It worked real well until my pcm server crashed and when I rebuilt it I could not remember (successfully) how to make it alert again. If anyone could help with this I would be obliged.
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