- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: ARP Table refresh in 4000m and 2524
Switches, Hubs, and Modems
1752815
Members
5899
Online
108789
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
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
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
тАО09-07-2005 06:13 AM
тАО09-07-2005 06:13 AM
Hi.
I would like to know what is the refresh time on procurve 4000m and procuve 2524 for the ARP table. We have a weird probleme with our cluster server and we suspect the switch... but not sure.
TX
Marc
I would like to know what is the refresh time on procurve 4000m and procuve 2524 for the ARP table. We have a weird probleme with our cluster server and we suspect the switch... but not sure.
TX
Marc
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-11-2005 12:49 PM
тАО09-11-2005 12:49 PM
Solution
Could you provide more details? These are layer 2 switches and should only use their ARP tables for personal use (switch management, etc.) If you are looking for an ARP cache problem between two other nodes whose traffic is passing through the switch, this should not relate to the switch's ARP table but to a problem with one of the nodes. Hope this helps.
Jim
Jim
Building better networks since 1981
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2005 01:25 AM
тАО09-13-2005 01:25 AM
Re: ARP Table refresh in 4000m and 2524
Ah great. Tx for the answer. This is what I was looking for! I was sure of this answer, but I was seeking someone to confim this. It must be the server, after a patch, who doing the problem. I know that the switch at this layer(not a routing switch) not doing anyting with arp with other devices, but my consultant was not sure.
Since I have post this question. My net admin look farther more and found a patch for tcpip. We think we resovle the problem but not sure.
Tx again.
Marc
Since I have post this question. My net admin look farther more and found a patch for tcpip. We think we resovle the problem but not sure.
Tx again.
Marc
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2005 01:38 AM
тАО09-13-2005 01:38 AM
Re: ARP Table refresh in 4000m and 2524
While Jim may have been right in this case, I still take exception to his statement. Layer 2 switches DO rely on ARP (MAC) tables to "route" through the fabric. That is the only way they know what path to take. Every port in the fabric holds the MAC of devices on that port and the switches periodically refresh these tables. IIRC the schedule is somewhere around 15 minutes.
I once had a badly behaving switch that was misrepresenting a MAC address and it kept subverting the route through the fabric. The short term workaround was to continually ping the address so as to lessen the effect of the bogus table until I could schedule the downtime to change out the switch.
I once had a badly behaving switch that was misrepresenting a MAC address and it kept subverting the route through the fabric. The short term workaround was to continually ping the address so as to lessen the effect of the bogus table until I could schedule the downtime to change out the switch.
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