THE BLOG ★ Ramblings on WiFi & stuff.

Life After the Red Pill. (or, CWNP & Me)

Estimated reading time: 7 minutes, 8 seconds. Contains 1427 words

To start off 2016 I wanted to give you an idea of my life before CWNP (Certified Wireless Network Professional), the benefits I have seen from the program, learning the intricacies of 802.11, and its affect on my business, and customers.

THE KNOWN UNKNOWNS

In 2007 I was hired by a large cabling company to start a new voice & data services business. I had been in voice since 1994, installing and maintaining large Nortel PBXs, as well as Windows Server Management (Active Directory, Exchange, ISS, etc.). The cabling company eventually decided they wanted to sell Wi-Fi so they asked me to research various vendors to partner with - and so I did. That was my introduction to wireless.

After deciding on our vendor I proceeded to take the prescribed classes and learned how to "program" their system. There was no discussion of RF in these classes, or encouragement to learn about such things. I got a paper that certified I knew what I was doing - so I figured I actually did. How hard could it be? It did not take long to realize it was pretty hard.

My first deployment was for a large Restaurant/Comedy Club/Event Facility and I "designed" the WLAN the way any normal, intelligent person would - I walk into the facility pointed to where I wanted the APs and marked it on a floorpan. The cabling techs ran the cable mounted the APs and I configured the system as I was taught.

When the inevitable problems arose upon the first event I was on the phone with TAC trying "fix the problem". Clearly their system was not doing what it promised. TAC enabled all various types of features to try to get things working. But, no matter what we did the wireless would fail.

It's only with hindsight, and experience, that I now know that APs don't work well from the concrete room where the sound guy is, or that two APs WILL NOT support 450 people no matter what the manufacturer tells you, or that setting APs to max power is not the answer to bad-fi. But, I digress...

INTO THE GREAT WIDE OPEN

I started my career in wireless in 2007, and then I started my own company in 2009. But, it wasn't until 2012(ish) that I hit the brick wall that set me on the path I now find myself. Because that's when I found a Web site called WLANPros.com, and a man named Keith Parsons, that seemed to know a lot about wireless. He mentioned things like, "RF", and "co-channel interference", and something called, "CWNP". By this time I had begun to think of myself as a wireless guy rather than a Voice, or Server guy and I was intrigued by people who understood wireless. Not my vendor of choice, but wireless - that invisible stuff that had alluded me for so long.

I started reading blogs, and finally making use of Twitter by following people such as Keith, Devin Akin, and Andrew von Nagy, among others. I started realizing just how little I knew about wireless, and how far I was from where I needed to be. And now I had the bug. I had to know wireless and its secrets.

My first step was to call Keith Parsons. I asked him about classes that he taught and told him that I wanted to learn more. He asked me questions that made me extremely uncomfortable, such as: "How do you survey?", "What tools do you use?", "Have you read the CWNA book?", among others. I finished that call knowing that I had left a path of poorly "designed" WLANs in my wake, and that I loved wireless. I purchased the CWNA Study Guide and started reading.

The results were immediate. I called up past customers and told them I would like do a free "wifi cleanup". I would go to their location and correct the wrongs I had done using the information I was learning from the CWNA book. Even relocating APs at my cost! I did this for a while and bought the book for new employees (and customers) so they could learn.

To me, getting the CWNA certification seemed unattainable - never mind CWNE, but in 2013 I signed up for a CWNA class taught by Robert Bartz. There were two things I learned in that class:

  1. I knew stuff! The past few years of reading and correcting my mistakes were really paying off.
  2. I knew nothing, but I wanted to learn more.

In December of 2013 I became a CWNA. I was now part of something I thought was out of my reach - a WLAN Professional.

DOWN THE RABBIT HOLE

alternate text

"You take the blue pill, the story ends. You wake up in your bed and believe whatever you want to believe. You take the red pill, you stay in wonderland, and I show you how deep the rabbit hole goes."

―Morpheus

I was now getting to be known as "that guy who fixes wi-fi". I was being called in to fix, validate, design, because I knew how to get it done right. It was only yesterday that I was on the phone with TAC trying to figure out what button to press, what checkbox to check, to fix everything. Now, with the knowledge I had gained I was "the Fixer". I was "the Architect". I was the "Professional".

Then, at WLPC 2014, I made the decision to try for CWNE. In a year, no less! Sure, I would never make it - that was for the real professionals, but would I learn a lot. So I proceeded to study through the CWNP program.

