At the end of this month, MicroMuse Inc. will address the scalability issues that have dogged large enterprise users of its NetCool/Omnibus event management software.
The network and systems management tool, widely used among service providers and large enterprises to manage IP networks, was re-architected to be able to handle hundreds of concurrent operators and manage hundreds of millions of network alarms in a day.
Also driving the improved performance and scale of NetCool/Omnibus 3.5 were customers looking to keep up with an increasing number of security alarms and wireless service providers looking to manage their services as they scale, according to Brent Compton, director of product management at London-based MicroMuse. "One customer is a security surveillance service provider. Last year they ran just under eight million security alarms a day, and they expected it to grow to 40 million alarms a day," he said. The user is working with the NetCool for Security Management option.
"Product scalability is a chronic issue we hear about on a regular basis," echoed Paul Bugala, senior analyst at International Data Corp. in Framingham, Mass. "It gets more difficult as you try to incorporate more analysis in terms of root cause and add more elements to be managed," he added.
For large-scale NetCool users who use the tool for a variety of different types of uses, the performance boost is a welcomed relief. "We have project managers, command center users and second-line support using our system," said one NetCool user, who asked not to be identified.
That NetCool implementation at a large telco supports casual users working on hundreds of projects who access the NetCool system via Web browsers and first-line support users. "We use it for service-level views as well," added the user.
Netcool 3.5 can now support two-tier or three-tier hierarchical processing cores. The previous version was comprised of a single object server and multiple desktops. The new release allows multiple collection object servers to feed pre-processed data into the central processing core, which is directly accessed by desktops. The three-tier architecture includes both collection object servers and the central object server and adds desktop servers that sit between the central object server and the desktops, distributing the read-only processing load.