Mike Fratto

Network Computing Editor

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 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 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.

openflowswitch.jpgOpenFlow  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.

Page:  1 | 2  | Next Page »

Related Reading

More Insights

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