I started with the CWAP. Packet Analysis was by far a weak point for me, and I knew if I could learn this secret code it could help me in the field. So, I bought the book and started reading. Within a few weeks I was at a Community College troubleshooting an issue with new HP clients not being able to connect to the WLAN, but only at one specific building. No better time than the present, so I open my packet analyzer and started capturing.

At first I didn't understand what I was seeing, but like Neo in the Matrix, it started to come together. I noticed the clients were sending disassociation frames to the APs. They did not want to stay connected. I looked at the beacons where the clients could connect. I looked at the beacons where the client could not connect. They were different. The beacons in the new building with the new APs showed they had the "RN Enabled Capabilities" Tag. The beacons where they could connect did not have 802.11k enabled.

I had done my first real-world, wireless packet analysis. And just like Neo, I could see into the Matrix and knew right away, "these client do not support 802.11k”, and they didn’t like connecting to a WLAN that did. One of the techs had enabled it on the new AP group because he heard, "it does something with roaming". The solution was to simply disable 802.11k and instantly the clients connected.

THE GIST OF IT ALL

That's CWNP to me. It's the Red Pill that let's you see the Matrix for what it is. But, it's not for everyone. Most don't want to travel that far down the rabbit hole and are happy with what the vendors tell them. "Check this box to fix roaming", "toggle that switch to increase your WLAN speeds by 50%", or "our APs are 175% faster than Cisco, Aruba, HP, & Ruckus... COMBINED".

Over the course of the following year I purchased the CWDP and CWSP and started reading those as well. My goal was now to run the gauntlet by WLPC 2015 in Dallas. In December 2014 I took another class with Robert Bartz and got my CWAP. Through January 2015, I self-studied for, took, and passed the CWDP and CWSP exams.

I had done it. What I thought was impossible for me - passing all the CWNP exams - was a reality. Thanks to the help and encouragement of an amazing community of wireless enthusiasts I had done in a year what I thought would take me 3, or 4.

Going through the CWNP program has resulted in a career I never thought I'd have. My customers have reaped the benefits of having someone who understand the fundamentals of why WLANs work, and I have seen the benefits in the growth of my business, and reputation, and a decrease in the Bad-Fi. I owe it all to the WLAN community and CWNP.


Thoughts on the HP/Aruba Acquisition

Estimated reading time: 6 minutes, 5 seconds. Contains 1218 words

I've made no secret of my apprehension at the HP/Aruba Networks acquisition talks. It was due mostly to the history of HP acquisitions over the last 10-15 years. I'm sure most people in networking are familiar so I won't list them. But, a simple Google search should give you all the info you need.

The news leaked the week before Aruba Networks' annual Airheads conference in Las Vegas called Atmosphere 2015. I was considering not coming and was vocal about it on Twitter. So, it was with only modest surprised when I arrived at the conference only to find that my reservation had been cancelled. I was pretty vocal about my distaste for the merger and as much so about the possibility of me not coming. So, I can't blame them for assuming that would be the case. I was straightened out rather quickly with little difficulty so it's really more of an amusing anecdote than anything else.

That said, I was not sure what to expect at this years Atmosphere. How would the announcement be made? Well, as it turned out, like this:

I have to admit that was NOT something I wanted to see. Very reminiscent of the Steve Jobs and Bill Gates version of this back in the 90s well Microsoft was investing millions in Apple. It certainly did not give me an warm fuzzies to see the Giant-Size "Big Brother" version of Meg Whitman over a teeny-tiny Orr. 

But, despite that uncomfortable introduction to the HP acquisition I will say that Dominic did make me feel better. I trust him, but I'm concerned about the HP end of the equation, "He with the most gold rules." HPs got the gold. Of course, Aruba cannot disclose much about the deal. First, it has only just been announced and it will be months before it can close. Second, the deal has to pass regulatory mustard, there will be negotiations as to how the deal will be structured, and what Aruba's management role will be. There isn't much to glean from the statements made, but they did post an announcement on their Web site. The interesting bits to me are:

 

"Together, HP and Aruba will deliver converged wired and wireless solutions, leveraging the strong Aruba brand."

 

LOTS of speculation here. Does this mean that Aruba MAS switching line will remain, or that it's technology will be implemented into HPs existing products, or that HPs switching will now become Aruba's switching line? 

