Cisco Blogs


Cisco Blog > Open at Cisco

Why I Chose the Open Source Model I did for OpenDaylight

Now that OpenDaylight has arrived, it’s time to explain why I made the Open Source choices eventually embraced by its Founders and the community at large.  One doesn’t often see such leaders as Cisco, IBM, Intel, HP, Juniper, RedHat, VMWare, NEC, Microsoft and others agree, share and collaborate on such key technologies, let alone the latter engaging in a Linux Foundation based community (some thought hell will freeze over before that would ever happen, though it got pretty cold at times last Spring).

For those of you not familiar with OpenDaylight (see “Meet Me On The Equinox”, not a homage to Death Cab for Cutie or my Transylvanian homeland), IBM and Cisco have actually started this with an amazing set of partners, nearly that ephemeral Equinox this year (~11am, March 20th) though we couldn’t quite brag about it until all our partners saw the daylight, which by now, we’re hoping everyone does.  It was hard not to talk about all this as we saw those half baked, speculative stories before the Equinox – amazing how information flew, distorted as it were, but it did; I wish source code would be that “rapid”, we’d all be so much better for it…

The Open Source model for OpenDaylight is simple, it has only two parts: the community is hosted in the Linux Foundation and the license is Eclipse.  The details are neatly captured in a white paper we wrote and published in the Linux Foundation.  Dan Frye, my friend and fellow counterpart at IBM and I came up with the main points after two short meetings.  It would have been one, but when you work for such giants as our parent companies and soon to be OpenDaylight partners, one has to spend a little more time getting everyone to see the daylight.  It boils down to two things, which I am convinced are the quintessential elements of any successful open source project.

1) Community.  Why?  Because it trumps everything: code, money and everything else.  A poor community with great code equals failure (plenty of examples of that).  A great community with poor (or any) code equals success (plenty of examples of that too).  Why? Because open source equals collaboration, of the highest kind: I share with you, and you with me, whatever I have, I contribute my time, my energy, my intellectual property, my reputation, etc.. And ultimately it becomes “ours”.  And the next generation’s.  Open Source is not a technology; it’s a development model.  With more than 10 million open source developers world wide, it happens to be based on collaboration on a scale and diversity that humanity has never experienced before.  Just think about what made this possible and the role some of the OpenDaylight partners have already played in it since the dawn of the Internet.  Dan Frye and I agreed that the Linux Kernel community is the best in the world and so we picked the closest thing to it to model and support ours, the Linux Foundation.

2) Fragmentation, or anti-fragmentation, actually.  Why?  The biggest challenge of any open source project is how to avoid fragmentation (the opposite of collaboration).  Just ask Andy Rubin and the Android guys what they fear the most.  Just ask any open source project’s contributors, copyright holders, or high priests, how much they appreciate an open source parasite that won’t give back.  Though we would have liked to go deeper, we settled on Eclipse, largely because of the actual language and technology we dealt with in the OpenDaylight Controller: most, if not all the initial code is Java, and though some are worried about that, I’m sure Jim Gosling is proud (btw, I’m not sure the Controller has to stay that way, I actually agree with Amin Vahdat), but we had to start somewhere.  Plus having a more friendly language NB (northbound, as in the applications run on top of the Controller) is such a cool thing, we think that the #1 open source (Eclipse) and the #1 commercial (Microsoft) IDE’s are going to be very good to it, so why not?  There are more reasons that pointed in the Eclipse direction, and other reasons for such wonderful alternatives (as APL or MPL, perhaps the subject of another post, some day).  But when it comes to understanding the virtues of them all, no one understands them better than the amazing founders of these license models, most of them from IBM, of course (I wish they did that when I was there).

What happened between the Equinox and Solstice is a fascinating saga within the OpenDaylight community which I think played its course in the spirit of total and complete openness, inclusion, diversity, respect of the individual and the community, and most of all, that code rules – we do believe in running code and community consensus.  I tip my hat to all my fellow colleagues that learned these two things along the way, the enormous talent at the Eclipse and Linux Foundation that helped us launch, and even the analysts who tried (and did incredibly well at times) to speculate the secret reasons why these partners came up with the model we did: there is no secret at all, my friends, we’re simply creating a community that is truly open, diverse, inclusive, and never fragmented.  Just like a big, happy family.  Welcome to OpenDaylight, we hope you’ll stay!

