I wrote this a few days ago, but didn’t have time to post, but it’s still relevant given all the discussion around SDN and Network Virtualization.

Getting into a long thread on Twitter is entertaining. You have to keep your thoughts short and concise and sometimes it’s hard to list every descriptive phrase known to man to articulate what you mean.  But…that also makes it fun! One example is the thread that happened last Saturday that I jumped into a little late.

Who will be the first to promote it?  Will it be via hardware or simply an application of network virtualization?  Because it will happen.

While some whole heartedly believe in not connecting sites with ANY type of layer 2, and I actually am a bigger believer in that now than I used to be, customers still ask and “require” this occasionally – namely for workload mobility.  Any answer I get or anything I read does not actively promote using an overlay such as VXLAN between data centers.  The responses are usually around 1. BUM traffic control 2. ARP localization 3. Traffic Trombone (since only one active default gateway) 4. STP isolation.  If you want to know all of the typical responses, look at the benefits of OTV.  But again, in a world that will soon be eaten by software, why can’t a viable solution be developed for L2 DCI with overlays?

I’ve read many of the predictions and trends that are expected to be seen in 2013.  I’ve seen articles that say straight up 2013 will not be the year of SDN, but on the other hand, have read articles that say the complete opposite – that SDNs are already here and now the focus is on the applications to further drive adoption of Software Defined Networks.  Who’s right?  We’ll have to wait and see because there isn’t a right or wrong answer at this point.

If you do look at many of the predictions being made you’ll notice a few common themes that I tried to capture here:

I was trying to prepare for a meeting a few weeks back on the topic of Hadoop; its impact on the network was supposed to be a large part of the conversation.  Needless to say, it wasn’t, but during the preparation, I was looking for material specific to building and designing networks specific for Hadoop environments.

Since there aren’t that many articles out there on the subject, I figured I’d share what I was able to find.

Pica8

Today, the industry officially welcomed another start up to the SDN world – Pica8.  I’ve been following these guys for a while as they posted on their blog and before their merger with Pronto.  At one point over a year ago, I even inquired about purchasing a Pronto Switch, but never pulled the trigger.  Check out the original Pronto Systems web site here for more background and history on their solution, products, and testing.  

Pica8 + Open vSwitch

In my last blog, I talked about Cisco’s Nexus 1000V, VMware’s VSS/VDS, and the Open vSwitch (OVS) as the three most deployed solutions for L2 virtual networking in the hypervisor.  One interesting fact here is that Open vSwitch can actually run as the control stack on a hardware switch as well.  Interesting?  Definitely – considering the majority of conversations around SDN have focused around data center network virtualization.  

What’s the foundation of the next generation data center network, i.e. this thing some call the software defined virtual data center network?  Many companies have recently re-branded their products and jumped on the Software Defined Networking (SDN) bandwagon in some way, shape, or form, and for good reason.  It has the potential to truly change networking as we know it today.  IDC has even stated SDN could be a $2B market by 2016. 

Let’s forget about all of this recent SDN washing and go back to virtual networking basics.  Most of us by now know what a software switch is.  It is also known as a vswitch or virtual switch.  This is arguably the most critical piece of real estate in the next generation data center network.  So, who owns this property?

Not much time to blog about this today, so this will be short, but another nice move for Cisco by announcing the acquisition of Cariden.  This is being seen by most as a great SP SDN play for Cisco, which indeed it is.  But remember, Service Providers have complex requirements, usually much more complex than Enterprises.  This means Enterprises may only need a portion of the Cariden solution to start dabbling in SDN that is available today, not in 6 months or not in 2 years.  So yes, Cariden was acquired for $141M and they do in fact have shipping products today, which is rare in the new and upcoming SDN community.  With that said, please note that Cariden had also announced integration with Big Switch’s Floodlight open source controller targeted at Enterprises.  With Enterprises potentially only needing a subset of Cariden’s actual feature set, I’m sure we may now see portions of Cariden’s application suite integrated as northbound applications riding on top of Cisco’s ONE SDN controller that is coming sometime next year letting Cisco provide an end to end solution potentially equivalent to the one Google announced last year at ONS.

How quick can you close a $1.2B dollar deal?  Supposedly it took Cisco and Meraki just four days.  “…they moved at lightning speed to get the deal done.  Within four days, we had a handshake agreement with Cisco.  They drove a fair bargain.” – Doug Leone, Sequoia Capital

Just over a year ago, I had my first encounter with Meraki.  Thanks to the Wireless Tech Field Day team, I was able to watch many of the sessions live from home.  Luckily, Meraki was one of them I got to see.  After learning a little bit about what Meraki was doing, it never seemed like rocket science, but it still seemed like magic.  They solved arguably the biggest problem in networking today – network management with a focus on the Campus. 

For those who visit here often know I'm a bit of an SDN purist , maybe even a Revolutionary.  But this article, it stemmed from several recent conversations on how the network will EVOLVE over time.  This pertains to data center only, so it's more relevant to the topic of *Empowering* the Software Defined Data Center (SDDC).  It was also meant to be a high level quick start guide regarding these trends.  For more details, I've written other posts and there are definitely a lot of others out there too. 

