Author: admin

We uncovered a bug in our Cisco 7010’s…

Wed Apr 23 00:52:11 PDT 1997 — We uncovered a bug in our Cisco 7010’s operating system (oh, lucky us) that caused problems with our 45Mbps HSSI interface. (The HSSI input queue ‘wedged’ during a reboot.) We’ve upgraded the router’s operating system (IOS – ‘THE’ Internet Operating System, it’s the way the world works) to Cisco’s latest release, 11.0(14a)). -Dane and Scott

Our DS3 is back up.

Tue Apr 22 23:54:13 PDT 1997 — Our DS3 is back up. It turns out we’ve uncovered a bug in our Cisco 7010’s operating system (oh, lucky us). We’ve adjusted the router configuration so as not to trigger the bug, and rebooted. We’re currently getting our ducks in a row to reload with a new operating system. -Scott and Dane

Our DS3 is still down.

Tue Apr 22 22:22:46 PDT 1997 — Our DS3 is still down. It turns out we’ve uncovered a bug in our Cisco 7010’s operating system (oh, lucky us). We’re currently getting our ducks in a row to reload with a new operating system. Meanwhile, our backup DS1 with MCI is operating correctly (although it is very busy.) -Scott

One of our circuits to the Internet is…

Tue Apr 22 19:22:40 PDT 1997 — One of our circuits to the Internet is currently down. We are taking measures to get it back up as soon as possible. Users will notice slow performance, but should not notice an outage. We will update when we know more. -Dustin

AOL’s mail delivery troubles have gotten a…

Thu Apr 17 12:35:13 PDT 1997 — AOL’s mail delivery troubles have gotten a bit better – there are currently only 902 outstanding messages deferred due to load on their mail exchange servers. Compare to ~13,200 this time yesterday, and it looks like they made some fixes or changes. Delayed mail will eventually be delivered, but if you get complaints of slow delivery from users who you send to on AOL, please take it up with AOL, or tip them off on how nice Sonic is. 😉 -Dane

Our 547-2000 ISDN hunt group is back in…

Wed Apr 16 22:04:48 PDT 1997 — Our 547-2000 ISDN hunt group is back in operation. Apparently, at some point after 6pm, our equipment was unable to register SPIDs with PacBell’s ISDN switch. So, a port would be usable until a disconnect, at which point it would go into ‘NO-SERVICE’ state. Rebooting the ISDN router resulted in ‘NO-SERVICE’ on all ports, as well as ‘NT-1 attached, but telco isn’t there’ messages. We regained service just before 10pm. Priority Repair was unable to tell me what happened, so all I know is that a) we didn’t change anything, and b) when I rebooted the ISDN router (around 8pm), it had been up for 56 days. -Scott

PacBell is having problems with their ISDN…

Wed Apr 16 20:33:11 PDT 1997 — PacBell is having problems with their ISDN switch. Currently, no ISDN circuits in the 547-2000 hunt group are working. The ISDN ports at 522-1002 (the ‘X2’ hunt group) appear unaffected by PacBell’s outage. Members with individual ISDN accounts can establish single-B sessions on 522-1002. ‘Routed ISDN’ networks will not work with the 522-1002 number. I don’t have a time when PacBell expects to de-snafu their ISDN switch — I’ll post it here when I get it. -Scott

AOL seems to be having some rather massive…

Tue Apr 8 16:41:02 PDT 1997 — AOL seems to be having some rather massive problems with their mail servers, and most mail addressed to AOL customers has not been delivered today. Of 4223 attempted deliveries, about 10% were delivered, and the rest are still in our queue. This doesn’t mean that your mail won’t be delivered, it means that delivery is delayed. If this is a problem, please do take it up with the folks at AOL – they seem to be having quite a few troubles lately. -Dane

While we have got a new disk in to add to the

Mon Apr 7 14:13:38 PDT 1997 — While we have got a new disk in to add to the /home space, we’re not very happy with it’s performance. Specificly, it’s got such a high pitch whine that no one wants to work in the machine room with it running. It’s a 4.55 Gig Seagate Cheetah running at 10,000RPM, so I guess that’s to be expected. Meanwhile, /home is getting a bit full. Please do a ‘diskuse’, or ‘du’ in your home directory and do a bit of Spring cleaning. Thanks! -Dane

The new USR modems refuse calls from private…

Sat Mar 29 08:20:31 PST 1997 — The new USR modems refuse calls from private originators. That is, people who have caller ID blocking on. USR claims that this isn’t even a feature option, and they have no idea why it’s happening. If this happens to you, you’ll probably hear a single ring, then a fast busy tone. To work around it, dial *82,522-1002 to unblock your caller ID for that session. We’re working with USR on a solution. -Dane