IT Is Woefully Behind Network Updates

The focus on software features and APIs in network equipment means a renewed emphasis on network maintenance that is severely lacking today. Network automation, adaptation and virtualization are increasingly focused around the software features of network equipment. The days of "speeds and feeds" have given way to the API. It is funny, I hear so much talk about APIs from network vendors that I am waiting for someone to tell me about the "Virtual, open-source, multi-port network appliance." It is

Jeremy Littlejohn

August 31, 2010

3 Min Read
NetworkComputing logo in a gray background | NetworkComputing

The focus on software features and APIs in network equipment means a renewed emphasis on network maintenance that is severely lacking today. Network automation, adaptation and virtualization are increasingly focused around the software features of network equipment. The days of "speeds and feeds" have given way to the API. It is funny, I hear so much talk about APIs from network vendors that I am waiting for someone to tell me about the "Virtual, open-source, multi-port network appliance." It is probably out there already, so send me the link if you have it.

This emphasis on software requires a new vigor around software maintenance, and this is an area that is virtually non-existent in most IT environments that we see. Network engineers are not paying enough attention to the software on their equipment. If IT plans on having the network power (in some cases literally), then IT must develop a methodology and strategy to update the software on its network equipment on a more regular basis.

Unfortunately, most IT infrastructure administrators are terrible about updating their software. Over the past month, I have been preparing RISC Networks' annual "State of the Network" report, and the data confirms that most engineers have an "if it ain't broke, don't upgrade it" attitude regarding their infrastructure equipment. In preparing our report, we took a look at 268 of the networks that we have performed analysis for over the last 8 months, and the problem of outdated software was rampant in many of these environments.

Of 268 engagements, 208 had at least one device with software that was over three years old. The oldest network software we detected was compiled in 1996. Seriously, 1996. Before you laugh, based on our data, your network is probably not too much better. We identified 480 total network devices that had software on them from before 2000. That is almost two percent of the over 30,000 network devices tested. These devices were spread among 48 different customers, or 18 percent of the networks included in the survey. If you raise the date threshold to 2004, indicating software that is at least 6 years old, the number jumps to 183 customers and 6,348 devices. That is almost 70 percent of networks. To add a little perspective, 2004 is the year that EMC bought VMWare for only $651 Million! Do you think the world of networking has changed since then? Then it is time to upgrade your software.

Cisco users seem to be the worst. While we had a significantly higher count of Cisco devices (28,0000+), they seemed to have the biggest problem staying current. The most popular Cisco IOS deployed is IOS Version 12.2(35)SE5. It accounts for 1,961 devices or roughly seven percent of all IOS devices. It was compiled in 2007 and is three years old. To put that into perspective, the code that powers seven percent of the Cisco devices in 268 networks was written before the iPhone was released.HP and other vendors were not immune either. While they faired much better overall, with the most popular software being from October 2008 (a total of 299 HP switches with H.10.74 code) that is still almost two years old. In most cases, code is loaded on equipment and deployed, never to be considered again. Only some significant external force such as compliance audits or security breaches move network administrators to upgrade their equipment code.

Much of this has been the fault of vendors. There has never been an easy way to upgrade network equipment without an outage. This is improving as SAN redundancy and reliability demands are coming to the LAN and vendors are implementing online upgrades. However, you can't always blame the vendors. IT departments have been slacking when it comes to a formal plan to upgrade network equipment on a regular basis. It simply must be part of the ecosystem of your network. Imagine a server that went three years without an upgrade.
 
As we put more emphasis on the APIs and features that the network can provide, a plan to manage the software that drives those devices is a must have if you are going to be successful.
 

Read more about:

2010
SUBSCRIBE TO OUR NEWSLETTER
Stay informed! Sign up to get expert advice and insight delivered direct to your inbox

You May Also Like


More Insights