Thanks everyone for your help with this problem:
> I have a very simple network with about 5 linux servers, a cisco
> 3500XL switch and a 2600 router.
>
> There is a problem with servers that have very little or no traffic.
> The network interfaces on the low traffic servers seems to become
> no
Tauren Mills wrote:
> Phil,
>
> Thanks for the suggestion. However, changing the arp timeout to 300
> doesn't seem to have helped.
Hmm. Re-reading your email, it doesn't sound like that was the problem
anyway.
Can you supply more detail on the physical topo? Does the router hang
off the switc
On Mon, 4 Jun 2007, Tauren Mills wrote:
> Thanks for the suggestion. However, changing the arp timeout to 300
> doesn't seem to have helped.
Do you have multiple interfaces on the systems? If so, are they ARP'ing
out the proper interfaces? I've run into that issue on Linux boxes before.
--
Phil,
Thanks for the suggestion. However, changing the arp timeout to 300
doesn't seem to have helped.
Tauren
On 6/2/07, Phil Mayers <[EMAIL PROTECTED]> wrote:
> Tauren Mills wrote:
> > Hello,
> >
> > I have a very simple network with about 5 linux servers, a cisco
> > 3500XL switch and a 2600
Tauren Mills wrote:
> Hello,
>
> I have a very simple network with about 5 linux servers, a cisco
> 3500XL switch and a 2600 router.
>
> There is a problem with servers that have very little or no traffic.
> The network interfaces on the low traffic servers seems to become
> non-response after a
Hello,
I have a very simple network with about 5 linux servers, a cisco
3500XL switch and a 2600 router.
There is a problem with servers that have very little or no traffic.
The network interfaces on the low traffic servers seems to become
non-response after a very short period of time (as low at
