Wireless Access

last person joined: an hour ago 

Access network design for branch, remote, outdoor and campus locations with Aruba access points, and mobility controllers.
Expand all | Collapse all

[Tutorial] Using Spectrum Analysis to Troubleshoot Wireless Problem #mhc

  • 1.  [Tutorial] Using Spectrum Analysis to Troubleshoot Wireless Problem #mhc

    Posted Mar 03, 2014 11:20 AM
      |   view attached

    This tutorial will show you how to provision an Aruba AP to perform Spectrum Analysis.

     

    If you found my post helpful, please give kudos!

     

    Introduction

    At a parents-teachers conference at my kid’s high school, a science teacher showed us a Power Point presentation in Wi-Fi smart board.  At the middle of the presentation, the wireless turned off with no connectivity, and teacher shrugged it off with comment “well, someone turns on microwave oven”.  You guess it right; they do not have Aruba gears.

    Do you wish when dealing with RF interference, you can see what causing the problem?  Then you need a Spectrum Analyzer.  Fortunately, with Aruba AP you don’t need to drag out the spectrum analyzer, drive to the location, set it up to analyze RF spectrum; you can do all at your desk.

     

    In this tutorial, I’ll demonstrate Aruba 6.3, AP-105 Spectrum Analyzer for ’g’ radio frequency.  Why only ’g’ you ask, I have not seen problem with ‘a’ band, not yet.  In addition ’g’ is a popular radio frequency for Wi-Fi, and at 2.4 GHz bandwidth, it is the most popular frequency spectrum not just for Wi-Fi, but also for microwave oven, x-ray, cordless phone, wireless camera, blue tooth…With this popularity, ’g’ radio suffers the most electromagnetic interference.

     

    The 2.4 GHz Frequency Spectrum

    For better analysis, we should understand the frequency spectrum.  I’ll explain “b/g” band 2.4 GHz radio frequency using the analogy of interstate highway.

    Government (FCC) gave us 11 lanes RF interstate highway.  In the late 90s, Wi-Fi companies started building vehicle model 802.11b.  The other companies such as blue-tooth, cordless phone, wireless camera… also built their vehicles and sent them to cruise the RF highway 2.4 GHz.  The interstate was crowded, but with 11 lanes to cruise, 802.11b vehicle carried passenger of 11 million bits (11 Mbps) could move and change lanes without problems. 

    The demanding for moving more data was growing, so the Wi-Fi companies came up with new vehicle model 802.11g that could carry 54 million bits.  To carry these many passengers, 802.11g required wider 3.5 lanes per vehicle, and to be cruised safely without collision with others, it could only travel on lanes 1, 6, or 11.  The RF high-way was crowded and more congestion, cruising safely in the wireless spectrum was no longer art or science, it was a war!  The poor or bad Wi-Fi design was easy knocked out of the high-way as in my kid’s public school I mentioned earlier.  To troubleshoot the problem, we needed a good spectrum analysis to blame the others that occupied “our spectrum” (even though we are the road rage)

     

    Convert AP to Spectrum for Analysis

    I think it is easy to use, and works better when AP is a full-time spectrum analyzer.  To convert AP to an analyzer I create a G- SPECTRUM radio-profile for ‘g’ radio, an A-OFF profile for ‘a’ radio, an ap-group SPECTRUM and add the radio profiles to this new ap-group

     

    (Aruba3600) #configure t
    Enter Configuration commands, one per line. End with CNTL/Z
    (Aruba3600) (config) #rf dot11a-radio-profile A-OFF
    (Aruba3600) (802.11a radio profile "A-OFF") #no radio-enable
    (Aruba3600) (802.11a radio profile "A-OFF") #rf dot11g-radio-profile G-SPECTRUM
    (Aruba3600) (802.11g radio profile "G-SPECTRUM") #mode spectrum-mode
    Warning: If there is an entry for a radio in 'ap spectrum local-override' profile on the local controller that terminates the AP, that entry will override the mode selection in the radio profile.
    (Aruba3600) (config) #ap-group SPECTRUM
    (Aruba3600) (AP group "SPECTRUM") #dot11a-radio-profile A-OFF
    (Aruba3600) (AP group "SPECTRUM") #dot11g-radio-profile G-SPECTRUM

     Find an AP in the area you want to do the spectrum analysis, and provision it to ap-group SPECTRUM:

    (Aruba3600) #ap-regroup ap-name 00TN-TEST SPECTRUM
    NOTE: For cert RAP ap-group specified in RAP whitelist will take precedence.

     

    We are now ready for Spectrum Analysis on next page

     

     

     

     

    one.png

     

    Figure 1 Logon to controller, click Monitoring -> SPECTRUM -> Spectrum Analysis

     

    two.png

    Figure 2: Click Spectrum Monitors tab, then click the AP that you just convert to Spectrum

     

     three.png

     Figure 3: Click the connected Spectrum Monitor to view real-time data

     

    The default will start with four screens: Real-time FFT, Swept Spectrogram (FFT Max), FFT Duty Cycle, and Interference Power.  I’ll keep the Swept Spectrogram and the FFT Duty Cycle, replace Real-Time FFT with Active Devices Table, and Interference Power with Channel Metrics.  You can find list of all tables, plots and their functions in Aruba OS 6.3 User Guide page 643. 

     

    four.png

     

    Figure 4: To replace Real-time FFT, click the little triangle at upper right corner of the graph, click “Replace With” then pick “Active Device Table”

    five.png

    Figure 5: My favorite table is Active device table.  Using this table with FFT Duty Cycle table in next figure, you can see channel 12-14 are affected by the fixed frequency as it shows in lines 1 and 2.  

    six.png

     

    Figure 6: The FFT Duty Cycle table shows channel 12-14 are 100% occupied probably by a wireless camera.  Fortunately, it won’t affect our Wi-Fi because we only use channel 1 to 11.

    seven.png

    Figure 7: The Swept Spectrogram displays power levels.  In this plot, channel 6 looks busy because my APs transmit on that channel.  

    eight.png

    Figure 8: Channel Metrics plot confirms with Active Devices table in fig. 5 that channel 12, 13, and 14 are affected by the Fixed Freq. devices.

    nine.png

    Figure 9: The impact of Microwave oven: you can see the last line is microwave oven, it affects channels 7-14, so if your host is on channel 6 or 11, it will have connectivity issue.  My Aruba AP quickly jumps to channel 1 to avoid this noise.

     

    To learn more about FFT Spectrum Analysis: http://bit.ly/1g2ONUc

     

     

    Attachment(s)

    pdf
    March_MHC.pdf   1.34MB 1 version


  • 2.  RE: [Tutorial] Using Spectrum Analysis to Troubleshoot Wireless Problem #mhc

    Posted Mar 03, 2014 11:21 AM

    Combined into the above post. (@Srynearson)



  • 3.  RE: [Tutorial] Using Spectrum Analysis to Troubleshoot Wireless Problem #mhc

    Posted Mar 03, 2014 02:14 PM

    Thanks Sean.  When I posted the whole tutorial it did not allow.  The error message was my post is more than 1,000,000 words  



  • 4.  RE: [Tutorial] Using Spectrum Analysis to Troubleshoot Wireless Problem #mhc

    Posted Mar 03, 2014 03:29 PM

    I have SUPERPOWERS :-) 



  • 5.  RE: [Tutorial] Using Spectrum Analysis to Troubleshoot Wireless Problem #mhc

    Posted Mar 30, 2014 02:44 PM

     

    The race for March MHC is about to end and it is a close race. For you, the “undecided kudoers”, I’d like to add a little zest to my post:

     

    In my tutorial I wrote that, “WLAN design was no longer an art or science, it was war!”  Let me explain what I meant by that.

     

    Back then we had no Wi-Fi solution at our company, and Aruba was only a toddler in the Wi-Fi market.  Departments deployed their own fat APs, “tsunami” was scattered around campus (remember those days?), so my company decided it was time to deploy WLAN.    We brought in few Wi-Fi companies for testing, at the end we liked the solution of and decided the two finalists Aruba and “Other”.  

     

    For the final test we asked the engineers of Aruba and “Other” setup their gears to make war Aruba vs. “Other” in our lab.  For test, we brought in a few laptops, microwave oven, popcorns, and cordless phones.  At that time Aruba AOS 2.0 just came out, I believed arm is version 1, immature and bugs, but Aruba engineer decided to keep arm 1 enable, why the “Other” engineer - after consulted with its engineer group back at the HQ - decided to turned off their version arm because they had even more bugs and problems.  That was a big mistake for the “Other”, Aruba Wi-Fi proved superior and won all the battles.