Tom Hollingsworth

Upcoming Events

Where the Cloud Touches Down: Simplifying Data Center Infrastructure Management

Thursday, July 25, 2013
10:00 AM PT/1:00 PM ET

In most data centers, DCIM rests on a shaky foundation of manual record keeping and scattered documentation. OpManager replaces data center documentation with a single repository for data, QRCodes for asset tracking, accurate 3D mapping of asset locations, and a configuration management database (CMDB). In this webcast, sponsored by ManageEngine, you will see how a real-world datacenter mapping stored in racktables gets imported into OpManager, which then provides a 3D visualization of where assets actually are. You'll also see how the QR Code generator helps you make the link between real assets and the monitoring world, and how the layered CMDB provides a single point of view for all your configuration data.

Register Now!

A Network Computing Webinar:
SDN First Steps

Thursday, August 8, 2013
11:00 AM PT / 2:00 PM ET

This webinar will help attendees understand the overall concept of SDN and its benefits, describe the different conceptual approaches to SDN, and examine the various technologies, both proprietary and open source, that are emerging. It will also help users decide whether SDN makes sense in their environment, and outline the first steps IT can take for testing SDN technologies.

Register Now!

More Events »

Subscribe to Newsletter

  • Keep up with all of the latest news and analysis on the fast-moving IT industry with Network Computing newsletters.
Sign Up

See more from this blogger

OpenFlow 1.3 Support: Why It Matters

OpenFlow is quickly becoming a very important foundation of the future of networking. Vendors are rolling out support for the latest version of the protocol -- OpenFlow 1.3 -- across a variety of product lines. This means customers can start architecting software-defined networks with the assurance that OpenFlow will be available for the long term.

The importance of OpenFlow 1.3 support cannot be understated. The original release of the protocol, OpenFlow 1.0, contains support for a limited subset of switching functions, and allows for activities such as network slicing and matching on Type of Service (ToS) markings on a packet. But it doesn't include many other features that are important to enterprise customers and service providers.

More Insights


More >>

White Papers

More >>


More >>

Fortunately, OpenFlow developers didn't stop innovating. The Open Networking Foundation, which manages the protocol, quickly released improvements in version 1.1 and 1.2. However, development was occurring too quickly for vendors to keep up; products in the design phase were developed on obsolete software before they were even released.

Consequently, vendors pushed back and asked for the OpenFlow development cycle to slow down. OpenFlow version 1.3 allowed vendors to catch up to a stable version before the ONF started iterating again.

OpenFlow 1.3 support is critical to the future of OpenFlow-enabled networks. The features that are enabled in version 1.3 are are very important in datacenter and campus networking: IPv6, Quality of Service (QoS), and support for service provider Q-in-Q tunneling. More important is its leap from basic support to incorporating a more robust feature set. Changing the architecture of a switch to support OpenFlow isn't easy, and there had been questions about scalability and feature completeness with OpenFlow 1.0.

By supporting OpenFlow 1.3, vendors can show customers that they are committed to the protocol long term. Building in new features with each release means that OpenFlow is quickly reaching parity with other network operating systems. Ensuring that those features can be installed on a given device is important to customers -- no one wants a device that can only run an old version of OpenFlow and can't be upgraded. Lab equipment is great for testing to prove a protocol can function in a production network, but it isn't made for production deployment.

[Read how new forwarding technologies and the emergence of SDN are changing the Ethernet switch landscape in "The Evolution Of The Ethernet Switch."]

OpenFlow 1.3 represents production-grade OpenFlow. The recent announcement from Brocade of OpenFlow 1.3 support across its MLX and VCS product lines shows that vendors are ready to bring OpenFlow out of the testing lab and into the live network. NEC and HP already have OpenFlow 1.3 support and companies such as Juniper plan to release support in the coming months.

For those looking to deploy OpenFlow in a modern datacenter, OpenFlow 1.3 is the key. With critical features and a stable code release, customers can finally go to the decision makers and plead their case. Hardware support for multiple versions of OpenFlow means that the features can evolve over time. The stability of OpenFlow 1.3 means no late nights debugging network behavior due to incomplete code.

OpenFlow 1.3 is the future of networking. Vendors looking to evolve their network products lines are either already shipping this version or soon will be. Customers can now feel confident that the changing architecture of the software-defined network now has sustainability.

Tom Hollingsworth, CCIE #29213, is a former VAR network engineer with 10 years of experience working with primary education and the problems they face implementing technology solutions. He has worked with wireless, storage, and server virtualization in addition to routing and switching. Recently, Tom has switched careers to focus on technology blogging and social media outreach as a part of Gestalt IT media. Tom has a regular blog at and can be heard on various industry podcasts pontificating about the role technology will play in the future.

Related Reading

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | Please read our commenting policy.
Vendor Comparisons
Network Computing’s Vendor Comparisons provide extensive details on products and services, including downloadable feature matrices. Our categories include:

Next Gen Network Reports

Research and Reports

Network Computing: April 2013

TechWeb Careers