Searching for Answers with Virtualization (
Page 1 of 2 )
Case Study: Solution provider AccessFlow helps the law of firm Eskanos & Alder solve its virtualization woes.Simplify and virtualize was the law firm of Eskanos & Adler's credo when replacing an overly complex network its IT staff couldn't manage. For help, the firm called on AccessFlow, a Sacramento, Calif., solution provider.
AccessFlow recommended a virtual network built around VMware ESX servers and Cisco Systems switches. The network saved money and provided IT flexibility and scalability, said Steve Kaplan, president of AccessFlow.
The firm also replaced difficult-to-use Avaya phone systems with a Shore-Tel VOIP (voice over IP) solution, cutting cost and complexity.
"We had gotten to the point where our network had become so segmented and complex that our IT staff was having difficulties performing such simple tasks as adding a computer to the network," said Paul Hicks, director of IT at Eskanos & Adler.
The law firm employs 230 people and specializes in the recovery of delinquent consumer and commercial obligations for clients such as American Express and Sears, Roebuck. In 2002, an e-mail virus hobbled the firm's IT network for several days, and that's when the trouble started. The cure, designed to prevent future disasters, made things worse.
To listen to an eWEEK podcast on the state of virualization, click here.
Good idea gone bad
A systems engineer hired as a consultant by Eskanos & Adler to prevent future downtime implemented a firewall and multiple VLANs (virtual LANs). It seemed like a good idea, but as the firm grew and VLANs were added, things became too complex.
"Other than the engineer, nobody on the IT team fully understood how the network worked or was configured," Hicks said.
Complexity went from bad to worse in 2003 when Eskanos & Adler added a remote California office with a second Avaya telephone system. More VLANs were added.
"By the end of 2004, we found ourselves with an extremely complicated network that was causing serious problems," Hicks said. IT personnel could not add computers without involving the network engineer, who alone understood the system.
"There were unexplained network delays and dropouts," Hicks said. The firm hired two consultants to analyze the network, and they were stumped by its intricacy.
Instability weakened the firm's disaster recovery capabilities and raised concerns about its ability to meet the exacting recovery requirements of its big financial customers.
Eventually Hicks and his staff decided they'd had enough, concluding they had better redesign the network, replace the Avaya systems and bring in external help.
VMware's technology struck Hicks as the most workable solution because of its simplicity, reliability and relative low cost. AccessFlow assessed the firm's needs and drew up a plan.
"We liked AccessFlow because it was the one [solution provider] that brought up the importance of having a suitable network configuration as part of a successful VMware implementation," Hicks said.
AccessFlow discovered the VLANs had been created as independent logical networks within the physical network. The technology itself was not the problem, but rather how it was implemented, said AccessFlow's Kaplan.
Experts see a link between virtualization and SOA. Click here to read more.
"The virtualization technology is rarely the problem because VMware is very powerful and scalable," Kaplan said. "What is often missing is the proper planning and underlying infrastructure to make it all happen."
A new network was designed around virtualization that had a secure outer shell protecting a simple-to-use core. "We liked the design because it would enable us to reuse many of our existing components," Hicks said.
The bones of the old network consisted of a Cisco 3750 and two 3500 switches, and FortiGate 200 and 100 firewalls. Fifteen servers were connected directly to the Cisco 3750 switch, some with a Gigabit Ethernet link, most with 100 M-bps connections. Four T-1 lines (two for voice and two for data) linked the firm's main office to a branch office, where a second Avaya system had been installed.
The telephone systems were a lot of work to maintain, and the Avaya interface was of the older command-line variety requiring hard-to-master syntax, Hicks said.
Next Page: Getting It Right
