Re: (PM) PM 2ER-30 locking up (fwd)

Phil Blancett (Phil@oakweb.com)
Thu, 29 Jan 1998 00:02:26 -0800

We have a 2ER-30 and it was locking up as well. We
took a look inside the fan and it was pretty gunked up
after a year and a half of sucking dust. We blew it out
and it stopped locking up. A little less technical reason
but you never know, it may be something simple like a
heat problem.

Phil Blancett
System Admin/Owner
California.Net

-----Original Message-----
From: MegaZone <megazone@livingston.com>
To: portmaster-users@livingston.com <portmaster-users@livingston.com>
Date: Wednesday, January 28, 1998 11:41 PM
Subject: (PM) PM 2ER-30 locking up (fwd)

>Once upon a time qcislands net gated newsgroup feed shaped the electrons to
say...
>>You can't telnet into it. Modems which may be live to it can't talk to it
>>as well. Nothing short of cycling power fixes it.
>
>Turn on syslog, and turn on all logging. What you are describing sounds
>like spurious interrupts keeping the CPU racing in circles. I've seen
>that a number of times over the years. And rebooting it can stop it
because
>it toggles DTR and can kick a crazy modem into line - at least for a
>while.
>
>You might also leave a terminal or printer on S0 with console set to S0
>to catch any panic messages it may be logging before it reboots.
>
>Also, do check the memory periodically. We have seen some evidence of
>a slow memory leak from other users. It seems to only be with ISDN when
>certain errors occur, but I'm not ready to rule it out. If you see
>memory usage growing over time until it is filling up, that could be it.
>
>Also keep an eye on nbufs. In light of a couple of recent reports I've
>been watching for more reports. If you see something where the used
>and available don't add up to the total - report it ASAP.
>
>>was up at 800 used, but after I ran a show sessions and then another show
>>mem it changed to only 51.
>
>Perhaps before the reboot? Nbuf usage can grow over time, but it should
>level out eventually.
>
>>Can some kind soul advise if I can crank up system logging from the PM to
>>my authenticator? My syslog gets nothing from the PM right now other than
>>a boot message. I wouldn't mind running it to the maximum logging to try
>>and find what the problem is..
>
>The manuals cover syslogging - I'd turn it all on.
>
>-MZ
>--
>Lucent Remote Access Division - Chair, Department of Interstitial Affairs
>Phone: 800-458-9966 510-737-2100 FAX: 510-737-2110 megazone@livingston.com
>For support requests: support@livingston.com <http://www.livingston.com/>
>Snail mail: 4464 Willow Road, Pleasanton, CA 94588
>-
>To unsubscribe, email 'majordomo@livingston.com' with
>'unsubscribe portmaster-users' in the body of the message.
>

-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.