Controllerless Networks

last person joined: yesterday 

Instant Mode - the controllerless Wi-Fi solution that's easy to set up, is loaded with security and smarts, and won't break your budget
Expand all | Collapse all

Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

This thread has been viewed 7 times
  • 1.  Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

    Posted Jan 13, 2014 10:00 AM

    did anyone observe this strange behaviour?

    my AP mesh point continue to reboot every 20 minutes

     

    IAP-175 OS version: 6.2.1.0-3.3.0.2_38733

     

    Thank you



  • 2.  RE: Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

    Posted Jan 13, 2014 12:19 PM
    Usually this happens due to poor RF connection quality from the mesh portal to the mesh point. Could I understand if this is a new AP that got installed or has it been working for a while and just started to have this problem?

    Sent from my iPhone


  • 3.  RE: Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

    Posted Jan 14, 2014 02:45 AM

    It has been working good for a while....so i can't understand the reason of this behavour.

    Mesh portal and mesh point are 50 meters and full visible to each other. 

    Yes i guess for some reason there is poor RF connection. 

    do you know if there is something i can setup to mitigate this? 



  • 4.  RE: Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

    EMPLOYEE
    Posted Jan 14, 2014 04:48 AM

    You probably need to work with support, or have someone take a look at your setup.  If there is a hidden source of interference or if the antennas managed to be come unaligned, it could create the issues you mention.

     



  • 5.  RE: Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

    Posted Jan 14, 2014 04:55 AM

    Thank you ,

     

    about alignement it's not an issue because i  use a couple of omni 5Ghz.

    about interference...is it capable or not IAP 175 to change channel if detects a source of interference?

    could you please tell me some smart commang to troubleshoot it?

    i used to work with Aruba MSR and trobleshooting with IAP i found it very difficult.

     

    thank you



  • 6.  RE: Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

    Posted Jan 13, 2014 03:49 PM

    run the comand show version

     

    aruba-ap# show version
    Aruba Operating System Software.
    ArubaOS (MODEL: 105), Version 6.3.1.1-4.0.0.1
    Website: http://www.arubanetworks.com
    Copyright (c) 2002-2013, Aruba Networks, Inc.
    Compiled on 2013-11-26 at 12:32:36 PST (build 41049) by p4build

    AP uptime is 5 days 18 hours 48 minutes 51 seconds
    Reboot Time and Cause: AP rebooted Tue Jan 7 20:56:34 UTC 2014; Image Upgrade Successful
    aruba-ap#



  • 7.  RE: Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

    Posted Jan 14, 2014 05:51 AM

    Hi,

     

    Let me repeat the phenomenon:

    mesh point (IAP-175) running 38733 build, rebooted every 20 minutes because of mesh link failure. And the mesh portal is IAP-105 running 41049. Right?

     

    Then let 's check:

    1. check the antenna connectivity

    2. run below comands on portal:

        show running-configuration

        show ap-env

     

        It is better, if following comands can be run right after IAP175 rebooting. If not, the outputs of these commands are also helpful

        show ap mesh neighbours

        show log debug

        show ap arm history

        show ap arm rf-summary

        

    3. run below commands on that IAP-175, if possible,

        show ap-env

        show ap mesh neighbours



  • 8.  RE: Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

    Posted Jan 14, 2014 08:27 AM

    mesh point and mesh portal are both IAP-175, and since this morning, i upgraded both to:

    6.3.1.2-4.0.0.2_41506

     

    but every 20-15 min ore sometimes more 40 min the mesh point reboots. now it's not so regular.

     

    I suspect DFS issue. Is there a way to turn it off (for a while) my regulatory domain is Europe.

     

    that's AP arm histor on mesh portal:

     

    Interface :wifi0
    ARM History
    -----------
    Time of Change Old Channel New Channel Old Power New Power Reason
    -------------- ----------- ----------- --------- --------- ------
    2014-01-14 13:30:47 116+ 124+ 27 27 M
    2014-01-14 13:11:29 100+ 116+ 27 27 R
    2014-01-14 13:11:18 132+ 100+ 27 27 R
    2014-01-14 13:10:47 108+ 132+ 27 27 R
    2014-01-14 13:08:09 116+ 108+ 27 27 R
    2014-01-14 13:00:36 124+ 116+ 27 27 R
    2014-01-14 12:34:57 116+ 124+ 27 27 R
    2014-01-14 12:06:54 100+ 116+ 27 27 R
    2014-01-14 12:06:16 100+ 100+ Max 27 P-

     



  • 9.  RE: Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

    Posted Jan 14, 2014 10:24 AM

    Mesh: portal:

     

    sh ap mesh neighbours

    Neighbor list
    -------------
    MAC Portal Channel Age Hops Cost Relation Flags RSSI Rate Tx/Rx A-Req A-Resp A-Fail HT-Details Cluster ID
    --- ------ ------- --- ---- ---- -------- ----- ---- ---------- ----- ------ ------ ---------- ----------
    d8:c7:c8:02:47:f9 d8:c7:c8:02:46:98 116+ 1 1 7.00 C 9m:39s HLK 49 270/270 1 1 0 HT-40MHzsgi-2ss a2fdabcb9231957da75a0d509eb8d8b

     

    after a while...

     

    sh log wireless

    [..]
    Jan 14 15:31:31 sapd[1121]: <404076> <WARN> |AP wisper_montefiore_comune_ap2@10.41.9.3 sapd| AM d8:c7:c8:02:46:98: Radar detected on interface wifi0, channel 116, typeid 38

     

    after a while...

     

    sh ap mesh link

    Neighbor list
    -------------
    MAC Portal Channel Age Hops Cost Relation Flags RSSI Rate Tx/Rx A-Req A-Resp A-Fail HT-Details Cluster ID
    --- ------ ------- --- ---- ---- -------- ----- ---- ---------- ----- ------ ------ ---------- ----------
    d8:c7:c8:02:47:f9 d8:c7:c8:02:46:98 100+ 0 1 7.00 C 3m:43s HLK 54 300/300 1 1 0 HT-40MHzsgi-2ss a2fdabcb9231957da75a0d509eb8d8b

     

    Jan 14 15:58:42 sapd[1121]: <404088> <WARN> |AP wisper_montefiore_comune_ap2@10.41.9.3 sapd| AM d8:c7:c8:02:46:98: ARM HT Radar Detected Trigger Current Channel old 116+ new 100+/9
    Jan 14 16:18:32 sapd[1121]: <404076> <WARN> |AP wisper_montefiore_comune_ap2@10.41.9.3 sapd| AM d8:c7:c8:02:46:98: Radar detected on interface wifi0, channel 100, typeid 33
    Jan 14 16:18:32 sapd[1121]: <404088> <WARN> |AP wisper_montefiore_comune_ap2@10.41.9.3 sapd| AM d8:c7:c8:02:46:98: ARM HT Radar Detected Trigger Current Channel old 100+ new 116+/9

     

    and now...no connectivity. what's happening?

     

    ARM History
    -----------
    Time of Change Old Channel New Channel Old Power New Power Reason
    -------------- ----------- ----------- --------- --------- ------
    2014-01-14 16:18:32 100+ 116+ 27 27 R
    2014-01-14 15:58:42 116+ 100+ 27 27 R
    2014-01-14 15:29:28 116+ 116+ Max 27 P-

     

     

     

     



  • 10.  RE: Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

    EMPLOYEE
    Posted Jan 14, 2014 10:34 AM

    It looks like you are using DFS channels and are encountering Radar.  What is your regulatory domain?

     

     



  • 11.  RE: Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

    Posted Jan 14, 2014 10:36 AM

    Europe



  • 12.  RE: Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

    EMPLOYEE
    Posted Jan 14, 2014 10:38 AM

    There is no europe regulatory domain.  It has to be a country.



  • 13.  RE: Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

    EMPLOYEE
    Posted Jan 14, 2014 10:42 AM

    Actually, you might have to switch to 2.4 ghz for mesh.  From the output it looks like you have radar on ALL of your available channels:

     

    2014-01-14 13:11:29 100+ 116+ 27 27 R
    2014-01-14 13:11:18 132+ 100+ 27 27 R
    2014-01-14 13:10:47 108+ 132+ 27 27 R
    2014-01-14 13:08:09 116+ 108+ 27 27 R
    2014-01-14 13:00:36 124+ 116+ 27 27 R
    2014-01-14 12:34:57 116+ 124+ 27 27 R
    2014-01-14 12:06:54 100+ 116+ 27 27 R

     

    These are the available channels:

     

    802.11a 40MHz (outdoor)  100-104 108-112 116-120 124-128 132-136

     



  • 14.  RE: Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

    Posted Jan 14, 2014 10:50 AM

    Sorry...Regulatory domain: Italy

     

    >Actually, you might have to switch to 2.4 ghz for mesh

     

    how can i do that. do you have a link on a document that explain this?

     

    Many Thanx



  • 15.  RE: Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

    EMPLOYEE
    Posted Jan 14, 2014 10:54 AM

    @lepida wrote:

    Sorry...Regulatory domain: Italy

     

    >Actually, you might have to switch to 2.4 ghz for mesh

     

    how can i do that. do you have a link on a document that explain this?

     

    Many Thanx


    Let us check something in the background to make sure a code upgrade will not help it.  Are you near a police station, hospital or airport where there could be radar?

     



  • 16.  RE: Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

    Posted Jan 14, 2014 11:11 AM

    a little town over the hills. 13km far from the sea and an from a little harbour

     



  • 17.  RE: Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

    Posted Jan 14, 2014 11:29 AM

    and 14km far from an airport!



  • 18.  RE: Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd
    Best Answer

    EMPLOYEE
    Posted Jan 14, 2014 11:34 AM

    Allright.  What you could do is disable "Wide" channels by going to RF> ARM and changing wide channel bands to "None".  That could give you more channels to use.  This could also drop your mesh throughput, but at this point, we are trying to keep your mesh link up..

     

    widechannel.png



  • 19.  RE: Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

    Posted Jan 15, 2014 02:48 AM

    ok,

     

    today i will try. Thank you. But only one more thing . I understand R, radar detact, but i can't undestand why IAP change channel if found one channel empy (M). Furthermore...i still can't reach the IAP

     

    wisper_montefiore_comune_ap2# sh ap arm history

    Interface :wifi0
    ARM History
    -----------
    Time of Change Old Channel New Channel Old Power New Power Reason
    -------------- ----------- ----------- --------- --------- ------
    2014-01-15 08:33:22 116+ 124+ 27 27 M
    2014-01-15 08:27:38 124+ 116+ 27 27 M
    2014-01-15 08:21:38 116+ 124+ 27 27 M
    2014-01-15 08:13:57 124+ 116+ 27 27 M
    2014-01-15 08:08:12 100+ 124+ 27 27 M
    2014-01-15 08:07:49 124+ 100+ 27 27 M
    2014-01-15 08:00:44 108+ 124+ 27 27 M
    2014-01-15 07:53:57 124+ 108+ 27 27 M
    2014-01-15 07:40:15 116+ 124+ 27 27 M
    2014-01-15 07:38:50 132+ 116+ 27 27 R
    2014-01-15 07:38:49 116+ 132+ 27 27 R
    2014-01-15 07:30:44 100+ 116+ 27 27 R
    2014-01-15 07:23:31 100+ 100+ 24 27 P+
    2014-01-15 07:16:26 108+ 100+ 24 24 R
    2014-01-15 07:09:57 124+ 108+ 24 24 R
    2014-01-15 07:03:05 124+ 124+ 21 24 P+
    2014-01-15 06:57:16 124+ 124+ 27 21 P-
    2014-01-15 06:49:23 116+ 124+ 27 27 R
    2014-01-15 06:41:29 100+ 116+ 27 27 R
    2014-01-15 05:34:19 100+ 100+ 24 27 P+
    2014-01-15 05:29:19 116+ 100+ 24 24 M
    2014-01-15 05:28:18 116+ 116+ 21 24 P+
    2014-01-15 05:23:14 124+ 116+ 21 21 M
    2014-01-15 05:20:52 124+ 124+ 18 21 P+
    2014-01-15 05:16:35 116+ 124+ 18 18 M
    2014-01-15 05:16:21 116+ 116+ 24 18 P-
    2014-01-15 05:09:54 124+ 116+ 24 24 M
    2014-01-15 05:08:37 124+ 124+ 21 24 P+
    2014-01-15 05:04:17 116+ 124+ 21 21 M
    2014-01-15 05:03:59 116+ 116+ 27 21 P-
    2014-01-15 04:51:03 100+ 116+ 27 27 R
    2014-01-15 01:59:45 124+ 100+ 27 27 R



  • 20.  RE: Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

    EMPLOYEE
    Posted Jan 15, 2014 06:51 AM

    Empty channel is when there is no activity on a channel, meaning it is better than the one that the access point is currently on.  Do your problems occur at a specific time of day or night?  Is there a pattern?



  • 21.  RE: Reboot Reason: AP rebooted mesh link BAD. rebooting mesh point by sapd

    Posted Jan 15, 2014 07:03 AM

    it was the one in this topic. i didn't understand why it was jumping from one frequence to another, giving me no stable mesh connectivity, although it wasn't find a radar, but only empty channels

     

    2014-01-15 08:33:22 116+ 124+ 27 27 M
    2014-01-15 08:27:38 124+ 116+ 27 27 M
    2014-01-15 08:21:38 116+ 124+ 27 27 M
    2014-01-15 08:13:57 124+ 116+ 27 27 M
    2014-01-15 08:08:12 100+ 124+ 27 27 M
    2014-01-15 08:07:49 124+ 100+ 27 27 M
    2014-01-15 08:00:44 108+ 124+ 27 27 M
    2014-01-15 07:53:57 124+ 108+ 27 27 M

     

    anyway i follow your suggestion and turn off wide channel bands. now for the first time mesh is stable for 4 hours!

     

    Many thanx