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.
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.
0 Comments
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. Let me be fair by saying I work on designs on a regular basis that are 99% Cisco. Of course, there are integrations with other equipment for every technology, but from an R/S standpoint, it’s mainly Cisco. Occasionally, I’ll come across competitive (to CSCO) information, but that’s about it. For this post, I wanted to make it a point to see what was out there in the new 40 GbE LAN switching market. It’s a topic that is becoming more popular (for various trends in the Data Center) and I’m really quite surprised about it all, so I figured let’s dive in and see who’s got what.
And this was a shallow dive. The goal was not to spend countless hours on each solution; I simply wanted to get a high level overview. The focus was just to try and get the following questions answered. Who has fixed configuration switches with 40GbE interfaces? Do they support “standard” L2/L3 protocols? Do they support some type of Layer 2 multipathing? Is there support for a type of MLAG? What is the port to port latency? What is the power consumption? Is there anything “special” about the switch, or is it unique in anyway? After a few seconds of thinking about it, I decided to focus on Arista, Dell Force10, Extreme, IBM, Juniper, Brocade, HP, and of course, Cisco. There are a few different warranty programs available from Cisco that are not widely advertised and discussed. However, given that every customer has different technical and business requirements, it is also true that each customer has different SLAs that have to be met internal to their organization. So let’s examine some of the options available.
There are standard SMARTnet (SNT) offerings from Cisco that are the norm including 24x7x4 and 8x5xNBD support offerings. These are probably two of the most popular offerings, but there are many others out there as well. It is important to note that each of the SMARTnet offerings from Cisco include 24x7x365 access to the Cisco Technical Assistance Center (TAC). I am not here to promote TAC by any means even though it is a world class organization, but this is questioned by the “8”x”5”xNBD usually found in the description of the SNT SKU being sold. The 24x7x4 and 8x5xNBD most importantly are referring to the turnaround time to get hardware replacements. So what if you’re an organization that has 200 user access layer switches, and you already spare a bunch of additional switches? Good question, and for me personally, I would first move away from 24x7x4 SNT if that was the case. Since the concern is no longer hardware replacement, the most important piece to the DAY 2 support puzzle becomes having a number to call in the case of a problem. Again, this is a where TAC comes in and you can leverage 8x5xNBD on the switches. It would be ideal to do a ROI of sparing vs. different levels of SNT being chosen to see which makes the best financial sense for the organization. Cisco or your local partner can help you with this. |
AuthorJason Edelman, Founder of Network to Code, focused on training and services for emerging network technologies. CCIE 15394. VCDX-NV 167. Top PostsThe Future of Networking and the Network Engineer Categories
All
Archives
May 2015
|