From owner-freebsd-net Wed Sep 22 15:59:44 1999 Delivered-To: freebsd-net@freebsd.org Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (Postfix) with SMTP id DDB5A14F80 for ; Wed, 22 Sep 1999 15:59:33 -0700 (PDT) (envelope-from vev@michvhf.com) Received: (qmail 18385 invoked by uid 1001); 22 Sep 1999 22:59:37 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 22 Sep 1999 18:59:37 -0400 (EDT) X-Face: *0^4Iw) To: Mike Wade Subject: Re: 3.2 and 3com Cc: freebsd-net@FreeBSD.ORG Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 21-Sep-99 Mike Wade wrote: > 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. Looks like you got it. The router was showing that it hadn't heard from any of the machines in more than 15 minutes (or something to that nature) and the switch decided that it needed to try sending any traffic for the subnets involved to the 'Network Uplink Port'. Disabling this (since it was no longer in use) fixed the problem. It's been up for more than 16 hours now. Thanks!! Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message