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.