I did notice that the ISDN lights were all behaving normally (i.e. the one
which is actually connected to an ISDN line was steady on and the rest
were flashing quickly, which isn't what the manual says should happen, but
is anyway...)
Also, the ethernet lights were behaving normally (green on, red flashing
almost continually).
The only thing I received via syslog were a series of "spurious
interrupts" errors just before it stopped responding.
I am assuming that the cause of the crash was that one of our technicians
moved some modems from this server to another at around that time. He
didn't notice any problems, but the "spurious interrupts" happened about
the time he did this, and they were on some (but not all) of the ports
which he was working on.
So, I have several questions.
1) Is it considered bad practice to unplug or plug in serial cables
(attached to turned-off modems) while the PM is on? We have always done
this, but if it is going to crash the terminal server... I'd rather not
shut down the whole server just to swap out a modem, though.
2) Is there any other information I can get to help me understand this
crash? The PM doesn't seem to hold on to anything after being rebooted,
and there wasn't anything in my syslog files other than the spurious
interrupts. I am not running SNMP. Could that have allowed me to collect
more information or is it only useful for normal operation?
Thanks.
Kevin
------------------------------------------------------------------------------
Kevin Fink <kevin@fink.com> N2H2, Creators of Bess
http://www.fink.com/ 1301 Fifth Avenue, Suite 1501
http://www.n2h2.com/ Seattle, WA 98101
------------------------------------------------------------------------------
(206) 971-1451 VOICE (206) 971-1460 FAX (206) 680-7666 PAGER
------------------------------------------------------------------------------