Imagine if you will having your own droids running around your network testing for and remediating issues as they happen. This would change the way we work.
I have been very lucky in my career. There is pretty much no network vendor whose gear has not come across my desk and I have had the opportunity to install and play with on some level. Last year we engaged Meraki to consider then for both their Cloud Controller based Access Points but also for their new Access Switch product line. I did lots and lots of research and honestly found a mixed bag of info. On one hand people were saying this is really amazing stuff and if you can handle a bit less than full enterprise class gear you should really look at it. On the other hand I read a few articles like this one out of Canada that paints a picture of pretty shady practices from Meraki.
So I sat through their online demos, had local partners come in to tell me how amazing it was then I got my AP (Modle MR12) from them to play with and see what I thought. In all honestly their AP and overall wireless product underwhelmed me. My Cisco 1200 B only radio covered better and and my Cisco 1252 even in 2.4 only mode way out gunned this poor little guy. But what they do very very well is the management of it all. Even after I had decided that my company would not be moving to their access points nor the new switch line I decided to stick with System Manager because how good it was at managing remote devices and it was free! So right off the bat I do not hate these guys or their products I actually think they are pretty cool but over just not the right fit for what we needed.
Then tonight it happened. @MrFogg97 hit me up and said “Saw this on #meraki’s site when reading the announcement. http://twitter.com/MrFogg97/status/270346667495145472/photo/1 and yes I did say that and to this second I still believe its a great product. But then I asked myself what announcement. A quick trip to Meraki’s website told the tale. Cisco announces intent to acquire Meraki And that is why I am really writing this post. Read more
So tonight as I was getting into bed I did my normal scan twitter to see who I have pissed off or what might be going on that should rob me of sleep. Well tonight @david_Strebel asked the following questions;
“Who thinks FCoE will win over iSCSI?” and I responded “Not I” and then David asked the next logical question which was why not and here is what I had to say in the incredible detail that Twitter allows; “l2 boundaries, specialized hardware other than nics, hate relationship from most network people.”
The problem with this answer is pretty clear though. It does not really answer the question just gives a few power point bullets to appease the crowd. I don’t feel like this is enough though. So I am going to attempt to lay out my overall view on this issue of who will win iSCSI or FCoE and why. For those of you who don’t want to read the whole article which might get a a tad windy I don’t think either will win. But I don’t think FCoE will emerge as the leader until something better come along. For those masochists who like this kind of crap read on.
I will be the first to admit that I make mistakes. I make lots of mistakes. But I learned a long time ago that it is not the mistakes that define us but
what we do when we make them. To that point it is both fascinating and infuriating when I enter someone’s network land and find that they have gone out of their way to do nothing to solve their own problem or in many cases to even
build a proper functioning network. So I am going to set out to show the Methods I use to deal with these people and their problems and the Madness that they have brought to the table to cause the issue.
This is going to be a series. Really my first series of posts, and they will all fall under the heading of Method and Madness with some sort of witty little
tagline. I will be pulling on a careers worth of situations that were totally preventable and how we resolved the problem or moved past it.
The format for each of this will be as follows:
Situation: This will be the “lab” Scenario piece of the post in which I outline
the base problem as well as the end goals of the situation. This section will
include a base diagram for use as reference.
The Method: This will be the troubleshooting and resolution phase of the post and
will breakdown the ultimate solution or bypass to the problem.
The Madness: This section will be my analysis of how things got to this point in the first
place. Keep in mind I have no in interest in posting garbage about oh look the senior
network engineer put a wrong static route in at 4am and a junior guy had to find it.
No I am more interested in exposing the issues where a Network Engineer or worse a team could not solve a problem that should be second nature for them to solve. In doing so I hope others will learn from and not find themselves in these situation.
So with all that said look for them. I hope to have the first one out by the end of
the week with about 50 Million other projects so bear with me. I think these will be a great recap for me and both education and humorous for you. I really encourage your feedback on these posts because I am not always right and there are lots of different paths so resolution of a problem.
So last night while working on a Scalable Compute and storage design for a client, this post popped up in my twitter stream from @ErinatHP;
New HP blog post “In the light of day the Cisco UCS hype doesnt match the promise” ; UCS not all its marketed to be http://bit.ly/dKj88W
So in my normal do not let a stupid dig by a lame duck player go unmatched I responded Oh I can’t wait to read this FUD (you can check me out on twitter @joshobrien77)
All the twitter marketing and pissing matches aside I meant what I said and I did look forward to reading the HP Spin on where their market is vanishing to. And here are my responses, while they might not be the most technical they are not un-informed from the basis of the Cisco UCS platform or the HP C7000 with FLEX-10 Platform. And remember at the end of the day I represent me not Cisco not my employer, just little old me.
Also just so if this gets nasty I want to make sure that I am crediting this correctly:
All of the HP Writes: Are direct Quotes from Duncan Campbel with HP on his blog which you can find here: http://h30507.www3.hp.com/t5/Converged-Infrastructure/In-the-light-of-day-the-Cisco-UCS-hype-doesn-t-match-the-promise/ba-p/83537
PLEASE READ ALL of Duncans Post BEFORE you READ Mine. I DO NOT PRETEND to REPRESENT HIS SIDE WELL AT ALL!