solarwindsthwackgeek speak

Tweets from the Head Geek

New blog post - Part Two of Wired vs. Wireless for new office build outs. http://bit.ly/cfcqHR

23 hours ago

Follow me on Twitter »
Geek Speak Blog
There's no place like 127.0.0.1
Geek Speak Blog

18 Mar 2010

Dude, cut the cord already - Part Two

Comments (1) | Trackbacks (0)

As you may have seen, a couple of weeks ago my friend and fellow blogger Michael Morisy over at Tech Target wrote a great blog post on his views of why today's network technology doesn't support the all wireless office environment. You can go read what Michael had to say about it here. I happen to be of the opposite opinion - i.e. I do believe that in many cases organizations could save a lot of time, money, and even improve the customer experience by going all wireless. You can read more about my position here.

As would be expected Michael came back with even more propaganda about how he thinks that wireless isn't really cheaper than wired, has security concerns, and etc and posted it here as well as opening it up for discussion on IT Knowledge Exchange. And now my friends, for, the rest of the story...

We have a habit as technologists of jumping onto new technologies really early and forming opinions that don't get updated as the technology evolves. Take NetFlow for example. When Cisco first released NetFlow you had to be extra careful about turning it on. In many cases enabling this feature took up so much CPU that the router either stopped routing packets or just completely gave up the ghost. A lot of folks decided at that point that NetFlow was too dangerous for their networks. This helped to drive the development of technologies leveraging Deep Packet Inspection (DPI) in network appliances. Funny thing is, NetFlow didn't sit still. It evolved. Nowadays it's extremely safe to enable and with the ISR G2s there's no way that you can affect the main operations of the router with ancillary applications like NetFlow. That said, I still run into people at every event that are afraid to use it because of their early exeriences with the technology.

Could it be that many of us are hesitant to trust wireless for similar reasons? I don't think any rational person could argue that wireless isn't a lot cheaper than wired so let's discount that right off the bat. The fact that the calculator I used was written by a wireless vendor doesn't change the math behind it. Microsoft, eBay, Google, Yahoo, SAP, Ohio State University, the United States Air Force, and NASA have all publicly talked about the money that they've saved by going wireless.

Sure, sometime wireless networks go down. So do wired networks. Spectrum-wide interference is no less rare than service impacting IOS or firmware bugs. Today's best in class wireless networks automatically adjust to interference to find clean air and some of the new stuff coming out from Aruba and Cisco will enable spectrum analysis to increase the networks' view of the air to alert and adapt in realtime.

Nowadays people don't even do site surveys or any of the old school practices we used to do with wireless. The just drop an AP every 4,000 sq feet or so, plug it into the wall, and the systems automatically adjust the power and channels.

I'm not saying that wireless is a fit for every single use case. However, I stand by my opinion that in many cases you can skip the wires. Cut the cord already. The technology is here.


Flame on...
Josh
Follow me on Twitter

 

 

Comments (1)  |   | 
| More
11 Mar 2010

Evolution, Justice, and the Art of Being a Geek

Comments (1) |
I've mentioned it before, but The Big Bang Theory is one of my absolute favorite TV shows and if you're a geek like me you really ought to check it out sometime. Spoiler alert - if you watch the show I'm just about to discuss this week's episode... This week they did a bit where the guys had been following Adam West around Pasadena (hey, if you saw Adam West driving around town wouldn't you follow him?) and stumbled into a garage sale where they bought a box of miscelaneous items for $65. Among various other treasures was the One Ring . The one, single, remaining...
4 Mar 2010

It's time dude, cut the cord already...

Comments (6) |
Some things really are a matter of opinion. My buddy Greg Newman prefers spinnerbaits while I prefer to fish with plastic worms. My brother Zach prefers to shoot a pump gun while I shoot an over/under. And apparently my friend and fellow-blogger Michael Morisy over at Tech Target prefers to waste his money on less secure,old school wired networks than to step into the 21st century and join the wireless fan club... You can read all about his take on this subject here . Don't get me wrong - there are plenty of places where wired networks are the only logical choice and I don't...
25 Feb 2010

Understanding When to Deploy a Distributed Network Management Architecture

Comments (1) |
Here at SolarWinds we offer a product called EOC - or Enterprise Operations Console. EOC is used when you want to deploy Orion in a distributed management architecture. Today I received a question about when you should think about deploying such an architecture so I thought I'd take a few minutes to write on the subject. Before we go into the reasons to deploy such an architecture we should agree on what exactly a distributed network manaement architecture is. For the purposes of this conversation, a distributed network management architecture is any NMS that has more than core...
22 Feb 2010

Understanding the difference between NetFlow and IP SLA

Comments (0) |
One of the most common things I'm asked to explain is the difference between Cisco IP SLA and NetFlow. At a glance, they have a lot in common: They're both supported on many Cisco devices (routers, swithes, firewalls, etc) They both can help you understand network performance, especially on the WAN Network management applications like Orion and the SolarWinds free tools support both All that said, the similarities mostly end there... NetFlow Let's for a moment group all flow technologies including NetFlow, JFlow, sFlow, and IPFix together and just call them "NetFlow"...





RECENT POSTS


FIND