Of the many things we can be thankful for as we launch into 2005, one is the knowledge that we won't be using our entire IT budget just to feed the network beast. Where a first-generation Gigabit Ethernet card could cost several thousand dollars, CDW's home page (as I write) displays a brand-name network interface card for $34.95. But, like most things, there are some trade-offs. We must ask ourselves - does quality sometimes fall along with price?

As I look back on the last two years, it just seems to me that we encounter more "bad cards," "bad ports" and "bad modules" than, say, five years ago. Given the wholly unscientific nature of my observations, I decided to conduct some brief research on how network vendors were dealing with mean time between failures (MTBF) of their devices.

And as "cheap" as network gear is, the real expense isn't in the capital cost of a new NIC or a switch, it is in the lost business and user productivity that occurs when the device fails. Add to that the time to isolate the failure and source a new piece of gear if, for example, you don't happen to have a spare switch on hand.

I think most people running small- to midsize-business (SMB) and enterprise networks would echo NASA's Gene Kranz (former director of mission operations at the Johnson Space Center in Texas) and say, "Failure is not an option." But getting there may not be easy.

I recall years ago, when IBM offered some early network products on its PC platform, hearing the representative boldly state that the MTBF was 10 years. This on a box that had only been shipping for a year or so. But he was serious - "Yup, 10 years and we are in the second year of the test." At that time, at least, a part of the process was actually to run a set of devices in the vendor lab to parallel what customers were doing.

Most often, though, industry-accepted formulas organizations such as BellCore/Telcordia produce are used to predict the likelihood that any part in the assembly will fail.

It is anyone's guess how vendors treat MTBF internally, but from the outside looking in - by way of Web sites and spec sheets - it is a mixed bag indeed.

Only the so-called "industrial Ethernet" vendors and providers of service-provider-class gear seem to push MTBF. With most enterprise and SMB products, that information is either buried or often simply invisible.

Whitepapers

• Best Practices for HP Servers and HP Enterprise Virtual Array in a Microsoft Exchange
• Network-Wide Change Management Visibility with Route Analytics
• REMOTE CONTROL: How to Reduce the Cost, Complexity and Risk of Managing Your Distributed IT Infrastructure
• Steal This Script: Hands-On Tips for Service Impact Network Management
• The Case for an Untethered Enterprise
• Best Practices for WAN Optimization with Data Replication

View more LANS & WANS whitepapers

Webcasts

• WAN Optimization Editorial Webcast
• Best Practices for Deploying WAN Optimization for Disaster Recovery
• Tips and Techniques for Remote Data Backup and Delivery
• WAN Optimization Landscape
• High Availability for SQL Server 2005 Using Array-Based Replication and Host-Based Mirroring Technologies
• Technical Overview of Exchange Server 2007 with HP Servers and Storage

View more LANS & WANS webcasts

Special Reports

• Network World Executive GUide: The Virtualization Equation
• Get More From Your WAN
• Learn how to Keep your Mobile Workforce Connected
• WAN Optimization: How to rev up sluggish applications
• The Wireless Explosion
• Network World Executive Guide: Perfecting Application Performance Management

View more LANS & WANS special reports