Category Archives: Marketing

160 MHz Wide Channels: Just the Tip of an Iceberg of WLAN Industry Dysfunction

What lies ahead in this blog isn’t so much a rant, as it is an analysis. That sounds classier, and implies critical thought rather than just someone bitching about things. With that in mind, I give you the following image, stolen from Matthew Seymour (on Twitter at @realmattseymour) and sourced from this year’s Aruba Atmosphere conference in Europe:

The topic of the slide is 802.11ax, but that is tangential to the points I want to make here. Read that first caveat- this requires the use of 160MHz channels, which is generally not possible or just not a good idea wow.

I’m not sure who actually presented this session, but I’m assuming it is a trusted voice from a trusted company- Aruba folks generally know their stuff (as evidenced by their growing customer base and industry longevity). When I saw this come across Twitter, something in my mind clicked and this simple thought bubbled up:

Why does the WLAN industry do this idiotic shit to itself?

When I say the WLAN industry, I’m including the IEEE, the Wi-Fi Alliance, and the vendors that provide the hardware and the marketing of wireless networking products. Let me state the underlying problem as clearly as I can: the IEEE creates the 802.11 standards, and since 802.11n each standard has had a nonsensical top end- you simply cannot reach the high part of the spec. Evuh. The Wi-Fi Alliance does nothing to bring any sanity to the situation, and WLAN vendors build in configuration options with high-end settings that actually do WLAN operational damage and so let us create operational situations that are…

just not a good idea

Has anyone TOLD the IEEE that no one is really impressed with the promise of high end specs that can’t actually be leveraged? That it’s all a big stupid tease? Got some bait-and-switch going on here… The entire professional WLAN community knows that 160 MHz channels are…

just not a good idea

So why do WLAN vendors present 160 as an option in the UI? Why don’t the Wi-Fi Alliance and the vendor community repaint their messaging with reality-based promises of what each new WLAN technology can do? Wi-Fi 6 will STILL be impressive- but market it as if 160 MHz channels don’t exist- and watch the Sun of Truth rise over the wireless landscape (can I get a witness?).

I’m guessing some of you are thinking “you idiot, the FCC is going to give us more spectrum and then we’ll be rockin’ 160 for sure”. To that I say- pffft. I’ll believe it when I see it- and even then the ability to toggle 160- to even see it in configs- should not be a default.

The argument might also be made that “Maybe people AT HOME can use 160 MHz channels so you should shut up about it already”. Don’t go there, girlfriend. That only amplifies my beef with the Wi-Fi Alliance members who refuse to draw a clean line between Enterprise Grade gear and Wonky Shit That Plays Well at Home But Shouldn’t Be Dragged Into The Enterprise environment.

And that loops us back to the “tip of the iceberg” thing- and a couple more examples of general industry dysfunction. We have cheap printers that come up in default 40 MHz wide channels in 2.4 GHz, which also is…

just not a good idea

And an industry-wide trend where pretty much most 5 GHz gear comes up with 80 MHz channels enabled. Which also happens to be…

just not a good idea

We’re at an odd place where all the players involved are obviously aware of all the things that are

just not a good idea

yet they MARKET bad ideas and then we have to explain to those we support why we can’t really USE those bad ideas which have been marketed to us.

We kinda need our collective wireless head examined. Thus ends my analysis. 

That Which Pisses Us Wireless Folk Off- Vendor Edition

Now there’s a title. And since you’re reading this, you bit on it… Sucka. Now that you’re here, let’s share some observations from the WLAN community over the last few weeks. This is not (totally) a “Lee’s complaining again” blog; it’s more a collection of sentiments from dozens of friends and colleagues from across the Wi-Fi Fruited Plain that stuck with me for one reason or another.

Most of these observations are aimed squarely at our vendors- those who we do business with “above” as we shape their offerings into the systems and services we offer to clients “below”, with us in the middle.

