Return to Main Menu

ClinLAN95 experiences growing pains During the past year, the MUSC Medical Center has been rolling out a new version of  “ClinLAN,” the MUSC-built assortment of software which brings order and manageability to the Medical Center’s thousands of PCs.  While “ClinLAN” was the name given to the old version of the system, which was based on Microsoft’s Windows 3.1 system, the new version is called “ClinLAN95” because it is based on Microsoft’s Windows 95 system. Since ClinLAN95’s debut in August 1998 during the opening of the Rutledge Tower, nearly 3,000 ClinLAN95 PCs have been set up.  More than 5,500 employees now utilize ClinLAN95. Last week, ClinLAN95 PCs throughout MUSC began experiencing frequent problems with printing and logging in to the MUSC network.  “We understand the seriousness of these problems, especially given MUSC’s dependence on ClinLAN95 for patient care and many other activities.  We sincerely apologize to our customers and patients, and we are working very aggressively to resolve the problems,” said Dave Northrup, director of Healthcare Computing Services at the Center for Computing and Information Technology (CCIT). What’s The Problem? Early last week, a problem arose in ClinLAN95’s Novell network login software which prevented some employees from logging in to their PCs and accessing the programs or ‘icons’ they needed.  The problem seemed to clear up around 10 each morning. All other MUSC systems, such as Oacis, Keane, Oversite, and GroupWise, were running trouble-free, but the ClinLAN95 login problem prevented access to these systems—from the user’s perspective, not much different than if Oacis, Keane, etc. were down themselves. When It Rains, It Pours At the same time the login problem developed, another piece of Novell software responsible for managing printing on ClinLAN95 PCs had begun crashing several times each day with each crash delaying network printing for approximately 30 minutes.  This problem had been seen sporadically before, and CCIT was already testing a workaround for this problem when the login problems began. Why Now? Two words: growing pains. With experience gained from ClinLAN, CCIT engineered ClinLAN95 to be much more flexible and with additional redundancy. Still, ClinLAN95 is a relatively new system that is being deployed on a huge scale. It’s difficult to test developments of this size and nature to absolute perfection beforehand in the computing laboratory. Delayed by the Columbia/HCA deal, but necessitated by Y2K issues, the conversion of thousands of PCs to ClinLAN95 began only 18 months ago with the first two thousand or so PC’s converted without major problems. But with the conversion of the final thousand PCs, the Novell login and printing software was overwhelmed. The Fix Novell engineers, on-site and off-site, have been working with CCIT engineers around the clock since shortly after the problems began. Novell confirmed that CCIT deployed their software exactly the way it was supposed to be deployed. In other words, Novell intended for its software to be able to handle logins and printing on a network the size of MUSC’s, but there clearly are some bugs in the software that weren’t exposed until the network grew to nearly 3,000 PCs. As of press time, though Novell expects to have its software fixed very soon, CCIT is preparing to deploy a workaround in the form of new ClinLAN95 services which will let users access critical programs and university systems, including printing, even if the Novell software malfunctions again in the future. “Plan B” CCIT’s workaround has two key components: 1. New printer method: An additional printing mechanism has been developed by CCIT, apart from Novell’s software, that will provide ClinLAN95 PCs with an alternate way of getting documents to printers. The switchover from one method to the other will require some effort from each user in order to direct printouts through the new system. Instructions for accomplishing this will be forthcoming from CCIT. 2. New software installation method: It’s the Novell login software that provides each user with individualized icons. CCIT is in the process of developing an alternate access mechanism in case the Novell login software becomes problematic again. To accomplish this, CCIT will be installing key software on the local (C:) drive of each ClinLAN95 PC, including Oacis and PMSI among others. If the Novell login problem occurs, a user may not have their individualized set of icons nor access to their personal files (stored on the “I: drive”), but this limitation will affect few patient care activities. “By installing software on each workstation for mission-critical applications such as Keane or Oacis, we eliminate a point of failure in gaining access to these and other systems,” said Bill Rust, CCIT manager of the Healthcare Network Services group.  “Only a major network failure could then prevent access, and the underlying network infrastructure has historically been very reliable technology.”  Rust added, “The design of ClinLAN95 remains solid, but we will be working hard to provide even more redundancy.” Northrup also commented, “Since StatLAN has to be retired before the end of the year due to Y2K issues, we understand the importance of being able to get to Oacis and being able to print ‘anytime from any workstation’ and we’re working day and night to ensure that access to clinical data continues as reliably in the next 11 years with Oacis as the last 11 years with StatLAN have been.”  Rust estimates the new printing method will be phased in beginning next week, and the new software installation method later in October. Northrup said CCIT will continue to keep users closely informed of progress via e-mail and other means.