- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Comware Based
- >
- The ARP packet rate(89pps) exceeded the rate limit...
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
Forums
Discussions
Discussions
Forums
Discussions
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
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
11-04-2015 02:53 AM
11-04-2015 02:53 AM
Re: The ARP packet rate(89pps) exceeded the rate limit (50pps) on interface...
I came across this problem couple of weeks ago, my loggs were flooded with ARP packet rate messages and also had a high CPU load. Turned out to be due to Tc flooding and after going for RSTP in instead of PVST the problem went away. I now have the occasional message. This was in a mixed Cisco, HP enviroment.
Kjartan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2017 04:57 AM
04-18-2017 04:57 AM
Re: The ARP packet rate(89pps) exceeded the rate limit (50pps) on interface...
I saw ARP packet rate exceeding the default rate on all the link agg'ed interfaces as well as TCs and duplicate IP addresses logged yesterday where the core switch side of a 20G linkagg had one of the members taken out of the link aggregation group to an IDF by a consultant.
Simply adding
port link-aggregation group 5
back into the interface configuration got everything OK again.
- « Previous
-
- 1
- 2
- Next »