You may not agree with all of these. Perhaps some of your own beefs didn’t make my list. Either way, I’d love to hear from you in the comments section. Now, in no specific order:

  • Marketing claims. OK, we’re starting out with the obvious. Wi-Fi marketing has always been about hype, far-fetchedness, and creative blather. Nothing new under the sun here. I truly hope that your 10x better Wi-Fi is serving up 500 APs per client that are all streaming 62 Netflix movies each simultaneously from a range of 37 miles away from the AP.
  • “Enterprise” switches that don’t stack. Stacking is neither new, nor special. Do your bigger switches stack? Is it not even an option? If not, maybe tone down calling them “enterprise”.
  • Big Bucks for power cords. You got major balls as a vendor if you’re pricing garden variety power cables at $20 per.  Shame on you. Same same for PoE injectors, nothing-special antennas, rack mounts and assorted other parts/pieces that can be gotten for pennies on YOUR dollar elsewhere. C’mon…
  • No version numbers. By now, we all get “cloud”. And most cloud infrastructure vendors ARE using OS version numbers as a point of reference for their customers. The absence of version numbers becomes more onerous as ever more features get added. Give us the damn version number. Do it. Doooooo it.
  •  No CPU/Memory/Interface stats. It doesn’t matter what the “thing” is, or whether it’s cloud-managed or not. EVERY interface needs to show statistics and errors, and every thingy needs to show CPU and memory information. Whatever your argument to the contrary may be, I promise that you are wrong.
  • Frequent product name changes. Just stop already.
  • The same stinking model numbers used for everything. Why? Maybe someone has a 3 and 5 fetish out in Silly Valley. It’s confusing, it’s weird, and it’s weirdly confusing in it’s weirdness, which leaves me confused.
  • The notion that EVERYTHING to do with wireless must be monetized. After a while, we start to feel like pimps as opposed to WLAN admins. I get that vendors need to be creative with new revenue streams, but it can be carried to extremes when applied to the WLAN ecosystem.
  • Too many models. It seems like some vendors must be awarding bonuses to HW developers based on how many different versions of stuff they can turn out, but customers are left confused about what to use when and where and why versus the other thing down the page a bit. Variety is good, but massive variety is not.
  • Complexity. This might be news to some vendors: the ultimate goals in deploying your systems for both us and the end user are STABILITY and WELL-PERFORMING ACCESS. Somewhere, vendors have lost track of that, and they are delivering BLOATED and HYPER-COMPLICATED FRAMEWORKS that place a cornucopia of buggy features higher on the priority list than wireless that simply works as users expect it to.
  • Slow quote/support ticket turnaround. Most times when we ask for pricing or open a case with technical support, it’s because there is a need. As in, we need something. And our assumptions are that our needs will be fielded with some degree of urgency, as we’re all in the business of service at the end of the day. No one likes slow service. No one likes asking over, and over, and over, and over, and over if there are any updates to our need possibly getting addressed.
  • Escalation builds/engineering code bugs. At the WLAN professional level, most of us work off the assumption that if we don’t typically do our jobs right the first time, we may not get follow up work and ultimately may be unemployed. That’s kind of how we see the world. I’m guessing that WLAN code developers play by different rules. ‘Nough said.
  • Bad, deceitful specs. Integrity is what keeps many of us in the game as professionals. Our word is our bond, as they say. Can you imagine telling someone that you can deliver X, but then when they need X, you can actually only provide a fraction of X- and then expecting that person to not be pissed off? Why are networking specs any different? Enough truth-stretching and hyper-qualified performance claims that you have to call a product manager and sign an NDA to get the truth about.
  • Mixed messages. OK, we ALL own this one- not just the vendors. The examples are many- grand platitudes and declarations that might sound elegant and world-changing in our own minds, but then they often fizzle in the light of day. Things like…
    • We need mGig switches for 802.11ac! 
    • We’ll never need more than a Gig uplink for 802.11ac!
    • 2.4 GHz is dead!
    • Boy, there’s a lot of 2.4 GHz-only clients out there!
    • We’re Vendor X, and we’re enterprise-grade!
    • Why do I see Vendor X gear everywhere, mounted wrong and in nonsensical quantities for the situation?
    • That one agency is awesome at interoperability!
    • Why does so much of this stuff NOT interoperate?
    • You must be highly-skilled with $50K worth of licensed WLAN tools or your Wi-Fi will suck!
    • Vendor X sells more Wi-Fi than anyone, most people putting it in are obviously untrained, yet there are lots of happy clients on those networks!
    • Pfft- just put in one AP per classroom. Done!
    • Cloud Wi-Fi is a ripoff!
    • Cloud Wi-Fi saves me soooo much money and headaches!
    • Here’s MY version of “cloud!”
    • Here’s MY version of “cloud!”
    • I freakin hate how buggy this expensive gear is!
    • At least those bugs are numbered on a pretty table!

It goes on and on and on. Always has, always will. Behind the electronics that we bring to life and build systems from are We the People. The humanity involved pervades pretty much everything written here, from all sides and all angles. And I have no doubt that every vendor could write their own blog called “That Which Pisses Us Vendor Folk Off- WLAN Pro Edition”.  Touche on that.

Ah well- there’s still nothing I’d rather be doing for a living.

Dear Marketers- If the Phone Doesn’t Ring, It’s Me

I’ve had good days and bad days
And going half mad days
I try to let go but you’re still on my mind
I’ve lost all the old ways
I’m searching for new plays
Putting it all on the line

Lots of new friends with the same old problems
Open your eyes, you might see
If our lives were that simple
We’d live in the past
If the phone doesn’t ring, it’s me

(“If the Phone Doesn’t Ring, It’s Me”- Jimmy Buffet, 1985)

Ah yes… great tune. It came out in my first year serving Uncle Sam in the USAF, and I happened to be right in Jimmy Buffet’s neighborhood on the Gulf Coast at the time. I felt a connection with the song then because I was a long way from home, away for the first time. There was no way I could afford to actually call the people I missed very often, back in the days of pricey toll calls and very little rank on my sleeves to fund those calls.

Now, a hundred years later, the same song plays in my mind every time I get one of these emails:
no-call

As I wrote about here in The Wirednot Memo to PR/Marketers, I believe everyone has value. And though I’d never want to be in marketing myself, I also don’t have a lot of tolerance for “my toe in the door come hell or high water” messaging.

If I don’t answer your email, don’t expect a warm reception on the uninvited follow-up call. I’m both busy, and not interested- and I will not give co-worker’s names. If your initial email struck me as something a coworker could benefit from, rest assured that I forwarded it on to them to evaluate.

Otherwise… I’m Incommunicado.

Cheers.