Upcoming Events

Cloud Connect
Santa Clara
Feb 13-16, 2012

Cloud Connect brings together the entire cloud eco-system to better understand the transformation we're experiencing and promises to be the defining event of the cloud computing industry. Learn about the latest cloud technologies and platforms from thought leaders in Cloud Connect’s comprehensive conference.

Register Now!

F E A T U R E

Network Management on $1.19 a Day

February 6, 2003
By Bruce Boardman and Andy Woods

>> continued from previous page

Readers in Focus

	Issue TOC
	Print full article
	Print this page
	Download as PDF
	E-Mail this URL
	Discuss this article
	Flame the author

	In this article
	Introduction
	Readers in Focus
	What To Expect
	Executive Summary

We asked readers responsible for network management how they'd prioritize the FCAPS model based on two scenarios. First, we asked what areas they'd focus on if money were no object. It was no surprise that security was most important, chosen by 61 percent, followed closely by fault and performance, then trailing off a bit for configuration, with accounting bringing up the rear.

Then we asked the same readers to prioritize FCAPS management functions if they had the budget to accomplish only one task. Security, while still holding the top spot, led by a smaller margin. Fault management remained strong, and performance and configuration held their own. Accounting may make sense, but it's not high on anyone's list, money or no.

So how much management bang can you buy for 10,000 bucks? Surprisingly, a lot. Managing 1,000 interfaces will get you control over the backbone, important network nodes and servers in a 10,000-node network.

But what about ROI and TCO? Those are big sticking points if you're doing the usual megabucks network-management thing, but how about $800--the price of our Best Value award winner? That eases worries about financial models, business impact and that nasty project creep.

FYI

Node Lode: What constitutes 1,000 nodes or, more accurately, 1,000 interfaces. How do you define an interface? The distinction becomes even cloudier when collecting performance data. Are all the MIBs available on a device considered a single managed instance? Maybe, but not always. We managed a couple dozen devices that included some Cisco 6509s with 90-plus interfaces. So, with a big centralized switch/router like a 6509, a dozen supporting switches, edge routers and a simple two-tier application, we had 1,000 nodes at the core that were vital to the much larger 10,000-node network.

Of course, even a single dollar is too much to spend if you're not going to benefit. That is not the case here: Automation of response and reporting improves productivity. Report distribution, via Web and portal delivery, improves intercompany communications and fosters self-service. For example, Web reports supplied to business groups give them availability information on their servers and the network, helping them identify downtime problems and direct their inquiries when a process is failing. Performance baselining can improve capacity planning and lead to more proactive management.

Most important is the time it takes to implement and maintain these products, which has always gobbled the biggest slice of the network-management implementation pie. Some inexpensive products, because they can't go beyond simple monitoring or performance gathering, aren't going to cost a lot. Others that limit their functionality based on price will, if expanded to cover other portions of the FCAPS model, increase TCO.

You should also consider your network's growth prospects: If you see significant expansion in your future, then buying a product that will grow with you will let you leverage the installation going forward.