HPE GreenLake Administration
- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- router mac address caching
Switches, Hubs, and Modems
1827295
Members
2182
Online
109717
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
Go to solution
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
06-29-2005 04:22 AM
06-29-2005 04:22 AM
Hi all,
I have got a router which caches mac address.
So if I change LAN card IP adress I'm not able to reach it using this router for some time.
They told me that this was done to improove router performances.
I don't like this router configuration so I'm looking for any acceptable solution.
-Do you know if it is possible to disable caching only for some specified mac address?
-How mutch do you think performance are impacted disabling mac address caching?
-Do you have any other idea?
Thank You
I have got a router which caches mac address.
So if I change LAN card IP adress I'm not able to reach it using this router for some time.
They told me that this was done to improove router performances.
I don't like this router configuration so I'm looking for any acceptable solution.
-Do you know if it is possible to disable caching only for some specified mac address?
-How mutch do you think performance are impacted disabling mac address caching?
-Do you have any other idea?
Thank You
Ubi maior, minor cessat!
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2005 08:25 PM
06-29-2005 08:25 PM
Solution
Hi,
you are talking about the ARP cache. Every router (and every IP talking device) has one, and it is indeed done for performance reasons (asking for an ARP resolution prior to every packet is pointless).
The problem is that some vendors have silly defaults for the ARP cache timeout. Notabliy Cisco has a default of 4 *hours* which gives all sorts of grief like you describe.
Good platforms allow to reduce the ARP cache timeout to something reasonable, like IMO 5 minutes (300s). On a Cisco, you would do
int e0
arp timeout 300
On a HP ProCurve, the current default timeout seems to be 20 minutes. That's still a bit large but good to prevent high broadcast rates in overwhelmingly large broadcast domains, I usually reduce it to 300s as well, you can do this either in the menu or in the CLI using
ip arp-age 5
BTW, one reason for setting the ARP cache timeout to not larger a value than the MAC table timeout (which in any sane bridge is 300s) is that it will prevent unidirectional unicast flows from becoming a flood to unknown destination MACs. Before it would come to that, the destination must be ARPed for, forcing it to give an ARP reply, and that one can prime the MAC tables again.
HTH,
Andre.
you are talking about the ARP cache. Every router (and every IP talking device) has one, and it is indeed done for performance reasons (asking for an ARP resolution prior to every packet is pointless).
The problem is that some vendors have silly defaults for the ARP cache timeout. Notabliy Cisco has a default of 4 *hours* which gives all sorts of grief like you describe.
Good platforms allow to reduce the ARP cache timeout to something reasonable, like IMO 5 minutes (300s). On a Cisco, you would do
int e0
arp timeout 300
On a HP ProCurve, the current default timeout seems to be 20 minutes. That's still a bit large but good to prevent high broadcast rates in overwhelmingly large broadcast domains, I usually reduce it to 300s as well, you can do this either in the menu or in the CLI using
ip arp-age 5
BTW, one reason for setting the ARP cache timeout to not larger a value than the MAC table timeout (which in any sane bridge is 300s) is that it will prevent unidirectional unicast flows from becoming a flood to unknown destination MACs. Before it would come to that, the destination must be ARPed for, forcing it to give an ARP reply, and that one can prime the MAC tables again.
HTH,
Andre.
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP