------------------------------------
ACCESS SERVER "DIALUP-1" (CONTINUED)
------------------------------------
In System News on December 24 I described a problem that was causing one
of our access servers to reboot spontaneously.  Today (December 26) I have
been working with the Technical Assistance Center (TAC) at Cisco Systems
trying to find a solution.  In order to complete the diagnosis of the
problem, TAC needs a "core dump" from the faulty access server. 

The core dump needs to occur under the same conditions that caused the
original problem, so we need to bring dialup-1 back on line and allow it
to accept calls.  Then we wait for it to crash.  When it crashes it will
"dump core" to a "core file" on our UNIX host.  That file will then be
sent to Cisco TAC for analysis. 

If all the technobabble is meaningless to you, ignore it.  What you really
need to be aware of is the fact that when dialup-1 crashes, it will
disconnect all of the 46 callers who are connected to it at the time.  We
know this will cause some inconvenience and unhappiness, but there is no
other way to provide the data Cisco TAC needs.  If you get disconnected,
please call right back.  Your call will be taken by one of the other
access servers. 

Once the core dump is done, dialup-1 will be taken off line again.  This
will leave us with a reduced modem pool (276 lines instead of 322) until
at least Monday, but possibly longer.

-------------------------------------------------------------------
All System News is archived at  http://www.bcpl.lib.md.us/sysnews.html
(or enter "sysnews" at the UNIX shell prompt)

If you have questions about this message or about anything else related
to your BCPL Internet Account, please contact the BCPL Help Desk. 

 Phone:   410-887-3297
 FAX:     410-887-2091
 E-Mail:  help@mail.bcpl.lib.md.us

Visit our Help pages at:  http://www.bcpl.lib.md.us/help.html
(or enter "help" at the UNIX shell prompt)