- To: outages-list@eskimo.com, radcom@eskimo.com, aeai@eskimo.com, mirader@eskimo.com, dnet@eskimo.com, dmadance@eskimo.com
- Subject: Seattle4 Communication Server Failed
- From: Robert Dinse <nanook@eskimo.com>
- Date: Mon, 20 Mar 2000 16:08:57 -0800 (PST)
- Newsgroups: lobby, announcements
- Resent-Date: Mon, 20 Mar 2000 16:09:15 -0800
- Resent-From: outages-list@eskimo.com
- Resent-Message-ID: <"RAk9Z3.0.HY5.eshru"@mx1>
- Resent-Sender: outages-list-request@eskimo.com
- Prev by Date: Seattle, WA Busy Signals and Vancouver BC Data Issues
- Next by Date: Eskinews INND crash
- Prev by thread: Eskinews INND crash
- Next by thread: Seattle, WA Busy Signals and Vancouver BC Data Issues
- Index(es):
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Seattle4 Communication Server Failed
We lost a Xylogics Annex-3 64 port communications server today that took
out a number of dedicated PPP lines as well as regular dial-up lines.
The server failed hard, I determined it wasn't any of the peripheral cards
that can be changed, something bad with the motherboard, so we had to replace
the entire unit.
Because of the amount of cabling and software configuration involved, this
process took about four hours. We are still in the process of setting the
modem types so that the modems will get the proper re-initialization when a
call terminates but all of the dedicated should now be back in operation.