home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.sys.cisco
- Path: sparky!uunet!cis.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!agate!boulder!recnews
- From: Jim Forster <forster@cisco.com>
- Subject: Re: ARP Cache Timeout Value
- In-Reply-To: Your message of "12 Dec 92 00:51:55 GMT."
- <1992Dec12.005155.24951@netcom.com>
- Message-ID: <724492536.14868@news.Colorado.EDU>
- Sender: news
- Date: 15 Dec 92 21:24:33 PST
- Approved: news
- X-Note1: mail msgid was <9212160524.AA19106@wolf.cisco.com>
- X-Note2: message-id generated by recnews
- Lines: 23
-
- > Our ciscos are set to the factory default of 4 hours for the ARP cache
- > time-to-live value. Why is it set so high and is there any reason I
- > shouldn't set it to, say, 15 minutes? We make a lot of changes to our
- > nets and it seems that a lot of bad data sits around for an awful long
- > time when it is set to 4 hours, no?
-
- The reason the default is set to 4 hours is simply that's what seemed like
- a reasonable value when the ARP code was written (5 or 6 years ago). Some
- tens of thousands of routers later, after very few questions about that
- default value, it still seems reasonable for a default. I don't see any
- problem with lowering your timeout to 15 minutes.
-
- If your hosts were conformant to the Host Requirements (RFC-1123), you
- could change them at will, and not worry about the ARP timeout at all,
- because RFC-1123 calls for hosts to send a 'gratuitous' Broadcast ARP reply
- upon startup. That way if they've had their MAC address change since their
- last presence on the net, cached values will be updated. Our routers do
- this when we startup and when we change our interface MAC addresses (e.g.,
- when DECNet is configured).
-
- -- Jim
-
-
-