Date: Tue, 21 Sep 1999 19:17:24 -0400 (EDT) From: Mike Wade <mwade@cdc.net> To: Vince Vielhaber <vev@michvhf.com> Cc: freebsd-net@FreeBSD.ORG Subject: Re: 3.2 and 3com Message-ID: <Pine.GSO.4.10.9909211915000.4043-100000@server1> In-Reply-To: <XFMail.990920193031.vev@michvhf.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 20 Sep 1999, Vince Vielhaber wrote: > I have an odd one going on. In the last couple of weeks we installed 3.2 > (from the CDs) on 7 machines. 5 were new pIII-450's ASUS MB with 3C905 > PCI network cards, two are older Pentium 150's with 3C509B's - ISA, all > with 128MB ram. All power management stuff is turned off in BIOS. These > machines, if left alone with no traffic, will seem to drop off the network. > No ping, no telnet, no ssh. If you walk up to the console you can log in > and ping anywhere you want and suddenly you can get in from outside again. > It's like it was woke up. It also wakes up if a cronjob sends mail. Right > now I have open pings running to a couple of the machines to keep them > awake. The only things these machines seem to have in common are: 10base-t, > FreeBSD 3.2-RELEASE, 128MB Ram and a Cisco Catalyst 1900 switch. > > Anyone seen this before or have any ideas? I had a similar problem with a 3Com ethernet switch. The solution was to up the MAC address expire time so the switch didn't drop the MAC making it unavailable to the network until the machine generated traffic. --- Mike Wade (mwade@cdc.net) Director of Systems Administration CDC Internet, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.9909211915000.4043-100000>