HPE GreenLake Administration
- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Problem with ProCurve 2650 and ip source-lockdown
Switches, Hubs, and Modems
1834254
Members
2177
Online
110066
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
Forums
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
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
03-12-2010 08:01 AM
03-12-2010 08:01 AM
Problem with ProCurve 2650 and ip source-lockdown
Hello,
We have to identical ProCurve 2650 switches, both with the last firmware and identical configuration.
Since a few days, we have terrible performance and huge packet drops (Drops Rx) whenever "ip source-lockdown" is activated on one switch (let's call it switch1; the other one (switch2) works perfectly well):
When transferring 100MB-file:
- between two computers connected to switch2, we have ~12MB/s (independent of the status of "source-lockdown") and no packet drops.
- between two computers connected to switch1, when source-lockdown is deactivated on BOTH ports, we have ~12MB/s and no packet drops
- between two computers connected to switch1, when the data LEAVES the switch at a port with "source-lockdown", we have ~10MB/s, and a few packet Drops in the other direction
- between two computers connected to switch1, when the data ENTERS the switch at a port with "source-lockdown", we have ~1.2MB/s, and ~20% of the packets appear as "Drop RX"
- between two computers connected to switch1, when source-lockdown is activated on both ports, we have ~0.7MB/s, and packet drops at both interfaces.
So: as soon as we activate source-lockdown on the problematic switch1, the network performance breaks down completely. When source-lockdown is deactivated, we have again good performance.
We already tried to restart all switches at the same time - this did not change anything.
Any good ideas what we could try?
Thanks,
Axel
We have to identical ProCurve 2650 switches, both with the last firmware and identical configuration.
Since a few days, we have terrible performance and huge packet drops (Drops Rx) whenever "ip source-lockdown" is activated on one switch (let's call it switch1; the other one (switch2) works perfectly well):
When transferring 100MB-file:
- between two computers connected to switch2, we have ~12MB/s (independent of the status of "source-lockdown") and no packet drops.
- between two computers connected to switch1, when source-lockdown is deactivated on BOTH ports, we have ~12MB/s and no packet drops
- between two computers connected to switch1, when the data LEAVES the switch at a port with "source-lockdown", we have ~10MB/s, and a few packet Drops in the other direction
- between two computers connected to switch1, when the data ENTERS the switch at a port with "source-lockdown", we have ~1.2MB/s, and ~20% of the packets appear as "Drop RX"
- between two computers connected to switch1, when source-lockdown is activated on both ports, we have ~0.7MB/s, and packet drops at both interfaces.
So: as soon as we activate source-lockdown on the problematic switch1, the network performance breaks down completely. When source-lockdown is deactivated, we have again good performance.
We already tried to restart all switches at the same time - this did not change anything.
Any good ideas what we could try?
Thanks,
Axel
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP