OpenFlow Coming To InteropNet Labs

One of the most interesting aspects of Interop is the Interop Labs area on the show floor, which highlights new and emerging technologies. In years past these technologies have included VPNs, network access control systems and various Trusted Computing Group projects. This year, InteropNet's OpenFlow Lab is going to showcase OpenFlow, with live demonstrations of the OpenFlow protocol. Openflow may well become an important networking protocol that will have significant impact on how you can depl

Mike Fratto

March 21, 2011

4 Min Read
Network Computing logo

One of the most interesting aspects of Interop is the Interop Labs area on the show floor,  which highlights new and emerging technologies. In years past these technologies have included VPNs, network access control systems and various Trusted Computing Group projects. This year, InteropNet's OpenFlow Lab is going to showcase OpenFlow, with live demonstrations of the OpenFlow protocol. Openflow may well become an important networking protocol that will have significant impact on how you can deploy and manage networks.

"Openflow is now mature enough to be investigated or adopted by enterprises. As switch vendors start to ship product, enterprises will have a chance to experiment with OpenFlow on their own, which provides an important feedback loop to tell the OpenFlow Consortium to help evolve and improve the specification," says Jed Daniels, director of product development at OPNET Technologies and team lead for the InteropNet OpenFlow Labs. While InteropNet doesn't have the names of the vendor participants yet, the demonstration will be running on equipment provided by vendors that support the OpenFlow specification. The labs will demonstrate loop free networking, dynamic load balancing across multiple links and quality of service for VoIP.

OpenFlow  is a network protocol, being developed at Stanford University, that manages the flow tables on network switches independently of the existing switch software. A flow describes a unidirectional set of frames or packets that share similar traits, such as source and destination MAC addresses, IP addresses, IP addresses and TCP/UDP ports, or anything that can uniquely differentiate one set of related frames or packets from another. The flow table in switches and routers is what commonly determines where a frame or packet is sent next.

Think of OpenFlow as a controller-based network where the forwarding and routing decisions are made centrally, similar to how controller-based wireless access points from vendors such as Aruba, Cisco and Motorola work. Greg Ferro has a nice writeup on Controller Based Networks for Data Centres that is worth a read.

Contrast the controller-based model with how network equipment is deployed today--every device discovers its own neighborhood or part of the world and individually makes forwarding decisions based on its own knowledge. Part of the complexity in routing and forwarding protocols and algorithms is ensuring that, independently, each participating device will build a coherent forwarding model. When the topology changes, it takes time for the devices to converge on the new topology. Applying rules to traffic such as quality of service, access control rules or load balancing is more difficult than it should be.While the distributed model of today works fine, controller-based networks do have several advantages. For example, Ethernet loops in the network are not a problem. Loops in Ethernet generally pose a problem because there is no way to stop frames from going in one port and circling back around again. Spanning Tree deals with loops by shutting off one leg of the loop. The controller builds a model of the network and connections and sees multiple connections between devices as alternate paths that it can use to forward frames. Access controls can be applied at any point in the network where it makes sense. Quality of service can be achieved by load balancing paths through the network, ensuring that no choke points develop (or alerting admins when they do).

One of the basic design parameters is that OpenFlow can run on existing switch and router hardware and can replace the hardware forwarding mechanisms or run concurrently with them. More vendors are beginning to adopt OpenFlow. For example, NEC has announced an experimental switch, and other vendors are showing interest.

Considering that many IT shops aren't yet at a point at which they are considering multipath Ethernet such as TRILL, Shortest Path Bridging, Brocade's VCS or Cisco's FabricPath, OpenFlow could be a useful alternative for multipath Ethernet. As with any standard, any equipment vendor that supports OpenFlow can participate in the network, allowing you to have a multivendor network. If you are at Interop, check out the demo. It is sure to be interesting. In fact, it was advertised on Time Square. (It's not Shopped, if you're asking)


About the Author(s)

Mike Fratto

Former Network Computing Editor

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