Here it goes.

Network Virtualization & Software Defined Networks

As an infrastructure and IT professional, you are probably overwhelmed with the amount of information and hype right now regarding topics such as OpenFlow and Software Defined Networking (SDN).  Rest assured you are not alone.  My goal is to simplify this messaging, review what can be done in the world of software and virtual networking today to meet the demands of Cloud, but will also lay the foundation for the next generation network.

There is no better time than now to be in the world of networking.  While it is changing significantly without many taking notice, we have exciting times ahead of us.  Many of us, including me, may even be out of a job in a few years once networking becomes truly automated, but for now, let’s embrace the change and see what happens!  Just in the past few months we’ve seen Nicira, vCider, and now Vyatta get acquired, not to mention the other SDN startups getting more VC funding, the most recent of this bunch, Big Switch Networks.  But, today’s announcement is clearly about Vyatta getting acquired by Brocade.

There was a recent blog on cisco.com by Eric Voit that discussed Software Defined Networking (SDN) with a focus on device proliferation in the data center and how this is impacting device configuration and management.  While I actually do agree that network management and reducing OpEx could be a huge driver for SDN in the short term, my focus here is on the broader topic Voit discusses – software based network integration.  This thing that we are calling “software based network integration” is going to be the foundation of next generation applications and next generation networks.  So, how will we integrate networks into an already functioning IT ecosystem in the future?  We’ll need some form of APIs and/or SDKs. 

It was just announced Riverbed will be acquiring OPNET.  With the growth of BYOD, Cloud, SDN, and Collaboration just to name a few of today’s hottest trends, it is now more important than ever before to have deeper visibility into both the network and the applications riding over the network.  For the mid-size Enterprise in my experience, they usually rely just on SNMP, WMI, and sometimes NetFlow to gain visibility to the network.  However, this data on its own is not enough to really know what’s going on throughout the network.  From my perspective, network and application performance management (APM) solutions are those that the incumbent network vendors should have been selling for the past decade.  These are what’s really needed.  How can you make a better network or make applications run smoother if there isn’t direct integration between the network and the applications (via an APM tool)?

I’ve been out of the Cisco world for a few months, but for the month of October, I’ve been trying to get re-focused as I watch the Yankees lose.  It’s been a month of several announcements, two of which I’ll focus on in this post:  the Nexus 1000V pricing update and the Cisco Edition of OpenStack.

Cisco 1000V Update

Early this month, Cisco made a major change to its pricing strategy for the Nexus 1000V virtual switch.  Prior to the announcement, the cost of the virtual switch was $695 list price per CPU.  It wasn’t a significant cost, but it was still a cost when you compare it to the no cost charge of using Open vSwitch (OVS).  Thanks to Nicira, well I guess VMware now, for the extreme focus on the development and success of OVS in the cloud and open source community.  Because of their work, it is now the standard offering in Citrix XenServer.  

If we use last year’s Interop as the OpenFlow/SDN coming out party, it took just over a year for Cisco to fully develop and announce a comprehensive multi-segment strategy.  Their SDN encompassing strategy is called Cisco Open Network Environment (ONE).  Congratulations, Cisco!  If they got David Ward back from Juniper sooner, maybe the strategy would have already been announced.  Joke…I really don’t have any insight as to who was or is responsible for the strategy, but would imagine it to be a fairly extensive team.

I think it was a good move to announce during Cisco LIVE.  Customers worship Cisco, not just for the products, solutions, architectures they develop, but also for this week long party where they receive gifts and gadgets, and soak up some of the most technical content in the industry, but most importantly can be around like-minded individuals.  That is the most important thing for those that are technically inclined and is often not understood by those who aren’t “down in the weeds.”

Greg Ferro does a nice job here directly stating the networking incumbents should step up with an SDN strategy.  I agree 100%.  Brad Casemore also chimes in with his thoughts.  If you aren’t already reading their blogs, I encourage you to do so because you’re missing out.

Several companies have announced they have OpenFlow-enabled switches, but for these companies, there is still no strategy and no reasoning as to why their switch should be used when deploying an OpenFlow based SDN.  Furthermore, they lack a strategy overall looking at the various components of a Software Defined Network.  From a hardware standpoint, some of the same features and characteristics  (buffers, table sizes, etc.) will still need to be compared as we already do today in traditional networks, but even that, isn’t documented in these announcements.  A lot of these vendors think they are on the offensive [vs. Cisco] announcing OpenFlow enabled switches (without a controller), but they really aren’t, in my opinion.

[Before you start reading, I need to give a big thanks to  Christian Esteve Rothenberg, Research Scientist at CPqD.  I asked if he wouldn't mind reading through this post prior to posting to ensure I didn't botch up anything on RouteFlow, and sure enough he immediately helped out and provided great feedback.  Christian also provided us with the picture you'll eventually see below and many of the RouteFlow links as well.  There was much more information he provided that I'll hope to get out soon too.  Thanks again, Christian.]

