- Community Home
- >
- Networking
- >
- IMC
- >
- Loop Protection issue/question
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
01-19-2012 07:30 AM
01-19-2012 07:30 AM
Loop Protection issue/question
Hello,
We would like to implement Loop Protection on our HP switches on our LAN.
We started by testing with a 2510G-24 with a basic configuration:
======
; J9279A Configuration Editor; Created on release #Y.11.35
hostname "ProCurve Switch 2510G-24"
ip default-gateway 172.18.46.11
snmp-server community "public" Unrestricted
snmp-server host 172.18.46.33 "public" All
vlan 1
name "DEFAULT_VLAN"
untagged 1-24
ip address 172.18.46.209 255.255.255.0
exit
loop-protect 1-24
loop-protect trap loop-detected
loop-protect disable-timer 15
======
We connected a dumb switch to one of the 2510 ports, then caused a loop on the dumb switch. The 2510 immediately sensed the loop and disabled the port. It would re-enable the port after 15 seconds and immediately disable the port again when it detected the loop was still there. When we took out the loop, the port was re-enabled and stayed that way. It worked exactly as expected.
We then connected another of the 2510 ports to our production LAN via a simple daisy-chain. None of the other switches in the LAN have Loop Protect turned on. With that connection in place, the Loop Protect no longer worked. The test 2510 logs a "high broadcast" rate for the port with the looped-dumb-switch, but no longer detects the loop. If we disconnect the cable to the production LAN, the Loop Protect works properly again.
What could cause the Loop Protect to fail when we are connected to our Production LAN? Is there some protocol that could be overriding/suppressing Loop Protect on our test 2510 switch?
Thanks for any insight that you can provide on this issue.
Bryan Hunt
- Tags:
- loop protection