IT Can Be Choosey With Network Management

 
 
By Cameron Sturdevant  |  Posted 2002-03-14 Email Print this article Print
 
 
 
 
 
 
 

eWEEK Product Update: Tools have matured, giving managers real choices for analyzing faults, monitoring service levels and managing devices.

Network monitoring tools ranging from Hewlett-Packards OpenView to Silverback Technologies InfoCare are entering a third stage of maturity. But this upward spike in product usability doesnt mean that IT managers should buy every single one of these tools. IT managers need an element manager that can provide fault information, one or two service-level monitoring and management tools, and enough budget and staff to make sure these tools are integrated into the help desk system.
Networks grew tremendously in the 1980s, and management systems such as the Enterasys (then Cabletrons) Spectrum and HPs OpenView—along with a host of brand-specific element tools—started knitting together what we now know as network management. Many of the early problems have been overcome, including floods of false-positive alerts, cross-platform blind spots and immature configuration tools from equipment makers.
After experimenting with and rejecting the overarching enterprise management systems (they were a good idea, and one that may yet have some benefit in the future) in the 90s, IT managers can now choose among mature products from a much-winnowed field. This means that nearly every sales pitch is going to sound good, but IT managers need to bring some common sense back to the discussion, especially when it comes to service levels. When dealing with the still-brassy service-level vendors, break the products into two groups. External service-level agreements should be monitored with reports provided by the ISP and, at least at the beginning, by one or more tools controlled by the enterprise. Measurement tools such as Compuwares PointForward can answer the question "what did the end user experience?" The second group, internal service levels—which should really be called service rationing—should be methodically set up whenever a new application is introduced or the network topology changes. Then, leave them alone and monitor traffic trends over time. The general trends are often much more interesting (especially when presenting to senior executives) than the day-by-day action on the network.
E-mail eWEEK Labs Senior Analyst Cameron Sturdevant
 
 
 
 
Cameron Sturdevant Cameron Sturdevant is the executive editor of Enterprise Networking Planet. Prior to ENP, Cameron was technical analyst at PCWeek Labs, starting in 1997. Cameron finished up as the eWEEK Labs Technical Director in 2012. Before his extensive labs tenure Cameron paid his IT dues working in technical support and sales engineering at a software publishing firm . Cameron also spent two years with a database development firm, integrating applications with mainframe legacy programs. Cameron's areas of expertise include virtual and physical IT infrastructure, cloud computing, enterprise networking and mobility. In addition to reviews, Cameron has covered monolithic enterprise management systems throughout their lifecycles, providing the eWEEK reader with all-important history and context. Cameron takes special care in cultivating his IT manager contacts, to ensure that his analysis is grounded in real-world concern. Follow Cameron on Twitter at csturdevant, or reach him by email at cameron.sturdevant@quinstreet.com.
 
 
 
 
 
 
 

Submit a Comment

Loading Comments...
 
Manage your Newsletters: Login   Register My Newsletters























 
 
 
 
 
 
 
 
 
 
 
Thanks for your registration, follow us on our social networks to keep up-to-date
Rocket Fuel