Date: Fri, 5 Jan 1996 11:34:37 -0600 (CST) From: Joe Greco <jgreco@brasil.moneng.mei.com> To: hackers@freebsd.org Subject: Machine "disappears" off the net..? Message-ID: <199601051734.LAA02253@brasil.moneng.mei.com>
next in thread | raw e-mail | index | archive | help
I'm seeing an odd problem on news.sol.net (DX4/100 ASUS SP3G, 48MB, NCR810,
AHA-3940, SMC8216 incorrectly identified as SMC8416), that just started
happening recently, and has suddenly been very bad this morning.
At first I was fairly sure it was a hardware problem, but then I wasn't so
sure, as I increased the network load on the machine and these problems
started to appear, and then yesterday increased the network load again and
the problems got worse. And there is something else strange (see below).
The machine appears to "drop off" the network for indefinite (1min-1hr)
periods of time. Symptoms are consistent with a marginal Ethernet cable
at first glance:
hummin# netstat -I ed0 (*news.sol.net*)
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
ed0 1500 <Link>00.00.c0.1e.84.75 7080742 0 5956928 4503 64262
Note in particular the output error rate and relatively high collision count
(as compared to the router, below, which has been up 90++ days):
trantor# netstat -I ed4 (*router*)
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
ed4 1500 <Link>00.40.c7.20.d5.c1 71246705 2522 86820038 0 71608
It looks somewhat odd to me, because I usually see both ierrs and oerrs on
segments with bad cables, yet I only seem to be seeing it in "one"
direction. Could be a bad card, probably the tx on hummin...
But I then noticed that trantor continues to receive rwho broadcasts from
hummin during these periods of deadness, even though I am not able to ping
hummin from either trantor or another host on that wire. And hummin isn't
showing any signs of input errors.
Syslog messages: none.
Level of head scratching: severe.
I have not had the good fortune to catch this happening while I am down at
the office, so I can't say what hummin is/isn't seeing during these
periods.
My most recent thinking is that there may be some sort of resource shortage,
so I looked at netstat -m, but I don't see anything obviously wrong:
hummin# netstat -m
184 mbufs in use:
84 mbufs allocated to data
26 mbufs allocated to packet headers
68 mbufs allocated to protocol control blocks
6 mbufs allocated to socket names and addresses
72/232 mbuf clusters in use
487 Kbytes allocated to network (34% in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines
Does anyone have any ideas, theories, or suggestions? Obviously the
networking hardware is already slated for replacement, but I'm not
confident that that's the problem here.
... Joe
-------------------------------------------------------------------------------
Joe Greco - Systems Administrator jgreco@ns.sol.net
Solaria Public Access UNIX - Milwaukee, WI 414/342-4847
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601051734.LAA02253>