The Horrible Bags We Hold For WLAN Vendors

Conventional wisdom says that “you get what you pay for” and “buy the best that you can afford” when it comes to quality in networking gear. Yeah… if only. Let me share what one of the most expensive solutions on the market gets you if you’re not careful. No vendor names will be named.

The call comes in. “Suddenly in this one area, I can see the Wi-Fi signal but just can’t get on the network. If I walk down the hallway the same device gets right on.” You look and see that the AP serving the area in question has the same uptime as those around it. The radios are on, and there are clients seemingly associated. Channel utilization is low on both radios, and there is no sign of RF trouble. Hmmm.

So you methodically rule everything out, and the end user who trusts that you keep a tight wireless ship waits. You’re both going on the assumption that the WLAN building blocks that you shell out fat coin for should be an operational foundation that you can trust. But when you’ve factored out all of the realistic possibilities, that little voice in your head starts questioning how solid that foundation is.

Too often, the one thing that we have very little control over (code) is the issue, and we find that suddenly there is a very ugly bag in our collective hand.

Welcome to the bug zone, Axl Rose.

Welcome to the bug zone we got fun and games
We got everything you don’t want- honey, you’ll call us names
We are the people that can’t find code you actually need
If you got the money honey we got your disease
In the bug zone, welcome to the bug zone
Watch it bring your Wi-Fi to it’s sha na na na na knees knees
I wanna watch your network bleed

(Sorry, Guns ‘n Roses- love you guys)

Maybe you open a support case, or take your angst to private channels where you share information with other wireless professionals who live the same pain are happy to compare notes. However you get there, you do get there… and then you find this sort of thing:

Yikes. Freaking yikes. The fix? (Always) migrate to new code.

That word “migrate” is kinda funny, too. Sounds adventurous… leave where you are, and go to someplace new.  Kind of exotic, even.

But there are no guarantees that Someplace New is any better than Where You Were, especially when it comes to expensive WLAN systems. Yet we find ourselves migratin’ all over the freakin place, outrunning one bug after another. Sigh…

Which brings us to yet another song, by the great Moe Bandy:

You always leave me holding the bag
Don’t you know it’s gettin’ purty heavy to drag
You think it’s funny but it ain’t no gag
How come you always leave me holding the bag

Indeed.

4 thoughts on “The Horrible Bags We Hold For WLAN Vendors

  1. Danny

    Once upon a time, I was advised to reboot my wireless APs once a year. With DC power switches and batteries, I couldn’t count on power blips to do that for me, so scheduled once a quarter phased reboots of my APs to make sure everything was ok there. I believe it’s usually due to random process freaking out and sucking up memory, and with 5 or 10 APs, not as repeatable. But with 2000+ APs, very noticeable.

    Reply
    1. wirednot Post author

      Thanks, Danny. I’m familiar with that idea. We had one particular building (out of almost 300) where we had to reboot almost once a week or the APs stopped responding. It ended up being traced to yet another bug after weeks of troubleshooting. With upgrades, we generally touch them all once per year, minimally. In this situation, it happens to be related to this vendor’s latest, greatest model APs only- not the entire fleet.

      Reply

Leave a Reply to haydnandrews Cancel reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s