Month: February 1999

Tue Feb 16 16:59:03 PST 1999 — We’ve modified the telnet issue file so that it warns users about the risk of using telnet versus SSH – we recommend users switch to SSH where possible. -Dane

Sat Feb 13 05:40:00 PST 1999 — Our database server, Timber, now sports a shiny-new RAID-5 disk subsystem. It has been online for over a day — so far, no problems. Thank you for your patience during this upgrade. -Scott

Sat Feb 13 17:30:08 PST 1999 — Sonic.net will be closed on Monday the 15th of February. Technical support is available on Saturday and Sunday from 9am to 9pm, and will reopen on Tuesday at 9am. Have a nice holiday weekend! -Dane

Thu Feb 11 20:14:05 PST 1999 — Our new RAID-5 disk system is ready for service in our mysql server (Timber). Since initialization would take far longer than we expected (12 hours!), we pulled the RAID out and initialized it in another computer. Starting at 1am tomorrow (Friday) morning, we’ll be moving databases on Timber to the new hardware RAID system, as well as performing miscellaneous maintenance on the system. Timber should be back in action by 5am. -Scott

Wed Feb 10 04:41:21 PST 1999 — Timber, the mysql server, is still down for maintenance as we move from software RAID to hardware RAID. The Mylex controller is currently initializing the RAID5 pack; I estimate it will complete prior to 6:30am. Sorry about the delay! -Scott

Tue Feb 9 09:54:58 PST 1999 — We’ve completed the emergency maintenance on the T3, and things are humming right along. Latency and packet loss are both back to normal levels, and we’re quite pleased. There was a configuration problem with the way that the SMDS circuit was engineered, and PacBell had to build up a new circuit which we’ve transitioned to. The engineering folks I worked with mumbled something about half versus full duplex, but the point is that it’s fixed, and fast again! -Dane

Mon Feb 8 18:01:40 PST 1999 — We’re running behind on expansion of capacity for our xxx-0174 (PacWest served) dialup numbers, and this is resulting in intermittant busy signals in some areas. More capacity is on order, and will be delivered by PacWest late this week. Meanwhile, in many areas where customers are using these numbers, there are alternate dialups, so if you find yourself experiencing a busy signal, you can check our POP finder for these numbers. The POP finder is at:

www.sonic.net/cgi-bin/pops.pl

Right now, at 6:10pm, we’re at 79% utilization, so there’s no busy signals, but I expect it to get a bit tighter as the evening goes on. For those of you in areas only served by xxx-0174 numbers, thank you for your patience as we wait for the phone company! -Dane

Mon Feb 8 17:54:28 PST 1999 — PacBell and UUNet are working on resolving slowdowns in the T3 SMDS cloud. This slowdown is causing some packet loss and long round trip times between us and UUNet. Emergency maintenance is being scheduled for the T3 circuit and should be completed on Tuesday. -Dane

Sun Feb 7 19:41:34 PST 1999 — West County dialups (-0174 numbers) are suffering due to problems with the PacWest tandems serving the area. PacWest is working on the problem; hopefully we’ll have a resolution later this evening. -Scott

Tue Feb 2 13:04:24 PST 1999 — We’ve just brought online a new dialup number serving West Sonoma County. The new number, 707-823-8812 replaces 707-887-0811 which will be decomissioned in the future. The new facilities offer v.90 and K56Flex support, plus ISDN. Sonic.net is not responsible for toll, so before using any Sonic.net dialup number, please check your telephone book or operator to assure that it’s local!

During these type of upgrades in the past, we’ve found customers who have v.90 or K56Flex modems, but who were connecting with v.34 may find previously unrevealed limitations in their modem. We recommend if you find yourself getting disconnected, or if your rate of speed decreases, you should contact your modem vendor. They may have a firmware upgrade which addresses any possible incompatibilities. If they don’t have an upgrade available, consider disabling v.90 and/or K56Flex and falling back to a stable v.34 connection instead. -Dane