So...let's get to it.

Understanding “flow based protocols” and RouteFlow can change the way you think about networking and the protocols we use on daily basis.  I’m referring to control plane protocols such as Spanning Tree, OSPF, EIGRP, and BGP.  Based on the traction from this blog, I can see many people are searching for answers on what SDN means for the industry and what the future will be for a network engineer, etc.  If you are one of those people, first, ready my last post. It’s a quick synopsis of a presentation at ONS that covers some interesting automated tools already available for controller based networks.  And second, keep reading here.

I mentioned in my previous post Nick McKeown, uber smart Entrepreneur and Professor at Stanford, gave what I thought was the finest presentation of the week at the Open Networking Summit hosted in Santa Clara this week.  As I wait to board my plane back to the East coast, here is a more detailed recap of the presentation and what I took away from it…

Here is a quick summary on what I think worked well, what didn't work, and some thoughts on improving ONS next year.

What worked?

• Getting everyone together that has an interest in OpenFlow/SDN.  It was great to collaborate and talk with like minded individuals even though we, as an industry, are probably still on the incline of the hype cycle.
• Google, Yahoo, etc.  Anything these hyper scale companies talk about is damn interesting
• Exhibits – these are great for any conference and will only improve at ONS as more products are further developed and created.
• VC presentation by Lightspeed.  Great presentation here and I’m sure it got the wheels spinning for anyone with an entrepreneurial mind since they are still looking to invest and also believe it’s early in the life of SDN.
• Nick McKewon – see my next blog post.  This was the best presentation of the week.  Wish I could have seen Nick present all day.
• Pragmatic view by mostly all admitting there is still a way to go in this shift to SDN.
• Logistics, overall schedule, multiple projector screens, and the like. 
• There were many more presentation that were also intriguing, but those listed above were the ones top of mind right now.
• Overall, extremely glad I had the opportunity to attend ONS 2012.

With just a few minutes to spare until the 5:30 start of the evening event and exhibits, I thought I’d give a really quick summary of Day 1 at the Open Networking Summit 2012.  Note there were two tutorial sessions today and I attended the one for engineers.

The first thing you noticed by seeing everyone’s badges/name tags with associated company, and was confirmed by Brandon’s presentation in the first slide, was there was and is a truly broad audience here.  There are the obvious participants from the big name manufacturers, but also, there are between 1-3 people from at least 60 “other” companies, which is the category I fall into since I’m the only one representing BlueWater from NY/NJ.  I also had the pleasure of sitting next to the sole person from Aruba Networks as well.  Not sure what that tells you about their SDN strategy.

The term Software Defined Networking (SDN) has seemingly become main stream in the past several months being one of the hotter topics, if not the hottest, for the blog and twitter communities.  But, has it really gone main stream?  I’m not so sure.  In fact, I’ll say it hasn’t for sure.  The Open Networking Foundation (ONF) formed last year is largely made up of hyper scale web companies, “traditional” network companies, some niche network/services providers, new SDN companies focused on developing software and hardware, and Goldman Sachs.  But, does it really matter who is on the ONF from an end user’s standpoint?  Do Enterprise’s really care that companies are spending the $30,000 or so per year to be part of the ONF?  Do they [Enterprises] care that Facebook, Google, and Yahoo are exploring OF/SDN and are on the board of directors?  Doubt it.  They care about their requirements that need that of some fixin’.  99% of the environments out there do not replicate that of these hyper scale web companies.  If anything, they are more represented by that of Goldman Sachs, right?  While Goldman is likely still in the early stages of their SDN R&D, they are who I’d like to hear from.  Several years ago I was on the SE team at Cisco that supported Goldman.  I didn’t support them directly, but a peer of mind did.  These guys/gals at GS are smart, really smart, and it’s no surprise GS looks at the network from a business perspective.  Should they realize the benefit of SDN, it’ll be adopted.  If they adopt, others will follow, especially those on Wall Street.  Pay attention to them and their ONF efforts.

But….as a week full of SDN will be starting shortly, here are some other thoughts relating to the topic of SDN.  Many of which could be controversial =).

I’ve started thinking about the SDN ecosystem and realized there are A LOT of companies making announcements, but really, who is doing what, how do they all fit together, and what products can be purchased today?  That’s what I’m hoping to get across in this post.  

Before I get started, I’ll say upfront, for some of the companies in the ecosystem, they have clear and concise messaging – exactly what they are working on and what they have planned, which is great for all of us.  However, for a quite a few, I don’t know much (maybe you do) about what they are working on, but they are calling themselves next generation SDN companies.  Their websites couldn’t be vaguer, but I guess that’s all we can expect from companies in stealth mode.  With that said, feel free to comment if you have further information or corrections to make on anything that you see below.

12/27/2013 - New post here on various players in the SDN Ecosystem.