I can see the benefit of bringing Aruba's technology to the wired edge. The MAS product line has not gotten a lot of traction in the market and adding that to the HP line may be seen as a good thing. But, Procurve has a solid brand already (especially in K-12), and they already have the no. 2 spot behind Cisco. So, this is going to be tricky if it happens at all.

 

"The new combined organization will be led by Aruba Networks CEO Dominic Orr and co-founder Keerti Melkote."
 
"After the transaction closes, Aruba will combine with the HP Networking business within HP’s Enterprise Group organization, led by Dominic Orr and Keerti Melkote."

 

So, is this actually saying that HPs networking business will be folded into a newly acquired Aruba? Will HP Networking's management be replaced by Aruba's management? I would love this to be true. I don't trust HP to manage this group into success, but I do trust Dominic and Keerti. If this actually happens - Aruba maintains their brand and will now be responsible for HPs networking division - then I have reason to hope.

Andrew Von Nagy made a good comment at Tech Field Day during the Aruba conference about Meg Whitman's (HP CEO) history with eBay/Paypal and her leaving each unit independent. So, will they really leverage Aruba's brand and expertise and let them run it as they see fit? That is the question at hand and it will take several years before we know the answer.

 

"HP will retain Aruba’s strong culture, including the Airheads Community, specialized sales focus on mobility solutions, and innovative development team."

 

To me, this is the biggest issue. Having the right technology is important, but having a team, and more importantly, a culture, that can execute the vision along with the technology is equally if not more important. HP does not inspire trust with their record of acquisitions in the 2000s. The HP "lifer" mentality is still alive and kicking and HP has not been known for real innovation in a while.

I don't know of an instance - other that Steve Jobs and NeXT - of an acquired company changing the culture of the larger company. They have the money, the actual numbers (300k, or so, at last count), and an entrenched culture of lifers that could make this difficult. The fact that they specifically mentioned Aruba's culture and community is cause for hope, but words are just words until it actually happens.

Aruba has also been an active participant and voice in the wireless community. They have non-Aruba bloggers post on their Airheads Community, and often reach across the aisle without hesitation. Will this also continue? Again, it will take a few years before we know the outcome.

 

"We will be able to significantly increase investments in demand generation across segments."

 

And here is the biggest perceived benefit to Aruba to come out of the acquisition: money. Aruba is just about an $800 million dollar company, whereas HP is in the $20 billion dollar+ club. Those are some deep pockets that could potentially help Aruba compete head-on with Cisco - their largest rival and the current market leader.

This would allow Aruba to scale and invest in R&D, perhaps even going as far as allowing Aruba to design their own custom silicon as does Cisco. HPs presence in the enterprise is another opportunity for Aruba to increase their customer base and reach.

But, this could also be a drawback. The catch-22 of being a large company - it gives you deep pockets to take advantage of opportunities, but at the same time slows you down via the inevitable bureaucracy that is introduced. Only a good, strong, and focused management team can help alleviate that.


MY TAKE?

I am officially, completely, 100% "cautiously optimistic". I can't help, but be slightly apprehensive about HP buying Aruba. No one familiar with this space can honestly say that HP has not botched acquisition after acquisition in the last 15 years. For every successful one there are three, or four that were disastrous. The revolving door of CEOs also makes me question their ability to not interfere with Aruba's success, or simply lose interest.

That said, I trust Dominic and Keerti. I believe they only want Aruba to be the most successful company it can be. If HP can stay out of their way, and let them and their team manage the newly created division as they see fit, I believe we'll see great things in the coming years. If they squander this opportunity and try to change Aruba to do it the "HP way" then I have no hesitation in saying I think they're doomed.

I want these guys to win. I want to see an Aruba that is the leader in it's space and keeps innovating with their products. 

I want to believe.

Don't screw this up HP.

 

REVIEW: AirTool 1.0

 

I've been beta testing a new app called AirTool from developer Adrian Granados for a few days. It finally went live today, so here is an overview of the app .

What does it does:

  • Select specific channels to perform a pcap on in 2.4/5GHz.
  • Select channel width
  • Capture on ALL 2.4/5GHz channels (hops through channels during pcap.)
  • Open pcap in Wireshark automatically upon stopping capture.
  • Visual indicator in task bar of channel/width

Best of all the app is FREE! 

DOWNLOAD...

Here is a link to make a donation via paypal. Let's help keep independent developers working!
 

LTE-U in 5Ghz: An Introduction