Tags: , , , , , , , , , , , , , , , ,

Announcing Cisco Wireless Release 7.5

With the prevalence of mobile devices connecting people and things today, we are seeing a base expectation for uncompromised wireless connectivity. There is no doubt that the trend for high performance, pervasive wireless is on the rise and will continue for the foreseeable future. We at Cisco strive to help organizations get ahead of these trends with solutions that can be deployed with confidence today.  That’s why I am proud to announce the latest Cisco Wireless Release 7.5, the third feature-rich release we’ve had in the last 12 months.

Release 7.5 enables mission critical wireless deployments with sub-second stateful failover for wireless clients, wire-like Gigabit performance with the 802.11ac Module, and a bevy of other features.

Key Features in 7.5:

Tags: , , , , , , , , , , , , ,

Success with Cisco Bonjour Services Directory

July 24, 2013 at 5:00 am PST

Have you seen this video?

For those of you who are not familiar with the technology, Bonjour is a multicast DNS(mDNS) based protocol used to advertise and connect to network services such as printers, file servers, TV’s. With the BYOD explosion and increased use of mobile devices for work in the office and classroom, Bonjour is applicable not only at home, but also in enterprise. Last Christmas with the 7.4 release, Cisco introduced the Bonjour Services Directory optimized for enabling enterprise campus environments to share Bonjour services across Layer 3 networks.  In this blog, I will share some details about how a K-12 school successfully deployed Cisco wireless solution to provide Bonjour Services. As a special treat, I will also discuss some details on Bonjour enhancements included with the upcoming 7.5 release.

St. Margaret’s Episcopal School (SMES) is a K-12 school based in Orange County California serving about 1200 students. The wireless deployment consisted of 30 Cisco 1140 Series Access Points , a Cisco 1260 Series Access Points and some Cisco 1130 Series Access Points managed by a Cisco 5508 Series Wireless LAN Controller. The wired access deployment included various Catalyst 3750, 2960 and 2950 Series Access Switches. Cisco Networking Assistant(CNA) allows them to keep a bird’s eye view on all the equipment.

bonjour 1 Read More »

Tags: , , , , , , , , , , ,

Wireless Controller Redundancy with No Client Reauthentication Needed

July 12, 2013 at 5:00 am PST

Last fall, I blogged about No SSID Outage or Access Point Stateful Switchover introduced with the AireOS 7.3 release whereby if your wireless LAN Controller fails due to some hardware failure, thousands of Access Points fail over sub-second to the standby controller! This is possible due to continuous synchronization of CAPWAP states, Configuration Changes, Radio Channel and Power, Roaming Keys and Access Point licenses between the two Controllers. This means even if the administrator changes the configuration, channel plans or the clients roam and the primary controller fails; the Access Points will simply fail over in a stateful fashion to the secondary. In this blog, I will share details on the upcoming enhancements to High Availabilty with the 7.5 release.

In the upcoming AireOS 7.5 release, we take High Availability to the next level with two critical enhancements.

1. Today, after Access Points fail over from the primary to the standby controller, each client tries to re-authenticate and the standby controller then checks against its CCKM database whether the client has already authenticated. At the rate of several tens of authentications per second, it can take anywhere from zero to a few hundred seconds for the tens of thousands of clients that are connected to a controller to re-authenticate. The client stateful essentially eliminates this downtime with sub-second failover. Thus the total downtime that any user running a voice-call or Citrix session experiences is 2-3 seconds that the application requires to reconnect.

sso1 Read More »

Tags: , , , , , , , , , , , , , , ,

What is a “Controller”? And how many do we need?

June 26, 2013 at 6:10 am PST

Thanks to SDN, the “Controller” word pops up in many network architecture discussions these days. In networking alone, we’re already surrounded by many “controllers” and we’re busy introducing more as we speak:  For example, Session Border Controllers or Wireless LAN Controllers have been around for quite some time, and have recently announced the OpenDaylight Controller, the Cisco XNC, or the Cloupia Unified Infrastructure Controller. So what is a “Controller” in networking terms, and how many do we need in emerging network architectures?

Read More »

Tags: , , , , , ,