Ericsson RBS 6402 Indoor Picocell

Ericsson RBS 6402 Indoor Picocell

Estimated reading time: 3 minutes, 46 seconds. Contains 756 words

I’m trying to wrap my brain around LAA-LTE. I understand what it’s trying to do, but not why. I mean that makes sense to me. Users are already choosing Wi-Fi over LTE when it's available. LAA will be used for downlink data only and most study's show that Wi-Fi use is significantly greater than mobile data usage anyways. Also, the carriers OWN their own spectrum, and unlike 5GHz, they control it, and have the ability to manage it. 

So, why encroach on unlicensed spectrum? They'll have to abide by the power constraints in 5GHz, so in-building, small-cell deployments seem to be the way to go. Does this mean lots of indoor carrier pico-cells right next to existing APs? 

I wanted to learn a bit more about LAA and this is what I found so far...

What is LAA? It stands for “Licensed Assisted Access”. Basically, the carriers want to use 5GHz to supplement their “primary” LTE cells with a secondary cell in unlicensed 5GHz. This cell (in the initial stages of LAA-LTE at least) will be for downlink data transmission only. The “License Assisted” part means that the 5GHz cell is linked to the “Licensed” cell via “Carrier Aggregation” (think channel-bonding.. sort of). But, all control functions reside in the licensed spectrum cell and can even disable the 5GHz secondary channel if necessary. At issue here is not the use of 5GHz, which is unlicensed and so by definition anyone can use, but HOW it will be used.

In countries other than United States, China and South Korea, there is a regulatory requirement to “Listen-Before-talk”, or LBT. Since we have no requirement for that in the U.S. carrier manufactures are looking for other ways to place nice with Wi-Fi. The “how” is still up for debate. But, one thing seems clear, they won’t be using CSMA/CA. Qualcomm has a white-paper about this specific issue. Nokia has one to, but you have to buy it. No thanks, I'll just stick with Qualcomm's. Some of their proposed “Coexistence Mechanisms” are:

Channel Selection - attempts to pick the cleanest channel based on Wi-Fi and LTE measurements. Basically, it uses energy detection to see if how used the channel is.

Pretty straight forward, it scans the medium to find the channel that has the least usage. So, in small, to moderately-sized WLAN it should’t be a problem. Especially with DFS enabled.

Carrier-Sensing Adaptive Transmission (CSAT) - "...the cell senses the medium for a duration (around 10s of msec to 200msec) and according to the observed medium activities, the algorithm gates off LTE transmission proportionally."

This one is interesting. If the medium is found to be pretty saturated, and a “clean” channel is not available the cell will fall back to CSAT. LAA-LTE uses an “on-off” duty-cycle pattern. When the medium is heavily used, CSAT will change the duty-cycle timing it will use. It will still use the 5GHz spectrum, but settle on the "least harmful" time-cycle. It also uses only primary channels to mitigate inference with QoS traffic. However, this duty-cycle is directly proportional to the throughput of wi-fi client. In other words, throughout is reduced.

CableLabs.com has a nice piece on this and actually shows the correlation of the LAA-LTE duty-cycle  on wireless clients. 

Opportunistic SDL - “Since the anchor carrier in license band is always available, the SDL carrier in unlicensed band can be used on an opportunistic base.”

The Supplemental Downlink (SDL) can be enabled, or disabled, on-demand as necessary. In theory, if the primary LTE cell in the licensed spectrum can handle the traffic, the 5GHz secondary cell is turned off. Then if unlicensed offload is required the secondary cell can be turned on. So, LAA-LTE may not always be present. If the carrier's primary channel can handle the load 5GHz won't be used. Question is, will the carriers actually do that?

Qualcomm's white paper claims "due to the coexistence safeguards. In fact, the Wi-Fi performance improves by about 10%, since the neighboring LTE-U Picos can finish transmission faster and incur less interference instead". I don't know about that, and 10% over what?

I'm skeptical about the affect LAA will have on WLANs, but I'm willing to learn and be proven wrong. Also, this is just one more thing we as WLAN professionals have to account for in our wireless designs. 802.11 is already a pretty inefficient protocol and adding more overhead to 5GHz doesn't seem like it will improve anything except the carriers sense of well-being.

Qualcomm White paper:
LTE in Unlicensed Spectrum: Harmonious Coexistence with Wi-Fi

CableLab.com article: 
Wi-Fi vs. Duty Cycled LTE: A Balancing Act